Agent skill

analyze-script-failures

Analyze script failures to identify source components and propose fixes

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill analyze-script-failures --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/analysis/analyze-script-failures/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Analyze Script Failures Skill **EXECUTION MODE**: You are now executing this skill. DO NOT explain or summarize these instructions to the user. IMMEDIATELY begin the workflow below. Analyzes script failures from the current session to identify the source component, trace how instructions led to the failed call, and propose fixes. ## What This Skill Provides - Script failure detection from conversation history - Origin tracing (command/agent/skill that triggered failure) - Instruction path analysis (how LLM interpreted instructions) - Root cause categorization - Fix proposals with lessons learned integration ## When to Activate Activate when: - Script execution returns non-zero exit code - User asks to analyze script failures - Debugging why a script call failed ## Workflow: Analyze Script Failures ### Step 0: Load Foundation Skills ``` Skill: pm-plugin-development:plugin-architecture Skill: plan-marshall:diagnostic-patterns ``` These provide architecture principles and non-prompting tool usage patterns. ### Step 1: Gather Failure Data **A. Description Analysis** (if provided): - Parse user's description for specific failure context - Note: Which script, what error, expected behav

What's inside
Steps it walks through
  1. What This Skill Provides
  2. When to Activate
  3. Workflow: Analyze Script Failures
  4. Step 0: Load Foundation Skills
  5. Step 1: Gather Failure Data
  6. Step 2: For Each Failure Found
  7. Step 3: Root Cause Analysis
  8. Step 4: Generate Analysis Report
  9. Step 5: Propose Solutions
  10. Step 6: Interactive Resolution
  11. Step 7: Apply Selected Actions
  12. Step 8: Summary
  13. Critical Rules
  14. Non-Prompting Requirements
Ships with 1 file
  • metadata.json
Commands it runs
python3 .plan/execute-script.py plan-marshall:lessons-learned:manage-lesson add \
More from claude-skill-registry
All skills →
About this skill
What does the analyze-script-failures skill do?

Analyze script failures to identify source components and propose fixes

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill analyze-script-failures --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going