TopRank Skills
FR
English 简体中文 français

Rechercher

PythonReactSEOPDF
GitHub Skill

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

udacity☆ 1 Étoiles du dépôt1 Forks du dépôt
Voir la source ↗Installation

Installation

Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.

Voir la source ↗Guides

Instructions

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

  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

Exemples

Consultez les exemples du dépôt source.

Voir la source ↗

Historique source

Date d’indexation
2026-01-20
Mise à jour de l’index
2026-02-02
Branch
main

Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!