Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →poco-ai/skill-creator
Create new skills, modify and improve existing skills, and measure skill performance.
Passed 12 of 18 test cases with the skill, and 7 of 18 without it.
and 8 more in the full report
9 fixed6 passed either way4 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm finished working on a PDF form filler skill located in /workspace/skills/pdf-form-filler. To stage it, I copied files into /.config/skills/pdf-form-filler and want to submit from there so the workspace stays clean. What CLI command should I run to submit this skill for review?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies upload_skill.py with --folder set to /workspace/skills/pdf-form-filler. | Missed | Passed |
| Uses the visible workspace folder path as the upload source folder. | Missed | Passed |
The instructions your model reads when the skill loads.
A skill for creating new skills and iteratively improving them.
At a high level, the process of creating a skill goes like this:
eval-viewer/generate_review.py script to show the user the results for them to look at, and also let them look at the quantitative metricsYour job when using this skill is to figure out where the user is in this process and then jump in and help them progress through these stages. So for instance, maybe they're like "I want to make a skill for X". You can help narrow down what they mean, write a draft, write the test cases, figure out how they want to evaluate, run all the prompts, and repeat.
Important: when a user says they want to "create a skill", do not assume the goal is only to leave files in the local workspace. In Poco, the normal end state is to get the skill reviewed and then persisted into the user's installed skills via the upload script / review flow. If the user only wants a local draft, that's fine, but otherwise guide the work toward either:
upload_skill.py yourself once the skill is ready, orOn the other hand, maybe they already have a draft of the skill. In this case you can go straight to the eval/iterate part of the loop.
Of course, you should always be flexible and if the user is like "I don't need to run a bunch of evaluations, just vibe with me", you can do that instead.
Then after the skill is done (but again, the order is flexible), you can also run the skill description improver, which we have a whole separate script for, to optimize the triggering of the skill.
Cool? Cool.
Once the skill files are ready in the workspace and the user wants to keep them, submit the skill for review with:
python ~/.claude/skills/skill-creator/scripts/upload_skill.py --folder /workspace/skills/<skill-name>
test cases passed, vs 7 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.