reflect-appworld-failure

reflect-appworld-failure is a skill for Claude Code from jmanhype/claude-code-plugin-marketplace. It costs 26 tokens per session (1,611 once invoked), scanned A, original, MIT.

A failure-analysis skill for AppWorld, a benchmark where agents complete tasks through app APIs. It turns failed tasks, errors, and code into reusable guidance with examples and tags.

In plain words
What is it for?
Use it after an AppWorld task fails to identify the root cause and document the correct API pattern. It can produce playbook bullets with fixes, code examples, tags, and confidence levels.
Why use it?
It helps recover lessons from failed API work instead of losing them. The resulting guidance can help avoid repeating the same mistakes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the ace-context-engineering plugin — 3 skills shipped together

Good fit Use it after an AppWorld task fails to identify the root cause and document the correct API pattern. It can produce playbook bullets with fixes, code examples, tags, and confidence levels.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jmanhype/claude-code-plugin-marketplace/reflect-appworld-failure
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jmanhype/claude-code-plugin-marketplace --skill reflect-appworld-failure
Clone the repo
git clone --depth 1 https://github.com/jmanhype/claude-code-plugin-marketplace

Made for: Claude Code.

Or install ace-context-engineering, the plugin that ships this one along with the rest of its 3 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for reflect-appworld-failure

README.md
[![agentmods](https://agentmods.dev/badge/skills/jmanhype/claude-code-plugin-marketplace/reflect-appworld-failure/github.svg)](https://agentmods.dev/skills/jmanhype/claude-code-plugin-marketplace/reflect-appworld-failure)
Your own site
<a href="https://agentmods.dev/skills/jmanhype/claude-code-plugin-marketplace/reflect-appworld-failure"><img src="https://agentmods.dev/badge/skills/jmanhype/claude-code-plugin-marketplace/reflect-appworld-failure/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for reflect-appworld-failure

Your own site · 80×15
<a href="https://agentmods.dev/skills/jmanhype/claude-code-plugin-marketplace/reflect-appworld-failure"><img src="https://agentmods.dev/badge/skills/jmanhype/claude-code-plugin-marketplace/reflect-appworld-failure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.01611
Opus 5 $0.00013 $0.00805
Sonnet 5 $0.00005 $0.00322
Haiku 4.5 $0.00003 $0.00161

Measured 10d ago against content hash 6857a4c0f5df, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

reflect-appworld-failure scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/ace-context-engineering/skills/reflect-appworld-failure/SKILL.md · 201 lines

How it starts

The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reflect on AppWorld Failure

Analyze failed AppWorld tasks to extract specific, actionable learnings that can be added to the playbook.

Purpose

When an AppWorld task fails, the Reflector calls this Skill with error details and failed code. You analyze the failure semantically and generate a high-quality bullet with:

  1. Specific title describing the pattern
  2. Detailed content with working code examples
  3. Relevant tags for retrieval
  4. Appropriate confidence level

Input Format

The input will be a text description with sections:

# Task
<task instruction>

## Apps
<comma-separated list of apps used>

## Error Type
<error_type: api_misuse, logic_error, timeout, etc.>

## Error Messages
<list of error messages from execution>

## Failed Code Snippet
<relevant code that failed>

## Missing Patterns (from heuristics)
<list of patterns the old system identified>

## Suggested Fixes (from heuristics)
<list of fix suggestions>

Your Analysis Process

  1. Identify Root Cause: What was the fundamental mistake?

    • Wrong API method name?
    • Missing authentication?
    • Incorrect data structure access?
    • Logic error?
  2. Extract Pattern: What general pattern does this represent?

    • Is this specific to one app or applies to multiple?
    • Is this about API order (login first)?
    • Is this about method naming conventions?
    • Is this about data validation?
  3. Generate Concrete Example: Create working code that demonstrates the CORRECT pattern

  4. Write Actionable Bullet: Make it specific enough that the Generator can apply it

Output Format

Return a JSON object with this structure:

{
  "bullet": {
    "id": "bullet-YYYY-MM-DD-HHMMSS",
    "title": "<Specific pattern title>",
    "content": "<Detailed explanation with working code example>",
    "tags": ["app.<app_name>", "<error_category>", "<pattern_type>"],
    "evidence": [
      {
        "type": "execution",
        "ref": "<task_id>",
        "note": "<brief note about failure>"
      }
    ],
    "confidence": "high|medium|low",
    "scope": "app|global"
  }
}

Read the full file on GitHub · 201 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 201 lines · 26 tokens per session scan A 6857a4c0f5df

Subscribe to this mod's changes

reflect-appworld-failure is a skill published in the GitHub repository jmanhype/claude-code-plugin-marketplace (27 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,611 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens