agent-introspection-debugging

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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable instruction-only skill with clear sequencing, checklists, and feedback loops. Minor gains available by trimming framing prose and optionally splitting the diagnosis table or templates into a reference file.

Suggestions

Trim framing sentences like "This is a workflow skill, not a hidden runtime. It teaches the agent to debug itself systematically before escalating to a human." — the When to Activate section already conveys this.

Consider moving the pattern→cause→check diagnosis table into a references/diagnosis-patterns.md file to keep SKILL.md as a tighter overview and improve progressive disclosure.

The body repeats trigger conditions already in the description (loop-limit failures, retries with no progress); consolidate to avoid duplication and save tokens.

Dimension	Reasoning	Score
Conciseness	Lean and table/template-driven with little padding, but a few prose sentences (e.g. "This is a workflow skill, not a hidden runtime. It teaches the agent to debug itself systematically...") could be trimmed; not a 3 since most tokens earn their place.	4 / 5
Actionability	Copy-paste ready markdown templates (Failure Capture, Recovery Action, Self-Debug Report) plus a concrete pattern→cause→check diagnosis table; per the instruction-only scoring note, absence of code is not penalized when guidance is this concrete.	5 / 5
Workflow Clarity	A clearly sequenced Four-Phase Loop with checklists, an ordered Recovery Heuristics list, and an explicit feedback step ("change the plan only if the check supports it"); not a 4 because checkpoints and feedback loops are present.	5 / 5
Progressive Disclosure	Well-organized into clear sections and self-contained with no nested references, but it is longer than the 50-line simple-skill case and keeps everything inline rather than splitting any detail out, so it falls just short of the reference-split 5 anchor.	4 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states both capability and trigger, with concrete named phases and a distinctive niche. Adding common-synonym trigger terms (stuck, looping, no progress) would push trigger term quality to fully comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "capture, diagnosis, contained recovery, and introspection reports" — giving comprehensive coverage of the four phases; not the 3 anchor since there are clearly more than 1-2 actions.	5 / 5
Completeness	Explicitly answers both what ("Structured self-debugging workflow ... using capture, diagnosis, contained recovery, and introspection reports") and when ("Use when an agent run fails and you need a reproducible diagnosis instead of a retry") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases like "agent run fails" and "reproducible diagnosis instead of a retry" are present, but synonyms a user might say (e.g. "stuck", "looping", "no progress") are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (self-debugging of failed agent runs) with a distinct trigger unlikely to fire for unrelated skills; minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/agent-introspection-debugging/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.