<< All versions

Skill v1.0.0

currentLLM-judged scan90/100
neeharikarn/neeha-bounded-autonomy-and-guardrails-with-claude-and-claude-code/ticket-classification
──Details
PublishedOctober 23, 2026 at 02:35 AM
Content Hashsha256:a54b46e6b70c34e0...
Git SHAa9f90a590d5c
──Files
Files (1 file, 3.5 KB)
SKILL.md3.5 KBactive
SKILL.md · 181 lines · 3.5 KB

version: "1.0.0" 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

<!-- TODO: Write an introduction explaining what this skill teaches -->

This skill teaches Claude how to TODO.

When to Use This Skill

<!-- TODO: List triggering phrases -->

Use this skill when the user requests:

  • "TODO: Example phrase 1"
  • "TODO: Example phrase 2"
  • "TODO: Example phrase 3"

Classification Matrix

<!-- TODO: Create a classification matrix for urgency levels -->

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: List keywords that indicate each urgency level -->

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: Define how to categorize tickets -->

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: Write step-by-step classification instructions -->

  1. TODO: First step
  2. TODO: Second step
  3. TODO: Third step
  4. TODO: Fourth step
  5. TODO: Fifth step

Examples

<!-- TODO: Provide at least 3 classification 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: Define how classification results should be formatted -->

TODO: Explain output structure

json
{
  "urgency": "TODO",
  "category": "TODO",
  "routing": "TODO",
  "customer_tier": "TODO",
  "sla_deadline": "TODO"
}

Quality Checklist

<!-- TODO: Add a checklist for quality classification -->

Before finalizing classification, verify:

  • [ ] TODO: First check
  • [ ] TODO: Second check
  • [ ] TODO: Third check
  • [ ] TODO: Fourth check

Tips

<!-- TODO: Add helpful 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

<!-- TODO: List common mistakes to avoid -->

❌ 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
All versions