agentleFS
Sign inStart free
c-monganc-mongan/support-triage-agent-template/skills/triage-report/SKILL.md

triage-report

Skill0 starsChanged 36 days agoMITView on GitHub

Produce a structured, evidence-graded support triage report.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. yxy050208/qwen-security-copilot★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Use references/triage-report-template.md (in this skill's directory) as the canonical report structure.

    line 8
  2. Distinctive:

    Every important claim must map to a source.

    line 12
  3. Distinctive:

    Keep the customer response free of internal-only detail.

    line 16
  4. Distinctive:

    Before considering the report done:

    line 27
  5. Distinctive:

    Verify that the root-cause confidence matches the evidence.

    line 29
  6. Distinctive:

    Check that all sensitive data is redacted.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Triage Report

Use references/triage-report-template.md (in this skill's directory) as the canonical report structure. Keep its section headings unchanged: the CI structure check and downstream tooling rely on them.

Rules

  • Every important claim must map to a source.
  • Separate customer-provided facts from facts independently verified by tools.
  • Include rejected hypotheses when they prevent repeated work.
  • Include unknowns instead of hiding uncertainty.
  • Keep the customer response free of internal-only detail.
  • Escalate when support cannot verify or resolve the issue with available evidence.

Confidence

  • Confirmed by data: direct evidence from the customer's own system (logs, events, traces, account state or a reproduction) proves the cause. Docs, release notes or a matching known issue alone are not enough; use Likely.
  • Likely based on pattern match: the evidence points strongly to one cause, but one or more facts remain unverified.
  • Suspected, needs human verification: plausible, but not enough evidence to act as if true.

Pre-Send Check

Before considering the report done:

  1. Verify that the root-cause confidence matches the evidence.
  2. Check that all sensitive data is redacted.
  3. Confirm that known-issue search includes at least two symptom-specific queries for bug-shaped tickets.
  4. Confirm that the recommended next action is specific and minimal.

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.

Check your setup, free