Web3 Triage and Report Examples
tradecatlabs/vibe-coding-cn
Seven-question triage gate, Immunefi report format and dissected paid bounty examples for deciding whether a smart contract finding is worth submitting.
Write a disclosure-quality bug bounty report for a finding, matching the HackerOne report format used in this repo's corpus.
Install Write Report
$ npx skills add bugbountywithmarco/bugbounty-disclosed-reports --skill write-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bugbountywithmarco/bugbounty-disclosed-reports write-report --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bugbountywithmarco/bugbounty-disclosed-reports.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/write-report .claude/skills/write-report && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "write-report" agent skill from https://github.com/bugbountywithmarco/bugbounty-disclosed-reports/tree/main/.claude/skills/write-report into .claude/skills/write-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-report", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bugbountywithmarco/bugbounty-disclosed-reports/tree/main/.claude/skills/write-reportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bugbountywithmarco/bugbounty-disclosed-reports --skill write-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bugbountywithmarco/bugbounty-disclosed-reports write-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bugbountywithmarco/bugbounty-disclosed-reports.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/write-report .agents/skills/write-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-report" agent skill from https://github.com/bugbountywithmarco/bugbounty-disclosed-reports/tree/main/.claude/skills/write-report into .agents/skills/write-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-report", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bugbountywithmarco/bugbounty-disclosed-reports --skill write-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bugbountywithmarco/bugbounty-disclosed-reports write-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bugbountywithmarco/bugbounty-disclosed-reports.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/write-report .cursor/skills/write-report && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-report" agent skill from https://github.com/bugbountywithmarco/bugbounty-disclosed-reports/tree/main/.claude/skills/write-report into .cursor/skills/write-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-report", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bugbountywithmarco/bugbounty-disclosed-reports.git --path .claude/skills/write-report--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bugbountywithmarco/bugbounty-disclosed-reports --skill write-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bugbountywithmarco/bugbounty-disclosed-reports write-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bugbountywithmarco/bugbounty-disclosed-reports.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/write-report .gemini/skills/write-report && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "write-report" agent skill from https://github.com/bugbountywithmarco/bugbounty-disclosed-reports/tree/main/.claude/skills/write-report into .gemini/skills/write-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-report", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bugbountywithmarco/bugbounty-disclosed-reports write-reportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bugbountywithmarco/bugbounty-disclosed-reports --skill write-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bugbountywithmarco/bugbounty-disclosed-reports.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/write-report .github/skills/write-report && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "write-report" agent skill from https://github.com/bugbountywithmarco/bugbounty-disclosed-reports/tree/main/.claude/skills/write-report into .github/skills/write-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-report", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bugbountywithmarco/bugbounty-disclosed-reports --skill write-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bugbountywithmarco/bugbounty-disclosed-reports write-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bugbountywithmarco/bugbounty-disclosed-reports.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/write-report .opencode/skills/write-report && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-report" agent skill from https://github.com/bugbountywithmarco/bugbounty-disclosed-reports/tree/main/.claude/skills/write-report into .opencode/skills/write-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-report", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
write-report- GitHub stars
- 122
- Token cost
- ~585 tokens
- SKILL.md length
- 147 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- None found
At a glance
Write a disclosure-quality bug bounty report for a finding, matching the HackerOne report format used in this repo's corpus.
- Works in 3 steps: Collect the finding details from the… → Find a style/structure exemplar. Pull… → Write the report in this structure…
- The user has a vulnerability and wants it written up — write a report for this
- SKILL.md covers Workflow and Rules
- Calls python3
What it does
Write Report is an agent skill from bugbountywithmarco/bugbounty-disclosed-reports. Write a disclosure-quality bug bounty report for a finding, matching the HackerOne report format used in this repo's corpus. Use when the user has a vulnerability and wants it written up — "write a report for this", "draft a HackerOne submission", "turn this finding into a report". Produces title, summary, steps to reproduce, impact, severity, and remediation, few-shot styled on real disclosed reports.
Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Bug bounty, Prompt engineering and Report writing. The repository describes itself as: Public Disclosed Bug Bounty Reports formated in markdown.
When your agent uses it
- The user has a vulnerability and wants it written up — write a report for this
- Draft a HackerOne submission
- Turn this finding into a report
Example prompts
- “write a report for this”
- “draft a HackerOne submission”
- “turn this finding into a report”
- “/write-report”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Collect the finding details from the user / conversation: target asset, vuln
- Find a style/structure exemplar. Pull 2–3 strong same-class reports to match
- Write the report in this structure (Markdown)
What it can do on your machine
Read from SKILL.md and the folder at commit b6c76d1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Write Report loads about 585 tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 147 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 147 words (~585 tokens).
“Draft a clear, triager-friendly bug bounty report that matches the structure of the disclosed reports in reports/.”
- name
- write-report
Files
Just SKILL.md in .claude/skills/write-report of bugbountywithmarco/bugbounty-disclosed-reports.
Open the folder on GitHubat commit b6c76d1
Compare with similar skills
Write Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write Report this skillbugbountywithmarco/bugbounty-disclosed-reports | 122 | — | ~585 | Automated safety check: Pass | None | |
| Web3 Triage and Report Examplestradecatlabs/vibe-coding-cn | 17k | 2 repos | ~7.7k | Automated safety check: Pass | MIT | |
| Bug Bounty Report Writingawarexone/Agentic-Bug-Hunter | 5.3k | 2 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Report Writingsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Bugcrowd Reportingsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.9k | Automated safety check: Pass | MIT | |
| Report Writingelementalsouls/Claude-BugHunter | 4.8k | — | ~5.2k | Automated safety check: Pass | MIT |
Similar skills
Bug Bounty Report Writing
awarexone/Agentic-Bug-Hunter
Guides writing bug bounty reports for HackerOne, Bugcrowd, Intigriti and Immunefi: impact-first titles, proven claims, CVSS 3.1 scoring and a pre-submit checklist.
Report Writing
sickn33/agentic-awesome-skills
Bug bounty report writing for H1/Bugcrowd/Intigriti/Immunefi
Bugcrowd Reporting
sickn33/agentic-awesome-skills
Bugcrowd-specific reporting tactics complementing report-writing
Report Writing
elementalsouls/Claude-BugHunter
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…
Web3 Smart Contract Audit
awarexone/Agentic-Bug-Hunter
Guides smart contract audits and bounty target selection with ten DeFi bug classes, kill signals, a Foundry PoC template and grep patterns.
More from bugbountywithmarco/bugbounty-disclosed-reports
Program Intel
bugbountywithmarco/bugbounty-disclosed-reports
Summarize the historical bug patterns for a specific bug bounty program/team using the local disclosed-report corpus.
Recon Playbook
bugbountywithmarco/bugbounty-disclosed-reports
Build a hunting checklist / methodology for a vulnerability class or target tech stack, distilled from the local disclosed-report corpus.
Severity
bugbountywithmarco/bugbounty-disclosed-reports
Estimate the severity of a vulnerability finding and produce a CVSS 3.1 vector + impact framing, calibrated against how similar findings were rated in the local disclosed-report corpus.
Related
Categories
Questions about Write Report
What does Write Report do?
Write a disclosure-quality bug bounty report for a finding, matching the HackerOne report format used in this repo's corpus. Write Report is an agent skill from bugbountywithmarco/bugbounty-disclosed-reports. Write a disclosure-quality bug bounty report for a finding, matching the HackerOne report format used in this repo's corpus.
When should I use Write Report?
Write Report fits situations like: the user has a vulnerability and wants it written up — write a report for this; draft a HackerOne submission; turn this finding into a report.
How do I install Write Report in Claude Code?
Run `npx skills add bugbountywithmarco/bugbounty-disclosed-reports --skill write-report -a claude-code`. Or copy the skill folder (.claude/skills/write-report in bugbountywithmarco/bugbounty-disclosed-reports) into .claude/skills/write-report in your project. Claude Code loads it when a task matches its description.
How do I install Write Report in Codex?
Run `npx skills add bugbountywithmarco/bugbounty-disclosed-reports --skill write-report -a codex`. Or copy the skill folder (.claude/skills/write-report in bugbountywithmarco/bugbounty-disclosed-reports) into .agents/skills/write-report in your project. Codex loads it when a task matches its description.
Can I use Write Report in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bugbountywithmarco/bugbounty-disclosed-reports --skill write-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-report, .gemini/skills/write-report, .github/skills/write-report and .opencode/skills/write-report in your project.
What does Write Report need to run?
Going by SKILL.md and its folder, Write Report needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Write Report access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Write Report safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Write Report use?
No licence was found for Write Report or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Write Report use?
About 585 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Write Report?
Skills that share tags, products or a category with Write Report: Web3 Triage and Report Examples (tradecatlabs/vibe-coding-cn, 17k stars), Bug Bounty Report Writing (awarexone/Agentic-Bug-Hunter, 5.3k stars), Report Writing (sickn33/agentic-awesome-skills, 47k stars) and Bugcrowd Reporting (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Report?
bugbountywithmarco (a GitHub user) maintains it in bugbountywithmarco/bugbounty-disclosed-reports, which has 122 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on July 14, 2026.
Source: bugbountywithmarco/bugbounty-disclosed-reports on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.