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.

7 stars

byLeonardoTrapani

View on GitHub Installation ↓

Best use case

better-skills is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Teams using better-skills should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/better-skills/SKILL.md --create-dirs "https://raw.githubusercontent.com/LeonardoTrapani/better-skills/main/resources/default-skills/better-skills/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/better-skills/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How better-skills Compares

Feature / Agent	better-skills	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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

1. 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.

Related Skills

better-auth-best-practices

from LeonardoTrapani/better-skills

Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

opentui

from LeonardoTrapani/better-skills

Comprehensive OpenTUI skill for building terminal user interfaces. Covers the core imperative API, React reconciler, and Solid reconciler. Use for any TUI development task including components, layout, keyboard handling, animations, and testing.

Coding & Development

web-design-guidelines

from LeonardoTrapani/better-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

vercel-react-best-practices

from LeonardoTrapani/better-skills

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

vercel-composition-patterns

from LeonardoTrapani/better-skills

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

turborepo

from LeonardoTrapani/better-skills

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

next-cache-components

from LeonardoTrapani/better-skills

Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag

next-best-practices

from LeonardoTrapani/better-skills

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

neon-postgres

from LeonardoTrapani/better-skills

Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.

hono

from LeonardoTrapani/better-skills

Efficiently develop Hono applications using Hono CLI. Supports documentation search, API reference lookup, request testing, and bundle optimization.

swe-cli-skills

from SylphAI-Inc/skills

Senior engineer CLI expertise for AI agents — workflows, safety guardrails, gotchas, and anti-patterns across cloud, IaC, containers, databases, dev tools, and platforms

DevOps & Infrastructure

pijul-sparse-skills

from plurigrid/asi

Sparsity-preserving skill versioning via Pijul patches with GF(3) projection gates