nano-muse/nanoMuse / nanomuse/skills/builtin/skill-creator
skill-creator
UnverifiedUse when creating or updating a reusable skill with task-specific instructions, supporting files and checks.
Skill Creator
Create a skill for the workflow the user asked to reuse. For an existing skill, read its instructions and referenced resources before changing it.
Choose the scope
Use the user's examples to identify when the skill applies and what result it should produce. Preserve their chosen tools, destination and permissions. If the installation location is unclear, inspect the current client's skill settings or documentation. A phone, desktop and Python runtime use different directories; do not assume one client's path configures another.
Bundled skills are managed by the app. Put a customized copy under a new name in the user's skill directory rather than replacing the bundled original. Check for an existing skill before creating files.
Write the skill
Use a folder named after the skill with a SKILL.md file at its root:
skill-name/
SKILL.md
scripts/ optional executable helpers
references/ optional material read when needed
assets/ optional files used in the output
Start SKILL.md with YAML frontmatter containing a lowercase, hyphen-separated
name and a short description of what it does and when to use it. Keep the name
under 64 characters. Preserve existing supported metadata when editing.
Write the body as instructions for the agent. Include details that change how the task is done: required inputs, useful tools, fragile steps and observable completion checks. Use provider-neutral language. Keep the main workflow short; link supporting references where they are needed, using relative paths.
Create scripts when deterministic execution improves reliability or avoids repeated work. Include only resources the workflow actually uses. Never embed credentials, personal records or private service addresses in a shared skill.
Check the result
Check the frontmatter, resource paths and script inputs. Exercise the workflow on a representative example and, where a failed check could accept the wrong result, on a counterexample. Test scripts with temporary fixtures before using them on the user's files. Report what was checked and any remaining limits.
Loading or creating a skill does not grant permission to send messages, install packages, change approval settings or take other external actions. Use the available tools through their existing approval rules and the user's scope.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |