CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

form-https

Use when reviewing HTML forms, fetch/XHR calls, and form action attributes to ensure data is submitted exclusively over HTTPS.

Quality

77%

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-https/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 tight, well-structured body with actionable check/fix guidance and exemplary progressive disclosure through a single verified one-level reference. The main cost is the motivational opening paragraph that restates knowledge Claude already has and duplicates content in the reference file, plus an unqualified version-specific Chrome detail.

Suggestions

Trim or remove the opening motivation paragraph — the plain-text-credentials threat model is knowledge Claude already has, and the same explanation appears in references/rule.md, so the body can start directly with the Quick Reference.

Move the 'From Chrome 86+, autofill is disabled on HTTP forms' version-specific detail into the reference file or a clearly labeled version-notes line, keeping the body free of time-sensitive version numbers.

Add a brief re-verify step to the Fix section (e.g., 'Re-run the check to confirm no http:// endpoints remain') to close the feedback loop after remediation.

DimensionReasoningScore

Conciseness

The opening paragraph explains threat-model basics Claude already knows ('anyone on the same Wi-Fi, the ISP, or a network proxy can read them') and duplicates text found nearly verbatim in references/rule.md; the time-sensitive 'From Chrome 86+' version reference is not placed in a deprecated/old-patterns section. Mostly efficient overall, matching anchor 3 rather than 4's 'minor instances'.

3 / 5

Actionability

Concrete, executable instructions like 'Scan all HTML form elements for action attributes pointing to http:// URLs' and 'Replace all http:// form action URLs with https:// equivalents' with a specific 301-redirect remedy; minor gaps only (no inline example search command or code snippet, though those live in the referenced file). Anchor 4, not 5, because nothing inline is copy-paste ready.

4 / 5

Workflow Clarity

A clear Check -> Fix sequence organized in purposeful sections, with verification present in the Code Review section ('verify them against the effective production-like response'); not 5 because there is no explicit re-check-after-fix feedback loop, though this review skill involves no destructive or batch operations so no cap applies.

4 / 5

Progressive Disclosure

The body is under 50 lines, keeps overview-level content, and clearly signals a single one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists in the bundle; matches anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

16

/

20

Passed

Description

75%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 well-crafted description with an explicit 'Use when...' trigger, concrete targets, and a clear purpose statement. Its main limitations are the single merged clause structure (what and when are not separate statements) and a few missing natural trigger variations.

DimensionReasoningScore

Specificity

Names several concrete targets ('HTML forms, fetch/XHR calls, and form action attributes') and a concrete outcome ('data is submitted exclusively over HTTPS'), but offers only a single action verb (reviewing) rather than multiple distinct actions, fitting anchor 4 better than 3 or 5.

4 / 5

Completeness

An explicit 'Use when...' trigger is present and the what ('ensure data is submitted exclusively over HTTPS') is stated, but the what is embedded inside the when-clause rather than given as a standalone capability statement; not 5 because the merged single-clause structure is less explicit than separate what/when statements, not 3 because both elements are clearly present.

4 / 5

Trigger Term Quality

'HTML forms', 'fetch/XHR calls', 'form action attributes', and 'HTTPS' are phrases users would naturally say when needing this skill, but common variations like 'form submission', 'AJAX requests', or the spelled-out 'XMLHttpRequest' are missing, matching anchor 4's 'good coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

The form-transport-security niche is distinct with specific triggers, but 'fetch/XHR calls' extends the scope beyond forms into general HTTPS/API-security territory, creating minor overlap risk with closely related security skills; anchor 4 fits better than 5's 'minimal conflict risk'.

4 / 5

Total

16

/

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-https/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.