CtrlK
BlogDocsLog inGet started
Tessl Logo

about-page

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

64

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/about-page/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 lean, well-structured overview for a simple single-purpose skill: a specific check, a concrete fix with an explicit route, and a clearly signaled one-level-deep reference that exists in the bundle. Remaining gaps are minor — the body never states how to concretely verify rendered output, and one E-E-A-T explainer sentence is redundant.

DimensionReasoningScore

Conciseness

The ~30-line body uses short, labeled sections (Quick Reference, Check, Fix, Explain, Code Review) with no padding. Not 5 because the intro sentence "An About page is a primary trust signal for both users and search engines, directly impacting the website's E-E-A-T profile" explains a concept Claude already knows, and the Quick Reference bullets restate the Check section; not 3 because these are minor trims in an otherwise efficient body.

4 / 5

Actionability

Concrete, instruction-only guidance: "Verify that the website has a dedicated About page that clearly identifies the people or organization responsible for the content" and "Create a new page at `/about` and add detailed information about your organization, mission, and the experts behind your content" give a specific route and specific content requirements. Not 5 because the body gives no concrete way to inspect rendered output (deferred entirely to the reference); not 3 because the check and fix directions are specific and executable rather than high-level hints.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear, appropriately ordered sequence for a simple, non-destructive audit skill. Not 5 because verification of the final output is delegated ("describe how to verify the final page output") rather than given as an explicit checkpoint; not 3 because the single-action flow is unambiguous and no validation gaps create risk.

4 / 5

Progressive Disclosure

"For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" is a clearly signaled, one-level-deep pointer to a real file (verified present), and the body keeps only the overview. Matches the anchor exactly: clear overview, well-signaled single reference, content appropriately split, easy navigation.

5 / 5

Total

17

/

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 solidly specific description with an explicit "Use when..." clause, natural SEO-audit keywords, and a concrete verification directive. Its main weaknesses are the grammatically awkward template phrase "related to Create a dedicated About page", a what-clause limited to verification, and generic leading triggers that risk overlap with sibling SEO rules.

Suggestions

Rewrite the mangled phrase "related to Create a dedicated About page" into a natural trigger, e.g. "Use when auditing whether a site has a dedicated About page with organization, mission, and contact information".

Add commonly used synonyms such as "SEO", "site audit", or "search engine visibility" to the trigger list so users phrasing the need generically still match.

State the full capability in the what-clause (audit for and create/fix a dedicated About page), not just the verification method, so the description answers "what does this do" completely.

DimensionReasoningScore

Specificity

"auditing metadata, crawlability, structured data, or indexability" and "Verify the rendered HTML and HTTP response rather than relying only on source files" list several specific concrete actions in the SEO-audit domain. Not 5 because coverage is one-sided (audit/verify only, no mention of the fix or reporting deliverables); not 3 because it goes beyond 1-2 actions to a list of distinct audit targets plus a concrete verification method.

4 / 5

Completeness

The "when" is explicit ("Use when auditing metadata, crawlability, structured data, or indexability related to Create a dedicated About page") and a "what" is present ("Verify the rendered HTML and HTTP response rather than relying only on source files"). Not 5 because the "what" only covers the verification method rather than the skill's full purpose, and the mangled phrase "related to Create a dedicated About page" weakens the trigger's explicitness; not 3 because both what and when are explicitly stated.

4 / 5

Trigger Term Quality

Natural keywords users would say are present: "metadata", "crawlability", "structured data", "indexability", "About page", "rendered HTML", "HTTP response". Not 5 because common variations like "SEO", "site audit", "search engine", or "ranking" are missing; not 3 because several relevant natural terms and synonyms are covered rather than just a couple of generic ones.

4 / 5

Distinctiveness Conflict Risk

The "About page" qualifier carves out a clear niche and a user asking about an About page would trigger this skill correctly. Not 5 because the leading generic triggers ("auditing metadata, crawlability, structured data, or indexability") overlap with sibling SEO-rule skills and could fire this skill for the wrong rule; not 3 because the distinctive About-page anchor term keeps it more specific than a generic category description.

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