BC Bug Bounty Triage
Exact-match bug bounty triage workflow for Code4rena, Sherlock, HackenProof, Cantina-style security reviews, Solidity/EVM targets, and vulnerability report prep. Use for bug bounty, bug bounty triage, smart contract bounty, DeFi bounty, finding reports, and audit target prioritization.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 8
✓ No critical or high findings
Medium and low: 8
-
low Risky intent
intent-offensive-securityREADME.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Bug Bounty Triage
-
low Risky intent
intent-offensive-securityREADME.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)Free exact-match ClawHub feeder skill for bug bounty triage and Atlas paid security ZIP funnel.
detector -
low Risky intent
intent-offensive-securityskill-card.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)Exact-match bug bounty triage workflow for Code4rena, Sherlock, HackenProof, Cantina-style security reviews, Solidity/EVM targets, and vulnerability report prep. <br>
detector -
low Risky intent
intent-offensive-securitySKILL.md:2Offensive-security / dual-use content (legitimate for authorised testing; review intended use)name: Bug Bounty Triage
-
low Risky intent
intent-offensive-securitySKILL.md:5Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)description: Exact-match bug bounty triage workflow for Code4rena, Sherlock, HackenProof, Cantina-style security reviews, Solidity/EVM targets, and vulnerability report prep. Use for bug bounty, bug b
detector -
low Risky intent
intent-offensive-securitySKILL.md:7Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)changelog: "Initial exact-match ClawHub listing for bug bounty triage discovery and Atlas $49/$150 security ZIP funnel."
detector -
low Risky intent
intent-offensive-securitySKILL.md:31Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- bug bounty target triage
-
low Risky intent
intent-offensive-securitySKILL.md:39Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Bug Bounty Triage
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Bug Bounty Triage) differs from the folder (bug-bounty-triage)
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 40 steps
- 100Execution cost. Instruction body is 599 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 286: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 40 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.