agent-introspection-debugging
Skill1 starsChanged 33 days agoNo licenceView on GitHub
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
23 other projects use a version of this, 20 of them edited.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codeedited, first seen Nov 8, 2026
- ahmadvahidi/skill-atlasword for word, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemonedited, first seen Nov 6, 2026
- renepf/claude-skillsedited, first seen Oct 25, 2026
- davidanthonyn/claude-skillsedited, first seen Oct 20, 2026
- gongyijie85/dsh-eccword for word, first seen Oct 13, 2026
Used with
Projects with it also use unified-memory, brand-discovery and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
gongyijie85Skillunified-memory
Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.
Also in 3 projects that use this
ysyecustSkillbrand-discovery
Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).
Also in 3 projects that use this
ysyecustSkillcompetitive-platform-analysis
Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong to, and which sources to mine. First step in the three-skill competitive pipeline; precedes benchmark-methodology.
Also in 3 projects that use this
mturacSkillmle-workflow
Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.
Also in 4 projects that use this
InfopibeSkilleverything-claude-code
Also in 3 projects that use this
- +2 more from ysyecust
Other versions23 projects use a version of this.
Word for word · 3
- gongyijie85/dsh-ecc★ 8100% same
- NISTALTALSON/essential-claude-skills★ 1100% same
- ahmadvahidi/skill-atlas★ 0100% same
Edited · 20
- affaan-m/ECC★ 246k99% same
- mturac/everything-openai-codex★ 8999% same
- Fmarzochi/EGC★ 6198% same
- ysyecust/everything-claude-code★ 4499% same
- VoVuongThanhDat/agentflow★ 899% same
- yevhens-hue/claude-skills-starter-kit★ 415% same
- ArogyaReddy/https-github.com-affaan-m-everything-claude-code1★ 299% same
- bjornjee/skills★ 286% same
- JameMy0001/antigravity-skills-hub★ 192% same
- niloykumarbarman/EVERYTHING-CLAUDE-CODE★ 199% same
10 more not listed
Wrote their own version · 0
None found.
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 repository196 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/tech-leads-club/react-best-practices/AGENTS.mdAGENTS.md
- skills/tech-leads-club/react-composition-patterns/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adversarial-devSkill
- agent-creatorSkill
- skill-judgeSkill
- analyze-comfyui-workflow-jsonSkill
- algorithmic-artSkill
- docxSkill
- frontend-designSkill
- mcp-builderSkill
- pdfSkill
- skill-creatorSkill
- webapp-testingSkill
- xlsxSkill
- apk-reverseSkill
- author-claude-hookSkill
- auto-improveSkill
- codebase-linguistic-analysis-to-csv-exportSkill
- codebase-rules-extractorSkill
- code-reviewSkill
- compress-skillSkill
- consolidate-markdownSkill
- context7-documentation-lookupSkill
- context-mapSkill
- copilot-sdkSkill
- coverage-gap-auditSkill
- create-task-specSkill
- create-validation-scriptsSkill
- deep-research-webSkill
- design-image-diffSkill
- document-summarizerSkill
- dynamic-programming-analysisSkill
- event-stormingSkill
- agent-architecture-auditSkill
- agent-harness-constructionSkill
- agent-self-evaluationSkill
- ai-regression-testingSkill
- api-designSkill
- architecture-decision-recordsSkill
- autonomous-agent-harnessSkill
- autonomous-loopsSkill
- backend-patternsSkill
- blueprintSkill
- browser-qaSkill
- codebase-onboardingSkill
- coding-standardsSkill
- content-hash-cache-patternSkill
- cpp-coding-standardsSkill
- cpp-testingSkill
- database-migrationsSkill
- data-scraper-agentSkill
- deep-researchSkill
- deployment-patternsSkill
- dmux-workflowsSkill
- docker-patternsSkill
- e2e-testingSkill
- error-handlingSkill
- exa-searchSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 10 are common, 0 are distinctive, and 4 are very specific to this project.
10
Common
Most of the 20 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
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 measured: kept by at least 6 in 10 of the 20 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.
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.

