Run any Skill in Manus with one click

hackenproof-comment-templates

Stars50

Forks6

UpdatedJune 18, 2026 at 18:26

Standard HackenProof triage closure comment templates for Out of Scope, Informative, Not Applicable, Need More Info, Duplicate, and Dual Defence Informative states. Use whenever writing a closure or decision comment on a HackenProof report. Trigger on "closure comment", "triage comment", "write comment", "close as", or any state transition that requires a comment.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hackenproof-public

hackenproof-public/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Information Security AnalystsComputer and Mathematical Occupations·SOC 15-1212

File Explorer

3 files

SKILL.md

readonly

name	hackenproof-comment-templates
description	Standard HackenProof triage closure comment templates for Out of Scope, Informative, Not Applicable, Need More Info, Duplicate, and Dual Defence Informative states. Use whenever writing a closure or decision comment on a HackenProof report. Trigger on "closure comment", "triage comment", "write comment", "close as", or any state transition that requires a comment.

HackenProof Comment Templates

Generate structured, professional triage comments using the standard HackenProof template format.

When to Use

Use when writing a closure or decision comment on any HackenProof report. Load references/comment-templates.md to select the correct template for the state being applied.

How to Use

Identify the state: Out of Scope, Informative, Not Applicable, Need More Info, or Duplicate
Load the matching template from references/comment-templates.md
Fill in all *PLACEHOLDER* values and // EXPLANATION blocks with specific technical reasoning
Post the comment via whichever method your setup supports

Comment Rules

Every comment must explain the specific rule violated, what evidence was missing, and what would be needed to resubmit
Never reference other report IDs in the comment body — reporters cannot see them. Internal labels like dup-{id} are fine because they are not part of the comment.
Never mention the specific severity label in Dual Defence closure comments — reference the threshold only
Never disclose private information (attack prerequisites, internal severity caps, client-side decisions) in public comments
Verify every factual claim before writing it
Comment quality does not drop during batch work

Reputation Line Rules

Only include the reputation line matching the state:

OOS: "Please note that this closure will not impact your reputation score." ✓
Informative: Do NOT include any reputation line — Informative gives +2 rep
N/A: NEVER include the reputation line — N/A is -5 rep
Duplicate: Do NOT include reputation line
NMI: No reputation mention

More from this repository

same repository

hackenproof-poc-grader

hackenproof-public/skills

Grade the evidence quality of a HackenProof bug bounty report before forming a severity opinion. Returns one of five verdicts (Verified, Plausible, Weak, Invalid, Out of Scope Evidence) based on a rubric of evidence tiers and negative signals. Trigger on "grade poc", "evidence quality", "is this poc valid", "check evidence", or before any triage severity decision.

2026-06-1850

hackenproof-triage-mistakes

hackenproof-public/skills

Accumulated HackenProof triage mistakes and corrections. Load at the start of every triage session and selectively before evidence evaluation, severity decisions, comment writing, or batch closes. Self-expands per-analyst into ~/.hackenproof/mistakes/. Trigger on "triage", "review report", "before triage", or any HackenProof report decision.

2026-06-1850

hackenproof-all-reports-export

hackenproof-public/skills

Export ALL reports of a HackenProof program into a structured file. User chooses report detail level (Full, No Comments, or Public) and output format (Markdown, JSON, or CSV). Trigger on "export all reports to markdown", "generate md file for all program reports", "create export of all reports", "give me all reports as a file", "make a full report export", "export program reports", "final report for my program", "provide final report for program", "generate final report for program".

2026-05-0750

hackenproof-fix-verifier

hackenproof-public/skills

Verify that a security fix actually addresses the reported vulnerability without introducing new issues. Works with any local codebase — no MCP or bug bounty platform required. Trigger on "verify fix", "check fix", "is this fix correct", "review patch", "did this fix the bug".

2026-04-2250

hackenproof-report-handoff

hackenproof-public/skills

Generate structured report handoff summaries for client teams. Use after triaging a report to produce a standardized handoff with report URL, recommended severity, bounty range, and explanation. Trigger on "handoff", "transfer to client", "prepare handoff", "client summary".

2026-04-2250

hackenproof-bulk-triage

hackenproof-public/skills

Bulk triage workflow for all assigned HackenProof programs. Discovers all open reports across every assigned program, syncs local codebases, analyzes each report, and outputs structured recommendations for human review — without applying any changes automatically.

2026-03-2650

name	hackenproof-comment-templates
description	Standard HackenProof triage closure comment templates for Out of Scope, Informative, Not Applicable, Need More Info, Duplicate, and Dual Defence Informative states. Use whenever writing a closure or decision comment on a HackenProof report. Trigger on "closure comment", "triage comment", "write comment", "close as", or any state transition that requires a comment.

HackenProof Comment Templates

Generate structured, professional triage comments using the standard HackenProof template format.

When to Use

Use when writing a closure or decision comment on any HackenProof report. Load references/comment-templates.md to select the correct template for the state being applied.

How to Use

Identify the state: Out of Scope, Informative, Not Applicable, Need More Info, or Duplicate
Load the matching template from references/comment-templates.md
Fill in all *PLACEHOLDER* values and // EXPLANATION blocks with specific technical reasoning
Post the comment via whichever method your setup supports

Comment Rules

Every comment must explain the specific rule violated, what evidence was missing, and what would be needed to resubmit
Never reference other report IDs in the comment body — reporters cannot see them. Internal labels like dup-{id} are fine because they are not part of the comment.
Never mention the specific severity label in Dual Defence closure comments — reference the threshold only
Never disclose private information (attack prerequisites, internal severity caps, client-side decisions) in public comments
Verify every factual claim before writing it
Comment quality does not drop during batch work

Reputation Line Rules

Only include the reputation line matching the state:

OOS: "Please note that this closure will not impact your reputation score." ✓
Informative: Do NOT include any reputation line — Informative gives +2 rep
N/A: NEVER include the reputation line — N/A is -5 rep
Duplicate: Do NOT include reputation line
NMI: No reputation mention