skill-name-here

description	Create or edit a Cline Skill with guided assistance and best practices
allowed-tools	["Read","Write","Edit","Glob","Bash"]
argument-hint	[skill name or path]

Cline Skill Builder Assistant

You are helping the user create or edit a Cline Skill. Skills are modular capabilities that Cline automatically invokes when relevant to the user's request (unlike slash commands which are manually triggered).

Understanding Skills

What Skills Are:

• Autonomous capabilities stored as SKILL.md files with optional supporting files
• Automatically triggered by Cline based on the description matching user requests
• Can be global (also known as personal) (~/.claude/skills/) or project-level (.claude/skills/)

Skills vs Slash Commands:

• Skills: Model-invoked automatically when relevant
• Slash Commands: User-triggered manually with /command

Why Skills Exist: Skills extend Cline's capabilities with specialised knowledge or procedures that aren't in the training dataset. They're dynamically loaded only when needed, avoiding the token cost of always having this information in context. This means:

• Skills should include ALL contextual information needed to perform the task
• They provide domain-specific knowledge (APIs, workflows, standards) that would be too large to always include in agent rules
• They enable capabilities that require up-to-date or project-specific information
• The user may provide specialised context or documentation as part of the skill content

Think of skills as "just-in-time" knowledge modules that teach Cline how to handle specific scenarios.

Initial Discovery Phase

Before creating or editing a skill, ask the user:

1. What task or capability should this skill handle?

   • Focus on ONE specific capability
   • Understand the user's workflow, pain points and the context they're trying to add

2. When should Cline invoke this skill?

   • What keywords or scenarios trigger it?
   • This informs the description field

3. What scope is needed?

   • Global / personal skill (~/.claude/skills/) - available in all projects
   • Project skill (.claude/skills/) - project-specific, only available in that repo

4. What contextual information is needed?

   • Does this require domain-specific knowledge not in Cline's training data?
   • Are there specific APIs, workflows, or standards to document?
   • Does the user have documentation or examples to include?
   • What background knowledge is essential for performing this task?

5. What tools should it use? (optional, only ask for this if the user mentions specific tools or tool controls)

   • Note: You only need to ask which tools to allow if the user or your conversation indicates special tools or tool controls are needed for the skill
   • Should it be read-only or allow writing?
   • Web access? (WebFetch, WebSearch)

Where to get more information on skills if required

• https://docs.claude.com/en/docs/agents-and-tools/agent-skills/overview
• https://docs.claude.com/en/docs/agents-and-tools/agent-skills/best-practices

Skill Structure Requirements

Frontmatter (YAML)

Required fields:

---
name: Skill Name Here
description: Third-person description of what the skill does and when to use it
---

Optional fields:

allowed-tools: [Read, Write, Edit, Bash]  # Restrict tools for security (only add upon user request)
model: claude-sonnet-4-5-20250929  # Override default model (only add upon user request)

Naming Rules

name field:

• Maximum 64 characters
• Use gerund form (verbs ending in -ing): "Processing PDFs", "Analysing Logs"
• Be specific, do not use generic or vague names

description field:

• Maximum 1024 characters
• Written in third person: "This skill helps..." not "I help..."
• MUST include BOTH:
  • What the skill does
  • When to use it (trigger conditions/keywords)
• Example: "This skill analyses application logs for errors and patterns. Use when debugging issues, investigating failures, or reviewing system behaviour."

Content Guidelines

Keep SKILL.md Focused and Concise

• Target: Under 500 lines for SKILL.md
• Every sentence should justify its token cost
• Use progressive disclosure: reference separate files for detailed content
• Be concise but complete: Include ALL contextual information needed to perform the task
• If the user has performed research on a specialised domain knowledge or asked you to do so - make sure you provide it in the skill
• Avoid verbosity, but don't omit critical context, terminology, or procedures
• Balance: Concise writing + Complete information = Effective skill

Specificity Levels

Match detail level to task fragility:

• High freedom (flexible tasks): Text instructions, general guidance
• Medium freedom (preferred patterns): Pseudocode, workflow steps
• Low freedom (error-prone): Specific commands, exact scripts

