Safe Captcha handling via Browser Agent or 2Captcha API.
36
31%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xnagato/captcha/SKILL.mdQuality
Discovery
40%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 identifies a clear niche (captcha handling) with two specific approaches, making it distinctive. However, it is too terse—lacking concrete action verbs, common trigger term variations, and critically missing any 'Use when...' guidance that would help Claude know when to select this skill.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user needs to solve or bypass CAPTCHAs, reCAPTCHAs, hCaptchas, or other bot verification challenges.'
List specific concrete actions such as 'Solves reCAPTCHA v2/v3, hCaptcha, and image-based CAPTCHAs using Browser Agent automation or the 2Captcha API.'
Include common trigger term variations like 'CAPTCHA', 'reCAPTCHA', 'hCaptcha', 'captcha solving', 'bot verification', 'anti-bot challenge'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (captcha handling) and mentions two specific methods (Browser Agent, 2Captcha API), but doesn't describe concrete actions like solving, bypassing, submitting, or what types of captchas are supported. | 2 / 3 |
Completeness | Provides a brief 'what' (captcha handling via two methods) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also quite thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Captcha', '2Captcha', and 'Browser Agent' which are relevant keywords, but misses common variations like 'CAPTCHA', 'reCAPTCHA', 'hCaptcha', 'captcha solving', 'bot verification', or 'anti-bot'. | 2 / 3 |
Distinctiveness Conflict Risk | Captcha handling is a very specific niche that is unlikely to conflict with other skills. The mention of 2Captcha API and Browser Agent further narrows the scope distinctly. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a skeletal outline rather than actionable guidance. It identifies the right concepts (detection, manual intervention, 2Captcha API) but provides almost no concrete implementation—no code for captcha detection, no 2Captcha API integration example, no browser interaction commands, and no clear branching workflow. It reads more like a planning document than an executable skill.
Suggestions
Add executable code examples for both paths: (1) pausing and prompting the user for manual captcha solving, and (2) calling the 2Captcha API with the site key and page URL to solve automatically.
Provide a concrete detection step with specific selectors or page indicators (e.g., iframe src containing 'recaptcha', specific element classes) rather than just 'sees I'm not a robot'.
Define a clear branching workflow: detect captcha → check vault for API key → if key exists, call 2Captcha API with specific code → poll for result → inject solution → validate page loaded; if no key, screenshot + prompt user → wait → verify resolution.
Add a validation/verification step after captcha resolution to confirm the page has progressed past the challenge.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably brief but includes some unnecessary framing ('This skill provides a protocol for...') and the strategy section is somewhat vague rather than adding concrete value. Could be tighter. | 2 / 3 |
Actionability | Almost entirely vague and abstract. No executable code for captcha detection, no API integration example, no concrete browser interaction commands. The only concrete element is the vault storage command, but the actual captcha-solving workflow is described rather than instructed. | 1 / 3 |
Workflow Clarity | The 'strategy' lists only 2 high-level steps with no real sequence, no validation checkpoints, no error handling, and no feedback loop. The 'Ask the user for help OR use an API key if configured' is extremely vague for what should be a branching workflow with concrete steps for each path. | 1 / 3 |
Progressive Disclosure | The content is short and organized into sections, which is fine for a simple skill. However, there are no bundle files and no references to deeper documentation. The structure is adequate but the content is too thin to warrant strong progressive disclosure scoring. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
f45fcb5
Table of Contents
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.