Organize skills with expo-* and eas-*#98
Open
jonsamp wants to merge 7 commits into
Open
Conversation
Resolve conflicts and bring new skills in line with the eas-*/expo-* naming + free/paid conventions: - Version: bump all three plugin manifests to 1.6.0 (> main's 1.5.0). - eas-simulator (new, paid EAS cloud service): add "EAS service (paid)." description prefix (trimmed one trigger example to stay under the 1024 char limit) and a costs/plan-limits callout; add to the paid catalogs. - web-to-native (new, OSS) -> expo-web-to-native: add "Framework (OSS)." prefix, repoint use-dom refs to expo-dom, register in all catalogs. - expo-dev-client / expo-ui: keep upstream improvements + version bump, re-apply the "Framework (OSS)." description prefix. - expo-skill-eval harness: update stale skill names to the new ones. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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
We're adding many skills and our naming conventions and patterns have started to sprawl.
This PR makes some changes to organize them:
expo-*oreas-*. This helps discovery since you can type/expo-and then you'll see all related skills. Also creates a clear boundary btw free/paid.Framework (OSS)orEAS service (paid).Breaking changes
There are no aliases for the old names for skills cli installations. So anyone who has installed
/building-native-uiwill no longer get updates. I don't think there's a way around this.Test plan
Please look at the skils and make sure they seem reasonable. Let me know if there are naming conventions/etc that you think we should change.
The new README is probably the best place to start: https://github.com/expo/skills/blob/bd295c4c5038247d6991aeac1e2d438118df62d1/README.md