Automated summary

Triage an agent failure during a long-horizon run by querying the failure wiki for a known recovery before spending new tokens.

Strengths

Reduces token waste by reusing known recoveries.
Builds a self-improving knowledge base of failure modes.
Cites the failure_id for auditability.
Prefers concrete, locally executable recovery actions.

Limitations

Depends on a well-populated failure wiki (cold-start problem).
The default match threshold (0.82) may discard relevant matches.
Only covers failures that have a known recovery pattern.

When to use it

When an agent hits a failure in a long-running task and wants to reuse past recovery knowledge instead of solving from scratch.

When not to use it

When the failure is novel or the wiki is empty, or when recovery would require a high-level plan change not supported by the wiki.

Security analysis

Safe

Quality score90/100

The skill only uses the 'memory_search' tool, which is a read-only internal query. No external commands, network calls, or file system operations are performed. Recovery actions are logical steps, not system commands. No risk of data exfiltration or destruction.

No concerns found

How this analysis is made

Examples

Recover from empty subgraph

The traversal returned an empty subgraph after step 3. Use the failure wiki to find a recovery action and apply it.

Break a traversal cycle

I'm stuck in a traversal cycle in a long-horizon run. Query the failure wiki for a known recovery and follow it.

Low-confidence match

The last retrieval had low confidence. Check the failure wiki for a recovery from a similar low-confidence event.

description: Triage an agent failure during a long-horizon run by querying the failure wiki for a known recovery before burning new tokens. allowed-tools: memory_search

Instructions

Name: Agent Failure Triage via Wiki
Author: Skills Guide Bot

When the agent hits a failure during a long-horizon run (missing relation, ambiguous match, traversal cycle, low-confidence retrieval, empty subgraph, or unexpected result shape), do not attempt to solve it from scratch.

Build a failure signature from the symptom plus the last three traversal steps. Keep it short and concrete.
Query the failure wiki via memory_search using that signature. The wiki stores FailureMode, RecoveryAction, SolutionLog, and LintIssue nodes connected to past AgentQuery events.
If a wiki record matches above the configured threshold (default 0.82), apply its recovery_action directly. Cite the matched failure_id in the response so the next agent can audit the chain.
If no record matches, log a new FailureMode with confidence=0.4 and apply the default recovery for the symptom class. The lint pass will flag the new memory until a later run confirms the recovery is stable.
Always record a SolutionLog entry tying the failure_id to the recovery action and the run outcome. That log is what feeds the self-improvement loop.

Prefer recovery actions that are concrete and locally executable: backtrack to a sibling, re-rank by relationship count, fall back to semantic search, maintain a visited set, rephrase with synonyms, or return the node's raw description. Avoid recovery actions that require changing the agent's plan unless the wiki has a high-confidence example that did so successfully.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/agent-failure-triage-via-wiki-msfn193o/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/agent-failure-triage-via-wiki-msfn193o' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/agent-failure-triage-via-wiki-msfn193o/download' --output '.skill-downloads/agent-failure-triage-via-wiki-msfn193o/SKILL.md.part' && mv '.skill-downloads/agent-failure-triage-via-wiki-msfn193o/SKILL.md.part' '.skill-downloads/agent-failure-triage-via-wiki-msfn193o/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): memory_search

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/agent-failure-triage-via-wiki-msfn193o/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Create Interactive Maps with kepler.gl

Data & AI

Create interactive map visualizations and export standalone HTML using the keplergl Python package. Use to plot geospatial data from DataFrames, GeoJSON, or CSV.

Claude CodeCursorCodexintermediateSafe 11,995

Skills Guide Bot