report

Convert triage.md and plan.md into structured markdown pentest reports.

18|3|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Kalp1774/akira --skill report-kalp1774
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report
Source: https://github.com/Kalp1774/akira/tree/main/skills/report
Command: npx skills add https://github.com/Kalp1774/akira --skill report-kalp1774

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts triage outputs and optional engagement plans into a polished, evidence-backed penetration test report or bug bounty submission so assessors can produce consistent deliverables without manual formatting or missed evidence checks. It enforces an evidence-gated workflow by requiring triage.md and optionally consuming plan.md to populate scope, findings, and reproduction steps.

Core Features & Use Cases

  • Automated Report Generation: Reads triage.md and optionally plan.md to produce a full markdown penetration test report with executive summary, findings table, and per-finding details.
  • Bug Bounty Mode: Produces HackerOne/Bugcrowd-friendly bug reports when requested, saving time when submitting to programs.
  • Evidence-Gated Findings: Requires direct tool output or evidence entries from triage to avoid hallucinated or unsupported findings.
  • Use Case: After completing an assessment, run the skill to transform triage artifacts into a dated report file stored under ~/pentest-toolkit/results/<target>/, ready for distribution or submission.

Quick Start

Write a full pentest report for target example.com using the saved triage.md and plan.md if available.

Frequently Asked Questions about report

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

FAQPage Schema
How do I convert triage output into a structured penetration test report?

To generate a penetration test report, provide your triage.md and optional plan.md files. The skill reads these artifacts to produce a full markdown report with an executive summary, findings table, and per-finding details, saving it to your results directory.

Can I generate a bug bounty submission for HackerOne or Bugcrowd from triage findings?

Yes, you can generate bug bounty submissions for HackerOne or Bugcrowd. By specifying bug bounty mode, the skill transforms your triage.md evidence into a formatted report file ready for direct submission to those platforms.

Do I need a plan.md file to generate a pentest report?

No, a plan.md file is optional. You must provide a triage.md file, but the skill will consume plan.md if available to populate scope and reproduction steps, ensuring a more comprehensive deliverable.

How does the report ensure findings are backed by actual evidence?

The report enforces an evidence-gated workflow by requiring direct tool output or evidence entries from your triage.md. This prevents hallucinated or unsupported findings from appearing in the final structured markdown.

Where are the generated pentest reports and bug bounty submissions saved?

Generated reports are saved as dated markdown files under the ~/pentest-toolkit/results/<target>/ directory. Filenames follow the report-<YYYY-MM-DD>.md or bugbounty-<YYYY-MM-DD>.md format for organized retrieval.