evidence-first-troubleshooting
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Diagnose errors from third-party products, integrations, or SaaS by checking error text → product version/changelog → vendor docs → branded forums → product logs FIRST, before reasoning. Use this skill whenever Aaron reports an error from any external system: PandaDoc, Salesforce managed packages, Gong, Stripe, n8n, HubSpot, Sigma, an npm package, a browser extension, a vendor API, or any tool with public documentation. Trigger even if Aaron just pastes an error message without an explicit help request, describes a broken integration ('X is throwing Y', 'Z says it can't connect', 'the integration is broken'), or shares a screenshot of a vendor error UI. Trigger proactively — undertriggering wastes hours of reasoning that vendor docs would resolve in minutes. Do NOT trigger for logic bugs in code Aaron wrote himself, pure SQL/SOQL syntax questions, or open-ended design discussions where no error message exists.
In this repository8 other files it gives its agents.
- dev-sparkSkill
- exec-requestsSkill
- humanizerSkill
- nntSkill
- session-reflectSkill
- sigma-computingSkill
- spec-kitSkill
- web-perfSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.