| name | template-skill |
|---|---|
| description | Replace with a clear description of what this skill does and when Claude should use it. Be specific about the use cases, tools, or workflows this skill addresses. |
Brief introduction explaining what this skill helps users accomplish.
Use this skill when:
- Specific use case 1
- Specific use case 2
- Specific use case 3
Explanation of the first important concept or pattern.
Example:
# Show concrete example
key: valueExplanation of the second important concept.
-- SQL example if relevant
SELECT * FROM table_nameContinue with other important concepts, patterns, or best practices.
# Show a complete, realistic example
example:
key: value
nested:
- item1
- item2Explanation: Describe what this pattern does and when to use it.
Provide another common use case with example code.
- Practice 1 - Clear guideline
- Practice 2 - Another guideline
- Practice 3 - And so on
Symptoms:
- What the user sees
- Error messages
Solutions:
- First solution approach
- Alternative approach
- Workaround if needed
Example:
# Show the fix
corrected:
example: hereFor users who need more sophisticated functionality.
Additional advanced patterns or techniques.
Step-by-step example of a complete workflow:
- Step 1: Do this first
- Step 2: Then do this
- Step 3: Finally complete with this
# Complete working example
complete:
workflow:
step1: value
step2: value- Link to related skill if applicable
- Another related skill
- Official documentation links
- Internal TD resources
- Related tools or services
When creating a new skill from this template:
-
Update the frontmatter:
- Change
nameto your skill's unique identifier (lowercase-with-hyphens) - Write a clear
descriptionthat explains when Claude should use this skill
- Change
-
Replace the content:
- Update the main heading
- Fill in "When to Use This Skill" with specific scenarios
- Add core principles and concepts specific to your domain
- Provide realistic, working examples
- Include common patterns from your area of expertise
-
Focus on TD-specific patterns:
- Include TD conventions and best practices
- Reference internal tools and workflows
- Use realistic TD table names and data patterns
- Include timezone considerations (JST/UTC)
-
Make it actionable:
- Provide complete, copy-paste-ready examples
- Include error handling patterns
- Show debugging approaches
- Add troubleshooting sections
-
Keep it maintainable:
- Add version comments if tracking changes
- Include last updated date
- Link to authoritative documentation
- Note any TD-specific limitations or requirements
-
Test your skill:
- Verify all examples work
- Test with Claude Code
- Get feedback from potential users
- Update based on real-world usage