Safe Captcha handling via Browser Agent or 2Captcha API.
45
Quality
30%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xnagato/captcha/SKILL.mdQuality
Discovery
22%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 description is too brief and vague to effectively guide skill selection. It names the domain (captcha) and tools (Browser Agent, 2Captcha API) but fails to specify concrete actions or provide trigger guidance. The word 'Safe' is unexplained fluff that adds no value.
Suggestions
Add explicit trigger guidance with a 'Use when...' clause, e.g., 'Use when encountering CAPTCHAs during web automation, form submission, or when the user mentions verification challenges.'
Replace vague 'handling' with specific actions like 'Solves image and text CAPTCHAs, bypasses verification challenges, integrates with 2Captcha solving service.'
Add common trigger term variations: 'CAPTCHA', 'verification', 'bot detection', 'reCAPTCHA', 'hCaptcha' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Safe Captcha handling') without specifying concrete actions. It doesn't explain what 'handling' means - solving, bypassing, generating, or something else. | 1 / 3 |
Completeness | Missing explicit 'Use when...' clause entirely. The 'what' is weak (just 'handling') and the 'when' is completely absent, leaving Claude to guess when this skill should be selected. | 1 / 3 |
Trigger Term Quality | Contains relevant keywords like 'Captcha', 'Browser Agent', and '2Captcha API' that users might mention, but lacks common variations like 'CAPTCHA', 'verification', 'bot detection', or 'image verification'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of '2Captcha API' and 'Browser Agent' provides some specificity, but 'Captcha handling' is vague enough that it could overlap with browser automation or web scraping skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise but severely lacks actionability. It describes a high-level strategy for CAPTCHA handling without providing any executable code for detection, API integration with 2Captcha, or solution injection. The workflow is too vague to be useful for actual implementation.
Suggestions
Add executable code showing how to detect CAPTCHA elements (e.g., specific selectors or text patterns to look for)
Provide a complete code example for calling the 2Captcha API, including request format and response handling
Add concrete steps for injecting the solved CAPTCHA token back into the page
Include validation steps to verify the CAPTCHA was successfully solved before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations. It assumes Claude understands what CAPTCHAs are and jumps directly to the protocol without padding. | 3 / 3 |
Actionability | The skill provides only vague direction ('Pause the browser', 'Ask the user for help OR use an API key') without any concrete code, API calls, or executable examples for actually solving CAPTCHAs. | 1 / 3 |
Workflow Clarity | The workflow is incomplete and unclear. Steps like 'use an API key if configured' lack any detail on how to actually call the 2Captcha API, handle responses, or inject solutions back into the page. No validation or error handling is mentioned. | 1 / 3 |
Progressive Disclosure | The content is appropriately short and organized into clear sections, but references to tools like 'browser_subagent' and 'hustle_vault' lack links to documentation or examples of their usage. | 2 / 3 |
Total | 7 / 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.
45f9fac
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.