How do I install the Better Skills skill?

Run npx skillmds@latest add leonardotrapani/better-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Better Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Better Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Better Skills free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Better Skills?

LeonardoTrapani (@leonardotrapani) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Better Skills by leonardotrapani — Agent Skill

Name: Better Skills
Author: LeonardoTrapani

Better Skills

Index and route better-skills vault operations from the CLI. Trigger when users ask to manage better-skills or a skill vault (create, edit, delete, remove, search, import, clone, link, sync, backup, onboard, enable/disable vaults, inspect available vaults, move a skill across vaults). Do not use when asked to use a skill.

File contents

better-skills

Flows

Trigger	Flow
GitHub URL, skills.sh link, npm URL, blog post, any external source, or pasted external install command meant for a vault import	[[resource:new:references/import-skill.md]]
User wants to create/write a new skill from scratch	[[resource:new:references/create-skill.md]]
User wants to update/edit an existing vault skill	[[resource:new:references/edit-skill.md]]
Asked to onboard, Existing local skill folders not yet in the vault	[[resource:new:references/onboard-skills.md]]
User wants to delete/remove a skill	[[resource:new:references/delete-skill.md]]
"What skills do I have?", find related skills, linking requests	[[resource:new:references/search-and-propose.md]]
Anything not included above	[[resource:new:references/commands.md]]

Shared references

Authoring guidelines → [[resource:new:references/authoring.md]]
Mention linking → [[resource:new:references/linking.md]]
CLI command reference (load only when stuck with CLI syntax) → [[resource:new:references/commands.md]]

Rules

Every resource file must have a \[[resource:new:<path>]] mention — either in SKILL.md or in another resource. Never run create/update until validate exits clean.
Never use bare markdown links for internal resource references.
Always read authoring guidelines before creating or editing a skill.
If the user wants something added to a better-skills vault and pastes a third-party install command (npx skills add ..., skills add ..., etc.), treat that command as source context only. Do not execute it; route to [[resource:new:references/import-skill.md]] and use the better-skills import workflow.
Only run third-party install CLIs when the user explicitly asks for local agent installation instead of vault management.

---name: better-skillsdescription: Index and route better-skills vault operations from the CLI. Trigger when users ask to manage better-skills or a skill vault (create, edit, delete, remove, search, import, clone, link, sync, backup, onboard, enable/disable vaults, inspect available vaults, move a skill across vaults). Do not use when asked to use a skill.---# better-skills## Flows| Trigger | Flow || -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- || GitHub URL, skills.sh link, npm URL, blog post, any external source, or pasted external install command meant for a vault import | [[resource:new:references/import-skill.md]] || User wants to create/write a new skill from scratch | [[resource:new:references/create-skill.md]] || User wants to update/edit an existing vault skill | [[resource:new:references/edit-skill.md]] || Asked to onboard, Existing local skill folders not yet in the vault | [[resource:new:references/onboard-skills.md]] || User wants to delete/remove a skill | [[resource:new:references/delete-skill.md]] || "What skills do I have?", find related skills, linking requests | [[resource:new:references/search-and-propose.md]] || Anything not included above | [[resource:new:references/commands.md]] |## Shared references- Authoring guidelines → [[resource:new:references/authoring.md]]- Mention linking → [[resource:new:references/linking.md]]- CLI command reference (load only when stuck with CLI syntax) → [[resource:new:references/commands.md]]## Rules1. Every resource file must have a `\[[resource:new:<path>]]` mention — either in SKILL.md or in another resource. Never run create/update until validate exits clean.2. Never use bare markdown links for internal resource references.3. Always read authoring guidelines before creating or editing a skill.4. If the user wants something added to a better-skills vault and pastes a third-party install command (`npx skills add ...`, `skills add ...`, etc.), treat that command as source context only. Do not execute it; route to [[resource:new:references/import-skill.md]] and use the better-skills import workflow.5. Only run third-party install CLIs when the user explicitly asks for local agent installation instead of vault management.

Frequently asked questions