SKILLEMALL.ai
GitHub ↗ RU Sign in

BD report-writing

Bug bounty report writing for H1/Bugcrowd/Intigriti/Immunefi — report templates, human tone guidelines, impact-first writing, CVSS 3.1 scoring, title formula, impact statement formula, severity decision guide, downgrade counters, pre-submit checklist. Validation gates and the submittability/always-rejected decision are owned by triage-validation; this skill owns the written report itself (templates, tone, formulas). Use after validating a finding and before submitting. Never use "could potentially" — prove it or don't report.

elementalsouls/Claude-BugHunter Agent Skills author: elementalsouls 1 file body ≈ 5 084 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Bug bounty report writing for H1/Bugcrowd/Intigriti/Immunefi — report templates, human tone guidelines, impact-first writing, CVSS 3.1 scoring, title formula…

As a process D 45/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches

GeneratorData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
95
Quality 40%
77
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 5

✓ No critical or high findings

Medium and low: 5
  • low Risky intent intent-offensive-security SKILL.md:3
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    description: Bug bounty report writing for H1/Bugcrowd/Intigriti/Immunefi — report templates, human tone guidelines, impact-first writing, CVSS 3.1 scoring, title formula, impact statement formula, se
  • low Risky intent intent-offensive-security SKILL.md:38
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    Stored XSS in profile bio field executes in admin panel — allows privilege escalation
  • low Risky intent intent-offensive-security SKILL.md:328
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Privilege escalation from user to admin
  • low Risky intent intent-offensive-security SKILL.md:351
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    2. Allows account takeover or privilege escalation?             → +2 severity
  • low Risky intent intent-offensive-security SKILL.md:492
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - **`redteam-report-template`** — When the engagement is an external red team (NOT bug bounty). Workflow primitive: confirm engagement mode via `bb-methodology` PART 0; if red-team, swap this skill ou

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5084 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "sources"

Process rating: all ten parameters 45/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 3 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
  • 70Execution cost. Instruction body is 5084 tokens
  • 85Steps. 54 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low 16 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 531: enough signal without eating the budget
  • +4Structure: 33 headings
  • +3Step-by-step instructions: 54 items
  • +4Has examples (22 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.