CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-introspection-debugging/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The content is a well-organized, actionable four-phase self-debugging workflow with templates, a diagnosis table, and feedback-loop guidance. It is concise and clearly sequenced, with only minor gaps in explicit validation framing and no need for external bundle files.

DimensionReasoningScore

Conciseness

The body is lean and well-structured with templates, a diagnosis table, and checklists; nearly every section earns its place, with only minor framing prose ('Before trying to recover, record the failure precisely') that could be trimmed, so it sits just below the fully lean anchor 5.

4 / 5

Actionability

Copy-paste-ready markdown templates, a specific pattern→cause→check diagnosis table, and a concrete ordered recovery-heuristics list give mostly executable guidance; actions are framed as directives rather than literal commands, leaving minor gaps vs anchor 5.

4 / 5

Workflow Clarity

A clearly sequenced four-phase loop (Capture→Diagnosis→Recovery→Report) with checklists and a described feedback loop ('run one direct check → change the plan only if the check supports it') is present, but validation checkpoints are embedded in templates rather than explicit numbered steps as in the anchor 5 example.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clearly headed sections (When to Activate, Scope Boundaries, Four-Phase Loop, Recovery Heuristics, Integration with ECC, Output Standard) with external skill references signaled clearly; at ~150 lines with no bundle files it is appropriately single-file but exceeds the under-50-line simple-skill exception, so it does not reach anchor 5.

4 / 5

Total

16

/

20

Passed

Description

58%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.

The description clearly states what the skill does and lists concrete phases, but it omits any 'Use when...' trigger guidance and lacks the natural user phrasing that would drive reliable activation. It is distinct but under-specified on the 'when'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when an agent run is looping, burning tokens without progress, or failing repeatedly on the same tools.'

Include natural user-facing synonyms such as 'agent stuck', 'agent looping', 'token burn', or 'no forward progress' alongside the technical terms.

Rephrase the action list as concrete verbs ('capture failure state, diagnose root cause, apply contained recovery, produce introspection report') to push specificity toward anchor 5.

DimensionReasoningScore

Specificity

Names the domain ('AI agent failures') and lists several concrete phases — 'capture, diagnosis, contained recovery, and introspection reports' — but the actions are phrased as abstract nouns rather than fully concrete verbs, leaving minor coverage gaps vs the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or any explicit trigger guidance; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant domain keywords ('self-debugging', 'agent failures', 'recovery') are present, but the natural phrases a user would actually say ('agent stuck', 'agent looping', 'burning tokens') are missing and no synonyms or variations are included.

3 / 5

Distinctiveness Conflict Risk

'Self-debugging workflow for AI agent failures' carves a fairly distinct niche with low overlap risk, though absence of explicit triggers leaves minor overlap risk with general debugging skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ysyecust/everything-claude-code
Reviewed

Table of Contents

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.