CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

contact-page

Use when auditing metadata, crawlability, structured data, or indexability related to Create a comprehensive Contact page. Verify the rendered HTML and HTTP response rather than relying only on source files.

Quality

76%

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/contact-page/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 lean, well-organized audit-rule body with a proper overview-to-reference split (references/rule.md verified real and appropriately scoped), a coherent Check→Fix→Explain→Code Review sequence, and only minor token waste. Its main weakness is actionability: verification and fix steps name what to do but not how, leaving execution details entirely to the reference file.

Suggestions

Add a concrete verification method to the Check section (e.g., 'Fetch the rendered /contact page — curl or a browser — and confirm the mailto link, form, and address are present in the served HTML') so the body's check is executable without the reference.

Define what makes contact methods 'working' — e.g., submit a test form, confirm the mailto address resolves, verify /contact is linked from the global navigation — to make the Fix step concrete.

Inline the single most useful snippet from references/rule.md (the footer nav link to /contact) into the Fix section so the discoverability requirement has an executable example at the point of need.

DimensionReasoningScore

Conciseness

The ~30-line body is tight — short bullets, 1-2 sentence sections — with only minor trimmable tokens: "A clear and accessible contact page is a major trust signal for E-E-A-T and provides essential support for users, improving overall site credibility" restates rationale Claude already knows, and "other relevant contact information" is filler. Matches 'efficient; minor instances of over-explanation'. Not 5 because of those two spots; not 3 because there is no concept-explainer padding and every section is load-bearing.

4 / 5

Actionability

Concrete but incomplete: the Fix names a specific route and elements ("Create a `/contact` page and add a contact form, email address..."), yet the Check gives no method ("Verify that the website has a dedicated Contact page with multiple, working contact methods" — how?), 'working' is undefined, and "other relevant contact information" and "Flag exact routes or templates" stay at directive level with key details deferred to the reference. Fits 'some concrete guidance but incomplete; missing key details'. Not 4 because no body-level verification technique or executable step exists — the how lives only in references/rule.md; not 2 because the Fix is a specific route plus named elements, more than high-level hints.

3 / 5

Workflow Clarity

The sectioned sequence Check → Fix → Explain → Code Review is a coherent audit workflow with "Verify that the website has a dedicated Contact page..." as an explicit upfront checkpoint and "describe how to verify the final page output" closing the loop — matching 'clear sequence with most checkpoints present; minor validation gaps'. Not 5 because there is no post-fix re-verification step in the body (confirming the new page is linked and its form works); not 3 because the Check checkpoint is explicit rather than 'implicit or missing'. No destructive/batch operations, so no cap applies.

4 / 5

Progressive Disclosure

The body is a clear, well-sectioned overview under 50 lines with a single well-signaled one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and the bundle check confirms references/rule.md exists, is self-contained (no nested references), and delivers what is promised (HTML code example, why-it-matters, exceptions, verification steps). Matches 'clear overview with well-signaled one-level-deep references; content appropriately split'.

5 / 5

Total

16

/

20

Passed

Description

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

The description has a clear 'Use when' trigger clause with relevant natural SEO keywords and an explicit verification action, but the embedded rule-title phrase 'related to Create a comprehensive Contact page' garbles both the what and the when and weakens distinctiveness against sibling SEO-audit skills. Overall solid but in need of a grammatical rewrite.

Suggestions

Rewrite 'related to Create a comprehensive Contact page' as a natural trigger phrase (e.g., "Use when auditing a site's contact page for working contact methods") so the niche is a clean, distinct trigger rather than an embedded rule title.

State the full 'what' explicitly, e.g., "Audits a site's contact page for multiple working contact methods, discoverability, and NAP/trust signals in the rendered HTML, then flags gaps" — so the capability is not limited to verification.

Scope the generic SEO trigger list (metadata, crawlability, structured data, indexability) to the contact page specifically, reducing overlap with sibling SEO audit skills that share those triggers.

DimensionReasoningScore

Specificity

Lists several concrete actions — "auditing metadata, crawlability, structured data, or indexability" and "Verify the rendered HTML and HTTP response rather than relying only on source files" — matching the 'several specific actions; minor gaps' anchor. Not 5 because the core capability (creating/fixing the contact page) is never stated as an action and "related to Create a comprehensive Contact page" is a garbled title insertion, not a verb; not 3 because there are 4+ named audit targets plus an explicit verification directive, exceeding '1-2 concrete actions'.

4 / 5

Completeness

Both parts are present: an explicit "Use when auditing metadata, crawlability, structured data, or indexability..." clause and a what of "Verify the rendered HTML and HTTP response rather than relying only on source files". Not 5 because the 'what' is partial (verification only — the create/fix capability is buried in the awkward title phrase) and the 'when' mixes generic SEO triggers with an embedded rule title; not 3 because the 'Use when' clause is explicit with concrete triggers, well above 'when only weakly implied'.

4 / 5

Trigger Term Quality

Natural keywords a user would say are present: "metadata", "crawlability", "structured data", "indexability", "rendered HTML", "HTTP response", "Contact page" — good coverage with a few missing terms. Not 5 because "Create a comprehensive Contact page" is a rule title rather than a natural phrase and common variations ("SEO", "site audit", "search visibility") are absent; not 3 because coverage goes well beyond 'some relevant keywords', spanning four audit domains plus the page subject.

4 / 5

Distinctiveness Conflict Risk

The leading triggers ("metadata, crawlability, structured data, or indexability") are the generic trigger set for a whole family of SEO audit skills, and only the embedded "Create a comprehensive Contact page" phrase scopes this one — 'somewhat specific but could still overlap with similar skills'. Not 4 because the differentiator is a grammatically embedded title rather than a clean, prominent trigger, so sibling rules (sitemap, robots, etc.) would compete on the same phrases; not 2 because a named niche (contact page) is present, not just broad 'document files' level generality.

3 / 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/contact-page/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.