CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bugcrowd-reporting

Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints, debug-info framing, user-enumeration with sensitive PII, theoretical-issue counter), chained-finding cross-reference patterns, target selection for QA-vs-prod programs, researcher-side hygiene (Bugcrowdninja email alias, account state restoration, friendly-tester posture). Use when filing a Bugcrowd submission, when VRT default seems wrong, when triager closes as OOS or downgrades severity, when chaining linked submissions, or when scope distinguishes production from QA. Pairs with report-writing and triage-validation.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is bugcrowd-reporting in elementalsouls/Claude-BugHunter

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally actionable, well-structured tactical skill: every section provides copy-paste templates, concrete mappings, or ordered procedures grounded in real platform mechanics, with no filler. The only improvements are minor: consolidate the redundant skill-pairing sections and the thrice-repeated 'one fix = one bounty' rule, and consider splitting the §3–§4 template blocks into a references file for a leaner SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense with platform-specific knowledge Claude cannot know (VRT mappings, form mechanics, program rules) and wastes no tokens on known concepts, but has minor redundancy: the 'one fix = one bounty' rule is restated three times (§3.2, §5.2, §5.3) and three separate sections (§9 table, 'Notes on usage', 'Related Skills & Chains') cover skill pairing with overlapping content. This matches 'efficient; minor instances that could be trimmed' rather than 'every token earns its place'.

4 / 5

Actionability

Guidance is maximally concrete for an instruction-only skill: literal copy-paste markdown templates for the severity-request paragraph, all four OOS rebuttals, chain cross-references, and the QA disclaimer, plus a worked example (§3.2), a first-choice/fallback VRT mapping table, and numbered form-mechanics steps. Everything is fill-in-the-blank ready.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced — §5.1 explicitly handles the tricky UUID backfill ordering (file primitives → consumer → edit primitives), and §2.2/§7/§8.1 give ordered procedures with quality gates (§4.5 'don't file theoretical findings', §2.3 'don't over-claim'). It falls short of anchor 5 only in lacking an explicit post-submission error-recovery loop (e.g., what to do when a triager downgrades anyway). The destructive/batch cap doesn't apply: filing isn't destructive and §8 includes explicit anti-batch cautions.

4 / 5

Progressive Disclosure

A single ~310-line file with nine well-organized, cross-referenced sections (§ links throughout, a §9 routing table, clean boundaries with sibling skills). Structure is good, but nothing is split out — the template blocks in §3–§4 would fit naturally in a references/ file — so it stops short of the 'well-signaled one-level-deep references' top anchor while comfortably exceeding 'could be better organized'.

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a model skill description: dense with concrete capabilities, explicit multi-condition 'Use when' triggers phrased in natural user language, and clearly bounded against sibling skills. Third-person voice is maintained throughout with no padding or over-claims.

DimensionReasoningScore

Specificity

The description enumerates every major capability in concrete terms — 'VRT category search-and-fallback strategy', 'manual severity override when VRT defaults underrate impact', 'OOS-clause rebuttal templates (rate limiting on auth-flow endpoints, debug-info framing…)' — with sub-details for each, giving comprehensive coverage. It exceeds anchor 4 ('several specific actions; minor gaps') because every skill section is represented with no noticeable gap.

5 / 5

Completeness

It explicitly answers 'what' (a detailed list of seven tactic areas) and 'when' (an explicit 'Use when…' clause with five concrete trigger conditions), plus pairing guidance with sibling skills. Both halves are concrete and explicit, matching the top anchor.

5 / 5

Trigger Term Quality

Triggers like 'Use when filing a Bugcrowd submission, when VRT default seems wrong, when triager closes as OOS or downgrades severity' are the exact natural phrases a bug-bounty researcher would say. Full domain vocabulary (VRT, OOS, triager, severity downgrade, chaining, QA vs production) is covered with no meaningful natural terms missing, matching the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

'Bugcrowd-specific reporting tactics complementing report-writing' carves out a clear niche, and 'Pairs with report-writing and triage-validation' plus trigger conditions tied to Bugcrowd-only artifacts (VRT, OOS clauses) make wrong-skill triggering unlikely. It explicitly bounds itself against the closest overlapping skill.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Awarexone/Agentic-Bug-Hunter

Path

skills/bugcrowd-reporting/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.