Identify Key Failures

What it does

When your agent uses it

• The current batch of decomposition plans has failed — whether they failed already at direct proving
• Only after further attempts

Example prompts

• “/identify-key-failures”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Gather the reports from all failed plans. If only direct proving has run so far, work directly from the direct-proving failures.
2. 2List the key stuck points for each plan.
3. 3Identify common points across those failures
4. 4Summarize what the failures suggest for the next generation of decomposition plans.
5. 5When all current decomposition plans have failed and no pattern is leading anywhere, publish the synthesized dead_end (below): the main…
6. 6Save the synthesized failure knowledge to failed_paths so later planning skills can use it.
7. 7After recording the failure synthesis, return control to $propose-subgoal-decomposition-plans.

What it can do on your machine

Read from SKILL.md and the folder at commit 6d92e8d. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Identify Key Failures loads about 586 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 248 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~58

When it runs · the whole SKILL.md, loaded when a task matches

~586

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from frenzymath/Danus at commit 6d92e8d, republished under its Apache-2.0 licence (© frenzymath). 248 words, ~586 tokens.

name

identify-key-failures

description

Synthesize the common stuck points across failed decomposition plans. Use when the current batch of decomposition plans has failed — whether they failed already at direct proving or only after further attempts.

{
  "record_type": "key_failures_summary",
  "failed_plan_ids": ["..."],
  "plan_failures": [
    {
      "plan_id": "...",
      "stuck_points": ["..."]
    }
  ],
  "common_failures": ["..."],
  "implications_for_next_plans": ["..."]
}

© frenzymath, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in agents/skills/worker/identify-key-failures of frenzymath/Danus.

• SKILL.md
• agents/openai.yaml

Open the folder on GitHubat commit 6d92e8d