Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/kv0906/pm-kit/skill-creatornpx skills add kv0906/pm-kit --skill skill-creatorgit clone --depth 1 https://github.com/kv0906/pm-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kv0906/pm-kit/skill-creator)<a href="https://agentmods.dev/skills/kv0906/pm-kit/skill-creator"><img src="https://agentmods.dev/badge/skills/kv0906/pm-kit/skill-creator.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00063 | $0.07054 |
| Opus 5 | $0.00032 | $0.03527 |
| Sonnet 5 | $0.00013 | $0.01411 |
| Haiku 4.5 | $0.00006 | $0.00705 |
Grade A, and why
skill-creator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
89% identical to skill-creator — 59 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 480 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
A skill for creating new skills and iteratively improving them.
At a high level, the process of creating a skill goes like this:
- Decide what you want the skill to do and roughly how it should do it
- Write a draft of the skill
- Create a few test prompts and run claude-with-access-to-the-skill on them
- Help the user evaluate the results both qualitatively and quantitatively
- While the runs happen in the background, draft some quantitative evals if there aren't any (if there are some, you can either use as is or modify if you feel something needs to change about them). Then explain them to the user (or if they already existed, explain the ones that already exist)
- Use the
eval-viewer/generate_review.pyscript to show the user the results for them to look at, and also let them look at the quantitative metrics
- Rewrite the skill based on feedback from the user's evaluation of the results (and also if there are any glaring flaws that become apparent from the quantitative benchmarks)
- Repeat until you're satisfied
- Expand the test set and try again at larger scale
Your 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.
On 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.
Communicating with the user
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/analyzer.md 10 KB
- agents/comparator.md 7.1 KB
- agents/grader.md 8.8 KB
- assets/eval_review.html 6.9 KB
- eval-viewer/generate_review.py 16 KB runs code
- eval-viewer/viewer.html 44 KB
- references/schemas.md 12 KB
- scripts/__init__.py 0 B runs code
- scripts/aggregate_benchmark.py 14 KB runs code
- scripts/generate_report.py 13 KB runs code
- scripts/improve_description.py 10 KB runs code
- scripts/package_skill.py 4.1 KB runs code
- scripts/quick_validate.py 3.9 KB runs code
- scripts/run_eval.py 11 KB runs code
- scripts/run_loop.py 13 KB runs code
- scripts/utils.py 1.6 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 480 lines · 63 tokens per session scan A ba8bebb2c085
skill-creator is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 7,054 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to skill-creator, differing in 59 lines, and is treated as a copy.
Other skills, from other repositories
critique-agent
Pressure-test an existing product brief or PRD pack — find gaps, hidden assumptions, inconsistencies, and failure modes before stakeholder review. Use when: critique brief, critique PRD, devils advocate, red team, pressure test, find holes, what could go wrong, stress test the doc, pre-mortem.
interview-frameworks
Frameworks for user interviews, question design, and qualitative research. Use when conducting user interviews, designing interview guides, researching user needs, or gathering qualitative insights. Trigger on: 'create an interview guide', 'how do I interview users', 'customer discovery questions', 'user research…
query-datasets
Answer grounded yes/no questions about what exists in the 03-datasets/ example corpora (supporttickets, calltranscripts) using the local SQLite + FTS5 + vector hybrid index. Use when the user asks 'do/does [corpus] contain/mention/include/have requests for X?', 'any [corpus] about Y?', or similar factual queries over…
critique-prd
Rubric-score a PRD pack (02 + 03) against the 7-dimension PM Brain rubric and run a 4-persona panel review. Returns scores, panel critiques, the single weakest section, a concrete rewrite, and P0/P1 fix lists. Use when: PRD review, score my PRD, rubric review, panel review, rewrite weakest section, critique-prd.
create-prd
Write the PRD pack (02-product-requirements.md + 03-success-metrics.md) on top of an approved product brief. Use when: PRD, product requirements, requirements doc, success metrics, spec writeup, shape the PRD.
create-internal-feature-announcement
Drafts an internal feature announcement (IFA) from the PRD pack and user sources using the repo template, then writes 04-internal-feature-announcement.md. Use when: IFA, internal feature announcement, internal FAQ, Slack IFA prep, launch comms pack, or internal product documentation from the template.