← Back to list

todo-skill-name
by udacity
This repo contains the classroom material for Claude Code (Agent SDK) course.
⭐ 0🍴 1📅 Jan 23, 2026
SKILL.md
name: TODO-skill-name description: TODO - Describe when to use this skill. Make it specific so Claude knows when to apply it (e.g., "Classify support tickets by urgency and category. Use when analyzing tickets, determining priority, or routing customer requests"). allowed-tools: TODO, TODO
TODO: Skill Title
This skill teaches Claude how to TODO.
When to Use This Skill
Use this skill when the user requests:
- "TODO: Example phrase 1"
- "TODO: Example phrase 2"
- "TODO: Example phrase 3"
Classification Matrix
Urgency Levels
| Level | Criteria | Response Time |
|---|---|---|
| TODO | TODO: What makes a ticket this urgency? | TODO |
| TODO | TODO: What makes a ticket this urgency? | TODO |
| TODO | TODO: What makes a ticket this urgency? | TODO |
| TODO | TODO: What makes a ticket this urgency? | TODO |
Urgency Keywords
TODO urgency indicators:
- TODO: List keywords (e.g., "system down", "outage")
- TODO: More keywords
TODO urgency indicators:
- TODO: List keywords
- TODO: More keywords
TODO urgency indicators:
- TODO: List keywords
- TODO: More keywords
TODO urgency indicators:
- TODO: List keywords
- TODO: More keywords
Category Classification
TODO Category:
- TODO: What indicates this category?
- TODO: More indicators
TODO Category:
- TODO: What indicates this category?
- TODO: More indicators
TODO Category:
- TODO: What indicates this category?
- TODO: More indicators
Classification Process
- TODO: First step
- TODO: Second step
- TODO: Third step
- TODO: Fourth step
- TODO: Fifth step
Examples
Example 1: TODO - Category - Urgency Level
Subject: TODO
Body: TODO - Write a realistic ticket example
Classification:
- Urgency: TODO
- Category: TODO
- Routing: TODO
- Reasoning: TODO
Example 2: TODO - Category - Urgency Level
Subject: TODO
Body: TODO - Write a realistic ticket example
Classification:
- Urgency: TODO
- Category: TODO
- Routing: TODO
- Reasoning: TODO
Example 3: TODO - Category - Urgency Level
Subject: TODO
Body: TODO - Write a realistic ticket example
Classification:
- Urgency: TODO
- Category: TODO
- Routing: TODO
- Reasoning: TODO
Output Format
TODO: Explain output structure
{
"urgency": "TODO",
"category": "TODO",
"routing": "TODO",
"customer_tier": "TODO",
"sla_deadline": "TODO"
}
Quality Checklist
Before finalizing classification, verify:
- TODO: First check
- TODO: Second check
- TODO: Third check
- TODO: Fourth check
Tips
Finding urgency indicators:
- TODO: Tip 1
- TODO: Tip 2
Categorizing accurately:
- TODO: Tip 1
- TODO: Tip 2
Routing decisions:
- TODO: Tip 1
- TODO: Tip 2
Common Pitfalls
❌ Don't:
- TODO: Common mistake 1
- TODO: Common mistake 2
- TODO: Common mistake 3
✅ Do:
- TODO: Best practice 1
- TODO: Best practice 2
- TODO: Best practice 3
Score
Total Score
60/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon