CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

form-captcha

Use when reviewing public HTML forms (no authentication required to reach them) for bot and abuse protection mechanisms.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/form-captcha/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, token-efficient review skill: a tight overview with concrete check/fix guidance that correctly pushes code examples and framework specifics into a single, clearly signaled reference file. Remaining polish is trimming the motivation opener and the templated Code Review paragraph, and tightening the overlap between the Check and Code Review sections.

DimensionReasoningScore

Conciseness

The body is lean and mostly assumes Claude's competence ('Prefer invisible/automated solutions (Cloudflare Turnstile, Google reCAPTCHA v3, hCaptcha)'), but the opening motivation sentence ('an unprotected login form enables credential stuffing attacks that test millions of username/password combinations') restates stakes Claude already knows, and the templated Code Review paragraph ('Flag exact responses, cookies, or browser behaviors') includes off-topic filler like 'cookies'. Minor trims would earn a 5.

4 / 5

Actionability

Guidance is concrete for an instruction-only skill: 'Integrate a CAPTCHA service (Cloudflare Turnstile, hCaptcha, or Google reCAPTCHA v3) on all public forms. Validate the CAPTCHA response token on your server' names specific services and steps, and the Check section enumerates exact form types and protections ('CAPTCHA, honeypot fields, or server-side rate limiting'). It falls short of 5 because methods for verifying server-side validation are entirely deferred to the reference with no inline hint.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear and includes verification instructions ('Verify any CAPTCHA tokens are validated server-side', 'verify them against the effective production-like response'). Not a 5 because the Check and Code Review sections overlap without an explicit ordering relationship, and the Check section states verification goals without checkpoint mechanics.

4 / 5

Progressive Disclosure

The body is a concise overview that defers implementation detail via a clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and references/rule.md exists and delivers exactly those details (Turnstile, reCAPTCHA v3, honeypot, and rate-limiting code). Structure and navigation are clean.

5 / 5

Total

17

/

20

Passed

Description

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

A solid description with an explicit and specific 'Use when' trigger clause and a clearly bounded domain, but it under-sells the skill's concrete capabilities and omits the keyword users would most naturally say ('CAPTCHA'). Naming the mechanisms it checks would lift both specificity and trigger quality.

Suggestions

Add 'CAPTCHA' (plus 'spam' and 'honeypot') to the description — a user asking to 'add a captcha to my signup form' should textually match this skill's trigger.

State the what separately from the when, e.g. 'Checks public HTML forms for CAPTCHA, honeypot fields, and server-side rate limiting. Use when reviewing public HTML forms (no authentication required)...' to sharpen specificity and completeness.

Name the concrete protection mechanisms the skill evaluates instead of the generic 'bot and abuse protection mechanisms', which would also reduce overlap with generic security-review skills.

DimensionReasoningScore

Specificity

The description names a sharply defined domain ('public HTML forms (no authentication required to reach them)') and one concrete action ('reviewing... for bot and abuse protection mechanisms'), matching 'names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because it does not list several specific actions (e.g., checking for CAPTCHA, honeypots, or rate limiting); it is above 2 because the action and domain are specific rather than generic.

3 / 5

Completeness

Both what ('reviewing public HTML forms... for bot and abuse protection mechanisms') and when ('Use when... (no authentication required to reach them)') are present, and the when is unusually explicit. It falls short of 5 because the what is folded into the trigger clause and stays generic about mechanisms — it never states the concrete protections the skill checks (CAPTCHA, honeypot fields, rate limiting).

4 / 5

Trigger Term Quality

Relevant keywords like 'public HTML forms', 'bot', and 'abuse protection' are present, but 'CAPTCHA' — the single most natural term a user would say for this need — is absent, along with 'spam' and 'honeypot'. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The niche is clear and well-bounded — public, unauthenticated HTML forms with bot/abuse protection — with minimal overlap risk against unrelated skills. Minor overlap remains with generic security-review or form-validation skills, and the missing 'CAPTCHA' keyword weakens trigger distinctiveness against a dedicated CAPTCHA-integration skill.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/form-captcha/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.