CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

password-field-security

Use when reviewing headers, forms, cookies, or third-party integrations related to Secure password input fields. Validate the effective browser and HTTP behavior in a production-like environment.

Quality

73%

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/password-field-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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, concise overview body that delegates implementation detail correctly to a real one-level-deep reference file. Its weaknesses are in execution guidance: the body names the right attributes and values but provides no code, commands, or method for the verification step ('validate against the effective production-like response') that the skill positions as its core value, and the Check section redundantly restates the Quick Reference bullets.

Suggestions

Add a minimal executable verification step for the 'Code Review' section — e.g., a curl command or devtools procedure to observe the effective response/headers for the login form endpoint — so the promised validation is actionable.

Replace the redundant 'Check' paragraph (which restates Quick Reference bullets) with the one or two details not already listed, such as how to evaluate the show/hide toggle for accessibility (button placement, aria-pressed/aria-label).

Inline one short code snippet or the exact attribute checklist (e.g., name/autocomplete pairing for password-manager support) in the 'Fix' section so users get copy-paste-ready guidance without opening the reference file.

DimensionReasoningScore

Conciseness

The body is short and tightly organized: a one-line rationale, five compact Quick Reference bullets, and three brief Check/Fix/Explain sections — no explanations of concepts Claude already knows. It is not a 5 because there is real redundancy: the 'Check' section restates two Quick Reference bullets ('type=password', 'autocomplete values', 'show/hide toggles') almost verbatim, and the Code Review paragraph repeats the frontmatter description. It is above a 3 because the padding is minor and easily trimmed.

4 / 5

Actionability

Some guidance is concrete — 'type=password', "autocomplete='new-password' or 'current-password'" are specific, actionable values. But key execution details are missing: no code or commands appear in the body (full examples are deferred to references/rule.md), 'accessible toggle buttons' and 'optional strength meters' are stated without implementation specifics (ARIA attributes, toggle pattern), and 'verify them against the effective production-like response' gives no method (no curl commands, devtools steps, or test procedure). This matches 'some concrete guidance but incomplete; missing key details' — above a 2 because specific attribute values are given, below a 4 because the verification method — the skill's central claim — is undefined.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure lists the review phases in a recognizable order with concrete check items. It is not a 4+ because the validation the skill itself demands — 'verify them against the effective production-like response' and the description's 'validate the effective browser and HTTP behavior in a production-like environment' — is never operationalized: no commands, no test procedure, no explicit checkpoint for when verification passes. This matches 'steps listed but validation gaps; sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The body is a lean overview (well under 50 lines) with clear section headers, and all implementation detail — code examples and framework-specific guidance — is correctly split into references/rule.md, which exists in the bundle. The reference is clearly signaled ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') and exactly one level deep. This matches the 'clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation' anchor.

5 / 5

Total

15

/

20

Passed

Description

70%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 'Use when' trigger clause and relevant natural keywords, clearly anchored to the password-field security niche. Its main weakness is an under-specified 'what' — 'Validate the effective browser and HTTP behavior' never conveys the concrete review/fix actions the skill performs, and it omits common trigger phrasings like 'login form' or 'autocomplete'.

Suggestions

State the concrete actions the skill performs instead of the generic 'Validate the effective browser and HTTP behavior' — e.g., 'Check password fields for correct type and autocomplete attributes, fix them, and verify behavior in a production-like environment.'

Add natural trigger phrasings users would actually say, such as 'login form', 'sign-up form', 'autocomplete', or 'password manager', to broaden keyword coverage.

Tighten the opening scope list ('headers, forms, cookies, or third-party integrations') toward password-field-specific surfaces to reduce overlap with sibling header/cookie security skills.

DimensionReasoningScore

Specificity

The description names the domain ('Secure password input fields') and one to two actions ('Validate the effective browser and HTTP behavior in a production-like environment', 'reviewing headers, forms, cookies'), but the actions are stated generically without concrete operations like the Check/Fix guidance found in the body. It matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it is not a 4 because it does not list several specific actions, and not a 2 because the domain and an explicit action are clearly present.

3 / 5

Completeness

Both parts are present: 'what' ('Validate the effective browser and HTTP behavior in a production-like environment') and an explicit 'when' ('Use when reviewing headers, forms, cookies, or third-party integrations related to Secure password input fields'). It is not a 5 because the 'what' is vague about what the skill actually does (check, fix, explain are never mentioned in the description), and not a 3 because both what and when are explicitly stated with concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural keywords are well covered: 'headers', 'forms', 'cookies', 'third-party integrations', 'password input fields', 'browser', 'HTTP', 'production-like environment'. It falls short of a 5 because common user phrasings like 'login form', 'sign-up', 'autocomplete', and 'password manager' are missing; it exceeds a 3 because multiple relevant natural terms are present rather than just one or two generic keywords.

4 / 5

Distinctiveness Conflict Risk

The 'Secure password input fields' niche is distinct with clear triggers, but the broad opening terms 'headers, forms, cookies, or third-party integrations' create minor overlap risk with sibling security-checklist skills (e.g., cookie security or header security rules). This matches 'mostly distinct; minor overlap risk with closely related skills' — not a 5 given that overlap, and not a 3 since the password-field focus clearly dominates.

4 / 5

Total

15

/

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/password-field-security/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.