ticket-intake
Skill0 starsChanged 36 days agoMITView on GitHub
Normalize a raw support ticket into structured investigation inputs.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- aniketshukla1/sdlc-kittheir own version, first seen Nov 8, 2026
- neomjs/neo-agent-skillstheir own version, first seen Nov 8, 2026
- ohyesgocool/feature-looptheir own version, first seen Jul 28, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- neomjs/neo-agent-skills★ 11same name
- aniketshukla1/sdlc-kit★ 1same name
- ohyesgocool/feature-loop★ 0same 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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- escalationSkill
- kb-articleSkill
- known-issue-searchSkill
- log-evidenceSkill
- redactionSkill
- reproduction-stepsSkill
- response-draftingSkill
- support-triageSkill
- triage-reportSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill first for every ticket.
- Distinctive: line 15
Timeframe: when it started, whether it is ongoing, and any deployment/version correlation.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ticket Intake
Use this skill first for every ticket.
Extract
- Issue type: bug, how-to, feature request, account, integration, data, performance, other.
- Product area: the smallest meaningful product/component area.
- Customer impact: who is affected and how badly.
- Timeframe: when it started, whether it is ongoing, and any deployment/version correlation.
- Environment: browser, mobile OS, backend language, SDK/library, versions, region, plan, hosting setup.
- Identifiers: safe ticket IDs, event names, flag keys, background task IDs, error fingerprints, request IDs. Redact secrets and private user data.
- Reproduction: steps, expected behavior, actual behavior, frequency.
- Missing context: the smallest next pieces of information needed to confirm or reject the leading hypothesis.
Output
## Intake
| Field | Value |
|---|---|
| Issue Type | ... |
| Product Area | ... |
| Timeframe | ... |
| Impact | ... |
| Environment | ... |
| Identifiers | ... |
| Reproduction | ... |
| Missing Context | ... |
## First Investigation Paths
1. ...
2. ...
3. ...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
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.