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/espressif/esp-claw/skill_creatornpx skills add espressif/esp-claw --skill skill_creatorgit clone --depth 1 https://github.com/espressif/esp-clawWrote 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/espressif/esp-claw/skill_creator)<a href="https://agentmods.dev/skills/espressif/esp-claw/skill_creator"><img src="https://agentmods.dev/badge/skills/espressif/esp-claw/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.00022 | $0.02017 |
| Opus 5 | $0.00011 | $0.01009 |
| Sonnet 5 | $0.00004 | $0.00403 |
| Haiku 4.5 | $0.00002 | $0.00202 |
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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Use this skill when the user wants to add a new reusable feature that the model should be able to invoke later as a skill, including tool-like workflows, project-specific capabilities, Lua-backed automations, or feature requests phrased as "add a function", "support doing X", "make the model able to X", "create a tool for X", or "新增一个功能".
Also use this skill when the user asks to create, register, update, or remove a skill, or asks how to create a skill that includes Lua files.
Core Rules
Every skill creation flow those mandatory phases:
- Create the complete source skill files.
- (Options for Lua-backed skills) Create the complete bundled Lua files under the skill-owned
scripts/directory and document how the skill invokes Lua. - Immediately call
register_skillso the newly created skill is added to the active skill registry.
Skills with source files live under a skills/<skill_id>/ directory that is included in the firmware or file image build. They may require rebuilding or regenerating the image that contains skills.
Skill id rules:
- Use lowercase letters, digits, underscores, or hyphens.
- Do not use spaces, slashes, backslashes, absolute paths, or
... - Make the id match the user-facing behavior rather than the implementation.
- Do not reuse an existing skill id.
Intent description rules:
- Describe user intent, not just internal implementation.
- Include trigger words users are likely to say.
- Include prerequisites when they are required.
- Keep it to one concise sentence.
- Do not summarize a skill as only running a script or calling a tool.
File generation rules:
- Create skill files by directly writing the needed files. Do not run a bundled preparation script or template generator.
- Generate
SKILL.mdfrom the final behavior, not from a generic unchanged template. - Generate optional bundled files directly, such as
scripts/<name>.lua,references/<name>.md, or assets. - If the environment cannot write files or cannot call
register_skill, provide the target relative paths and full file contents, report the blocker, and do not claim the skill was fully created and registered.
What ships with it
2 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.
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 · 228 lines · 22 tokens per session scan A 6c11556d816d
skill_creator is a skill published in the GitHub repository espressif/esp-claw (2,080 stars, last pushed 2d ago), licensed Apache-2.0. It adds 22 tokens to every session and 2,017 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…