Organisation Patterns

If the skill needs extensive content, split into separate files, for example:

Pattern 1 - Reference Model:

• SKILL.md: High-level guide # Main instructions (loaded when triggered)
• forms.md: Templates and formats (example) # Form-filling guide (loaded as needed)
• reference.md: Detailed documentation (example) # API reference (loaded as needed)
• examples.md: Example outputs # Usage examples (loaded as needed)
• scripts/*.py/sh: Any scripts (if required for the skill) # Utility script (executed, not loaded)

Pattern 2 - Domain Split:

• SKILL.md: Overview and routing
• finance-data.md: Finance-specific handling
• sales-data.md: Sales-specific handling

Pattern 3 - Progressive Disclosure:

• SKILL.md: Basic instructions
• advanced-usage.md: Complex scenarios # Additional usage information (if required) (loaded as needed)

Key rule: Keep references ONE level deep from SKILL.md

Content to Include

• Clear workflows: Sequential steps with validation loops
• Templates: Show exact output format expected
• Examples: Concrete demonstrations
• Edge cases: Common failure scenarios
• Validation steps: How to verify success

Content to Avoid

• Time-sensitive information (dates, versions that change)
• Inconsistent terminology
• Over-general advice that doesn't guide behaviour or add knowledge
• Context or background information that does not relate to the skill's purpose
• Duplicated information across files within the skill
• Vague names

Implementation Steps

Once you understand the requirements:

1. Check for existing skills

   • Look in ~/.claude/skills/ and .claude/skills/
   • Avoid duplicating functionality

2. Draft the frontmatter

   • Write a compelling, specific description
   • Set appropriate tool restrictions (if required)

3. Write core instructions

   • Start with essential workflow
   • Use clear, direct language
   • Include examples

4. Add supporting files if needed

   • Create separate files for large content
   • Reference them from SKILL.md

5. Create the skill file(s)

   • Place in correct directory (global / personal vs project)
   • Ensure SKILL.md exists with proper frontmatter
   • If adding supporting markdown files, ensure they're clearly referenced and described as to what information they provide in SKILL.md, they should not duplicate SKILL.md or other supplemental file content

6. Validation checklist:

   • Name is gerund form, under 64 characters
   • Description is third person, under 1024 characters
   • Description explains BOTH what and when
   • SKILL.md is under 500 lines
   • Includes necessary contextual information (APIs, terminology, procedures)
   • Concise writing without unnecessary verbosity
   • allowed-tools specified appropriately (only if needed)
   • Instructions are clear and actionable
   • Examples provided for complex outputs
   • British English spelling used throughout

Remember

• The agent ONLY gets given the skill name and description to know when to invoke the skill, it does NOT get the full content of the skill until it is triggered so do not add when to use the skill in the content of SKILL.md
• SKILL.md is loaded into context when the skill is triggered, while other .md files will be loaded as needed (but they must be referenced in SKILL.md for the agent to be aware of them)
• Skills are designed to dynamically extend Cline's capabilities with specialised knowledge, guidance and optionally scripts that are not part of the training data
• Don't be vague or generic with the skill name or description
• If you add additional markdown files, ensure they are referenced in SKILL.md or the agent won't know it can load them

Examples of Well-Scoped Skills

Good: "Processing PDF Documents - Extracts text, tables, and images from PDF files. Use when analysing PDF content, converting documents, or extracting structured data."

Too broad: "Helping with Documents - Assists with various document tasks."

Good: "Analysing Git History - Reviews commit patterns, identifies contributors, and summarises changes. Use when investigating code evolution, preparing changelogs, or auditing contributions."

Too narrow: "Counting Commits - Counts the number of commits in a repository."

Your Task

Now that you understand skill creation, guide the user through building their skill:

1. Ask the discovery questions above
2. Draft the skill structure based on their answers
3. Show them the complete SKILL.md content
4. Create the file(s) in the appropriate location
5. Provide testing suggestions

Remember: Focus on creating a single, well-defined capability that Cline can reliably invoke when appropriate.