reporting

Generate Markdown post-CTF reports with challenge details and save via note naming.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hanc00l/nemo-agent --skill reporting-hanc00l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reporting
Source: https://github.com/hanc00l/nemo-agent/tree/main/claude-code/.claude/skills/pentest/core/reporting
Command: npx skills add https://github.com/hanc00l/nemo-agent --skill reporting-hanc00l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts completed CTF challenge results and notes into a consistent, shareable Markdown report so investigators do not need to assemble findings manually.

Core Features & Use Cases

  • Automated report template with required fields: challenge name, target URL, test date, elapsed time, and flag.
  • Structured sections for step-by-step attack narrative, discovered vulnerabilities, resource usage, and a summary.
  • Saves reports into the agent's note system using a predictable naming convention for easy retrieval.
  • Use case: After solving a challenge, produce a reproducible report for team handoff, writeups, or post-mortem analysis.

Quick Start

Generate a full Markdown CTF report for a completed challenge including challenge_name, target_url, flag, steps_summary, vulns_found, and elapsed_time and save it using the reporting skill.

Frequently Asked Questions about reporting

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

FAQPage Schema
How do I auto-generate a Markdown report for a completed CTF challenge?

To auto-generate a CTF Markdown report, input your challenge details including the name, target URL, flag, and elapsed time. The reporting skill assembles these into a structured Markdown document with step-by-step actions and vulnerabilities.

What is the standard format for writing CTF writeups and pentest findings?

A standard CTF writeup format includes the challenge name, target URL, test date, elapsed time, flag, detailed attack steps, and vulnerability descriptions. This structure ensures reproducible documentation for post-mortem analysis.

Can I automatically save generated CTF reports into my notes system?

Yes, you can save generated CTF reports directly into your notes system. The reporting skill uses the toolset.note.save_note naming pattern with a YYYYMMDD suffix to ensure predictable retrieval and storage.

Does automated reporting require manually documenting step-by-step vulnerability findings?

No, automated reporting eliminates manual documentation by structuring your input into a comprehensive narrative. You provide the raw steps and discovered vulnerabilities, and the skill formats them into a complete Markdown report.

What sections are needed when documenting a solved CTF challenge for team handoff?

Documenting a solved CTF challenge for team handoff requires sections for challenge details, target URL, test date, elapsed time, flag, step-by-step attack narrative, discovered vulnerabilities, resource usage, and a summary.