example-skill
Create automated task handlers
๋ํ ๋ค์์์ ์ฌ์ฉํ ์ ์์ต๋๋ค: anthropics,Joseph OBrien,ChaiWithJai,Joseph OBrien,ANcpLua
Users need reusable skills that activate automatically based on context. This template provides a starting point for building skills that perform specific tasks without manual invocation.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"example-skill" ์ฌ์ฉ ์ค์ ๋๋ค. Create a skill that helps with API documentation
์์ ๊ฒฐ๊ณผ:
- Skill Name: api-docs-helper
- Trigger: When user opens or modifies files with .api, .openapi, or .swagger extension
- Capabilities:
- - Analyzes API endpoint definitions
- - Validates request/response schemas
- - Generates documentation from code comments
- - Suggests improvements to API design
- Resources:
- - Scripts: api-analyzer.py, schema-validator.py
- - References: openapi-best-practices.md
- - Templates: api-doc-template.md
"example-skill" ์ฌ์ฉ ์ค์ ๋๋ค. Build a skill that validates configuration files
์์ ๊ฒฐ๊ณผ:
- Skill Name: config-validator
- Trigger: When user opens or modifies .json, .yaml, or .yml files
- Capabilities:
- - Parses configuration structure
- - Validates against schema definitions
- - Reports missing or invalid fields
- - Suggests corrections for common issues
๋ณด์ ๊ฐ์ฌ
์์ This is a documentation-only template skill containing no executable code. SKILL.md is a markdown file that describes skill structure and patterns. The static analysis scanner generated false positives by misinterpreting documentation references (script paths, URLs) as executable patterns. No actual code execution, network requests, or cryptographic operations exist in this skill.
์ํ ์์ธ
๐ ๋คํธ์ํฌ ์ ๊ทผ (1)
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (9)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Build new skills quickly
Use this template as a starting point for creating new Claude Code skills with proper structure.
Standardize skill format
Ensure all skills in a plugin follow consistent patterns using this template.
Document skill capabilities
Provide clear documentation for skill users with examples and usage patterns.
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Create a new skill called [skill-name] using the example-skill template. The skill should [describe what it does] and activate when [describe trigger conditions].
Add a new capability to [existing-skill] that [describes new functionality]. Reference best practices from the skill documentation.
Write clear documentation for [skill-name] including when it auto-invokes, what capabilities it provides, and how users should interact with it.
Define the exact conditions under which [skill-name] should auto-invoke, including file patterns, user queries, and detected situations.
๋ชจ๋ฒ ์ฌ๋ก
- Define clear trigger conditions so Claude knows when to auto-invoke the skill
- Keep capability descriptions specific and actionable, not generic
- Place actual scripts, references, and assets in their respective subdirectories
ํผํ๊ธฐ
- Leaving placeholder text like 'task X' or 'situation W' in published skills
- Declaring tools in allowed-tools without using them in the skill logic
- Creating skills that activate on too many conditions, causing context flooding
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
How is this different from an agent?
What tools can skills use?
Can skills execute scripts?
How do skills access their resources?
Are skills safe to install?
Can I modify an installed skill?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md