agent introspection debugging

AI Community

Skill notes

When to Activate

Maximum tool call / loop-limit failures Repeated retries with no forward progress Context growth or prompt drift that starts degrading output quality File-system or environment state mismatch between expectation and reality Tool failures that are likely recoverable with diagnosis and a smaller corrective action

Scope Boundaries

Activate this skill for: capturing failure state before retrying blindly diagnosing common agent-specific failure patterns applying contained recovery actions producing a structured human-readable debug report

Phase 1: Failure Capture

Before trying to recover, record the failure precisely. Capture: error type, message, and stack trace when available last meaningful tool call sequence what the agent was trying to do

Phase 2: Root-Cause Diagnosis

Match the failure to a known pattern before changing anything. Pattern · Likely Cause · Check Maximum tool calls / repeated same command · loop or no-exit observer path · inspect the last N tool calls for repetition Context overflow / degraded reasoning · unbounded notes, repeated plans, oversized logs · inspect recent context for duplication and low-signal bulk ECONNREFUSED / timeout · service unavailable or wrong port · verify service health, URL, and port assumptions

Phase 3: Contained Recovery

Recover with the smallest action that changes the diagnosis surface. Safe recovery actions: stop repeated retries and restate the hypothesis trim low-signal context and keep only the active goal, blockers, and evidence re-check the actual filesystem / branch / process state

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@affaan-m · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Failure Capture

Before trying to recover, record the failure precisely. Capture: error type, message, and stack trace when available last meaningful tool call sequence what the agent was trying to do

02
Phase 2: Root-Cause Diagnosis

Match the failure to a known pattern before changing anything. Pattern · Likely Cause · Check Maximum tool calls / repeated same command · loop or no-exit observer path · inspect the last N tool calls for repetition Context overflow / degraded reasoning · unbounded notes, repeated plans, oversized logs · inspect recent context for duplication and low-signal bulk `ECONNREFUSED` / timeout · service unavailable or wrong port · verify service health, URL, and port assumptions

03
Phase 3: Contained Recovery

Recover with the smallest action that changes the diagnosis surface. Safe recovery actions: stop repeated retries and restate the hypothesis trim low-signal context and keep only the active goal, blockers, and evidence re-check the actual filesystem / branch / process state

04
Phase 4: Introspection Report

End with a report that makes the recovery legible to the next agent or human.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.