CtrlK
BlogDocsLog inGet started
Tessl Logo

TODO-skill-name

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").

Invalid
This skill can't be scored yet
Validation errors are blocking scoring. Review and fix them to unlock Quality, Impact and Security scores. See what needs fixing →
SKILL.md
Quality
Evals
Security

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

LevelCriteriaResponse Time
TODOTODO: What makes a ticket this urgency?TODO
TODOTODO: What makes a ticket this urgency?TODO
TODOTODO: What makes a ticket this urgency?TODO
TODOTODO: 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

  1. TODO: First step
  2. TODO: Second step
  3. TODO: Third step
  4. TODO: Fourth step
  5. 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
Repository
udacity/cd14715-claude-code-classroom
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.