add expo-skill-eval#87
Merged
Merged
Conversation
davidmokos
approved these changes
Jun 23, 2026
davidmokos
left a comment
Contributor
There was a problem hiding this comment.
This is super helpful for us. The questions is whether it's helpful for expo users and should be shipped with the rest of the skills?
Contributor
Author
that's not a scope currently. the skill is based on many assumptions and only works on macos host. if people really want to have the skill, they could copy the entire directory to their $HOME/.claude/skills. |
zvadaadam
approved these changes
Jun 24, 2026
zvadaadam
left a comment
Contributor
There was a problem hiding this comment.
let's merge it so we can start experimenting with it <3
I had some problems with expo go in this version but might be problem with my setup. I don't feel it's a blocker now.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
add evals for our skills
How
inspired by the skill-creator that we can use a skill to run evals.
before running the eval, it will ask some questions
which skill to run the eval
what to verify: screenshots, lint results, or some custom criteria
what prompts to drive the evals, having some default e.g. build settings screen for expo-ui skill. you can also upload a screenshot to ask agent to generate code by the screenshot
which sdk version for the projects (will fetch the latest sdk version as default)
whether to test on expo-go or development builds
which platforms to test (android, ios, web)
for eval result, keep it on local or upload to claude shareable artifact
confirm question to run subagents on
--dangerously-skip-permissionsmode. otherwise subagents will ask many questionsconfirm question to make sure the installed expo plugin is disabled. otherwise people may use the skills from marketplaces rather than the local developed
Test Plan
multiple runs on sonnet 4.6. some shared results that required expo org claude accounts to access