create-skill

Guides authoring of Agent Skills with SKILL.md frontmatter, structure, and best practices.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Uguryldz/n8nclean --skill create-skill-uguryldz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/Uguryldz/n8nclean/tree/main/.claude/plugins/n8n/skills/create-skill
Command: npx skills add https://github.com/Uguryldz/n8nclean --skill create-skill-uguryldz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective Agent Skills is hard to get right: descriptions fail to trigger discovery, SKILL.md files bloat the context window, and workflows get crammed into one oversized skill. This Skill provides a structured authoring workflow so new skills are concise, discoverable, and correctly scoped. ## Core Features & Use Cases - Requirements gathering: Prompts for purpose, triggers, knowledge gaps, outputs, and examples before writing any skill content. - Authoring rules: Enforces concise SKILL.md files, progressive disclosure into reference.md, one default workflow, stable terminology, and forward-slash paths. - Scope guidance: Recommends one job per skill, small composable skills with thin parent orchestrators, and explicit MCP prerequisites with fallbacks. - Use Case: When you want to add a new team-shared skill under .claude/plugins/n8n/skills/, this Skill walks you through naming, description writing, file layout, and verification so the result matches team conventions. ## Quick Start Ask the agent to help you create a new skill for your workflow, and it will gather requirements and draft a compliant SKILL.md.

Frequently Asked Questions about create-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Agent Skill with SKILL.md?▼

Create a directory containing a SKILL.md file with YAML frontmatter defining a hyphenated name and a third-person description with trigger words. Keep the body concise, link optional reference.md or scripts one level deep, and verify terminology stays consistent.

What makes a good skill description for discovery?▼

A good description is third person, states what the skill does and when to use it, and includes trigger words users would say. Avoid vague phrases like "helps with documents"; instead name concrete tasks, formats, and scenarios.

Where should I put custom skills for Claude Code or Cursor?▼

Team-shared skills belong in .claude/plugins/n8n/skills/<name>/ so they are versioned and namespaced. Personal skills go in ~/.claude/skills/ for Claude Code or ~/.cursor/skills/ for Cursor, but never in ~/.cursor/skills-cursor/ which is reserved.

When should I split one skill into multiple smaller skills?▼

Split when triggers and steps diverge significantly, such as separate create-issue and create-PR workflows. Use small focused skills plus a thin parent orchestrator that links to each child SKILL.md instead of duplicating content.

How do I handle skills that require a specific MCP server?▼

State the requirement in the frontmatter description and add a Prerequisites block near the top naming the integration and its purpose. Always provide a fallback such as a CLI tool, web UI, or asking the user to paste data when the MCP is unavailable.