agentleFS
creanlabcreanlab/agent-genome-lab/.agents/skills/ticket-triage/SKILL.md

Ticket Triage and Routing

Skill2 starsChanged 4 months agoMITView on GitHub

Evaluate incoming user support tickets and route them to the proper department.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When operating in the support domain.

    line 13
  2. Distinctive:

    When resolving incidents related to ticket triage and routing.

    line 14
  3. Distinctive:

    If the issue requires manual human intervention.

    line 17
  4. Distinctive:

    If the domain does not apply.

    line 18
  5. Distinctive:

    Read the support ticket to extract key entities: user ID, error code, and affected feature.

    line 29
  6. Very specific:

    If it's a billing issue, route to billing.

    line 35
  7. Distinctive:

    Always verify changes in a staging environment before applying to production.

    line 48
  8. Distinctive:

    Do not execute destructive commands without explicit authorization.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ticket Triage and Routing

Evaluate incoming user support tickets and route them to the proper department.

When to use

  • When operating in the support domain.
  • When resolving incidents related to ticket triage and routing.

When not to use

  • If the issue requires manual human intervention.
  • If the domain does not apply.

Triggers

  • Pattern: ticket-triage
  • Keywords: support, ticket

Inputs

  • Context from the current user session or incident report.

Steps

1. Step 1

Read the support ticket to extract key entities: user ID, error code, and affected feature.

2. Step 2

Determine the severity: P1 (System Down), P2 (Major Bug), P3 (Minor Bug), P4 (Feature Request).

3. Step 3

If it's a billing issue, route to billing. If technical, route to engineering.

4. Step 4

Draft a polite acknowledgment message to the user confirming receipt and priority.

Success signals

  • The task is resolved without regressions.
  • Logs confirm the procedure was successfully applied.

Failure modes

  • Incorrect application of the steps leading to side effects.

Safety notes

  • Always verify changes in a staging environment before applying to production.
  • Do not execute destructive commands without explicit authorization.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.