Improve expo-api-routes skill structure and documentation#22
Open
fernandezbaptiste wants to merge 1 commit into
Open
Improve expo-api-routes skill structure and documentation#22fernandezbaptiste wants to merge 1 commit into
fernandezbaptiste wants to merge 1 commit into
Conversation
- Expand frontmatter description with trigger clause and bump to v1.0.1 - Add References section, Workflow steps, and Verify Deployment section - Extract EAS Hosting runtime and common patterns into reference files
Author
|
Hi - just following up on the above. |
Author
|
Following up on the above, @wodin. |
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.
Hey @EvanBacon, thanks to your team for sharing expo/skills. Really nice move to make your workflows public, and kudos on soon hitting 1k stars! I just starred it.
Was running your skills through some evals and noticed a few things on
expo-api-routesthat were pretty quick to improve (moving from~60% to ~90%agent performance):added a 5-step build, test, deploy sequence so the agent isn't cherry-picking instructions + added a Verify Deployment section with curl commands to check the route works.
frontmatter description is (a little) generic. it didn't match prompts like add an API route or set up an endpoint so the skill was getting skipped in a lot of cases.
quickstart mixed with deep runtime details. pulled the EAS Hosting constraints and common patterns (auth middleware, API proxy) into references/ files so the skill stays scannable and the agent only pulls deeper context when it needs it.
these were easy changes to bring the skill in line with what performs well against Anthropic's best practices. honest disclosure, I work at a company where we build tooling around this. not a pitch, just fixes that were straightforward to make.
you've got
7skills here, if you want to do it yourself, evals are free and open to run: link. otherwise happy to make the improvements for you.