hunt-captcha-bypass

Hunt CAPTCHA Bypass — 6 distinct patterns: (1) CAPTCHA field simply omitted from the request (server-side validation absent), (2) CAPTCHA token replayed from a solved challenge (no single-use enforcement), (3) CAPTCHA response accepted on a different endpoint than it was solved on (no binding to action/session), (4) static or predictable CAPTCHA values accepted (e.g. '0', 'null', empty string), (5) audio/accessibility CAPTCHA trivially solvable programmatically, (6) CAPTCHA only enforced after N failures (first N requests bypass it). Detection: intercept a successful form submission, remove the CAPTCHA field entirely, replay — if it still succeeds, server-side validation is absent. Medium severity standalone; High when it removes the only rate-limit gate protecting a login, registration, or payment endpoint.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/hunt-captcha-bypass/SKILL.md

Quality

Content

58%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.

The content is concrete and well-structured with actionable patterns, payloads, and concurrency guidance, but the Vulnerability Classes section is partly redundant and the batch-testing workflow lacks an explicit validation feedback loop.

Suggestions

Add an explicit validate-fix-retry loop for batch/concurrent testing, e.g. verify the concurrent payload is well-formed before firing, then re-run with adjusted N if the window is not satisfied.

Collapse or remove the 'Vulnerability Classes' section since it largely duplicates the patterns already enumerated under 'Autonomous Testing Priority'.

Provide a single complete, copy-paste example request or tool invocation covering the most common omit-field bypass to lift actionability to 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and action-oriented, but the 'Vulnerability Classes' section largely restates patterns already covered in 'Autonomous Testing Priority', and minor explanations of reCAPTCHA token semantics could be trimmed.	3 / 5
Actionability	Concrete guidance is provided with real field names (g-recaptcha-response), example payloads (captcha=&email=...), and a specific concurrency recipe, with only minor gaps such as a fully copy-paste tool command.	4 / 5
Workflow Clarity	Sequenced steps and a 'Proof' confirmation step exist, but for a batch/concurrent-request testing skill there is no explicit validate->fix->retry feedback loop, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear sections (Autonomous Testing Priority, Vulnerability Classes, Impact Chain, Related Skills) and no nested references; slightly above the simple-skill threshold with good navigation.	4 / 5
	Total	14 / 20 Passed

Description

71%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.

The description is highly specific and concrete, listing six bypass patterns and a detection method, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. Distinctiveness and trigger-term quality are strong.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g. 'Use when testing login, registration, or password-reset endpoints protected by a CAPTCHA').

Include common synonyms such as 'bot protection' or 'anti-bot challenge' to broaden natural trigger-term coverage.

Trim the severity footnote or move it into the body so the description focuses on what/when.

Dimension	Reasoning	Score
Specificity	Enumerates six distinct concrete bypass patterns (field omission, token replay, endpoint cross-use, static/predictable values, audio automation, after-N-failures) plus a specific detection procedure, giving comprehensive concrete coverage.	5 / 5
Completeness	The 'what' is detailed and concrete, but there is no explicit 'Use when...' or equivalent trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural phrases like 'CAPTCHA bypass' and 'CAPTCHA field simply omitted' map well to what a user would say, but synonyms like 'bot protection' or 'anti-bot' are absent, so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	The CAPTCHA-bypass niche is clearly distinct with specific triggers, with only minor overlap risk against closely related skills such as brute-force and forgot-password.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: elementalsouls/Claude-BugHunter
Path: skills/hunt-captcha-bypass/SKILL.md
Commit: d4b54e1

Reviewed: 12 hours ago

Table of Contents

Discovery Implementation Validation

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.