ctf-postmortem

Analyzes CTF challenge logs to compute solve rates and diagnose systemic failure root causes.

545|48|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/yhy0/CHYing-agent --skill ctf-postmortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctf-postmortem
Source: https://github.com/yhy0/CHYing-agent/tree/main/.claude/skills/ctf-postmortem
Command: npx skills add https://github.com/yhy0/CHYing-agent --skill ctf-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a CTF competition, it is hard to tell whether failures came from individual hard challenges or from systemic weaknesses in the agent's architecture. This Skill reads the agent's challenge working directories, computes solve-rate statistics, and converts raw logs into prioritized, system-level improvement recommendations.

Core Features & Use Cases

  • Solve-rate statistics: Scans all challenge directories under agent-work/ctf/, detects solved flags in progress.md and findings.log, and produces per-category solve-rate tables.
  • Failure diagnosis: For each unsolved challenge, extracts stop reason, final phase, dead ends, tool usage patterns, and knowledge-base search behavior.
  • Root-cause classification: Maps failures to ten systemic root-cause codes (e.g., KB_MISS, JS_BLIND, LOOP_SAME_VECTOR) and outputs P0-P3 prioritized optimization suggestions tied to concrete system components.
  • Use Case: After a competition, run the analysis to discover that three unsolved challenges had version numbers but never triggered a knowledge-base search, then get a P0 recommendation to fix the kb_search trigger conditions in the orchestrator prompt.

Quick Start

Analyze this competition's results and tell me which system components need improvement.

Frequently Asked Questions about ctf-postmortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze CTF agent failure logs after a competition?

Point the analysis at the agent-work/ctf/ directory containing per-challenge folders. The workflow scans progress.md and findings.log files, computes solve rates per category, then diagnoses each unsolved challenge by stop reason, dead ends, and tool usage patterns.

What root causes does CTF postmortem analysis detect?

It classifies failures into ten systemic codes including TARGET_UNREACHABLE, TOOL_GAP, KB_MISS, JS_BLIND, LOOP_SAME_VECTOR, PARTIAL_CHAIN, TIMEOUT_TOO_EARLY, RECON_SHALLOW, REFLECT_MISSED, and SESSION_REPEAT, each with defined detection signals from the logs.

How are solve rates computed from challenge logs?

A challenge counts as solved when progress.md contains a FLAG{ or flag{ string, or findings.log contains a kind: flag entry. Results are aggregated into a per-category table showing totals, solves, and solve percentages.

Can this analysis suggest fixes for individual challenges?

No, the analysis is deliberately system-level only. It never recommends how to solve a specific challenge; instead it identifies patterns across multiple failures and maps them to concrete system components like the orchestrator prompt or reflection tracker.

How are optimization recommendations prioritized?

Recommendations use P0-P3 priorities based on blast radius: P0 affects three or more challenges with a clear fixable component, P1 affects two challenges or one severe case, P2 affects one challenge with low fix cost, and P3 covers general improvements.