- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add nano-muse/nanoMuse --skill skill-creator -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add nano-muse/nanoMuse --skill skill-creator -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add nano-muse/nanoMuse --skill skill-creator -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add nano-muse/nanoMuse --skill skill-creator -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/nano-muse/nanoMuse/tree/HEAD/nanomuse/skills/builtin/skill-creatorDe l'éditeur
Create a skill for the workflow the user asked to reuse. For an existing skill, read its instructions and referenced resources before changing it.
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.
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 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.
Use when creating or updating a reusable skill with task-specific instructions, supporting files and checks.
---name: skill-creatordescription: Use when creating or updating a reusable skill with task-specific instructions, supporting files and checks.---# nanomuse/skills/builtin/skill-creator/SKILL.mdFAQ
Téléchargez nanomuse/skills/builtin/skill-creator/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/nano-muse/nanoMuse.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.