CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

citations

Use when auditing metadata, crawlability, structured data, or indexability related to Cite authoritative external sources. Verify the rendered HTML and HTTP response rather than relying only on source files.

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/citations/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, lean instruction-only skill body with a clean Check/Fix/Explain/Code Review flow and exemplary use of a single well-signaled reference file. Minor gains are available by trimming the E-E-A-T background sentence and inlining one concrete citation example or verification step.

Suggestions

Trim or delete the opening E-E-A-T justification sentence; Claude already knows why authoritative citations matter for trust signals.

Inline one short good/bad citation example (or a concrete link-check action) in the Check or Fix section so the guidance is executable without opening the reference file.

Add an explicit verification checkpoint in the workflow, e.g. confirm each cited external link resolves (HTTP 200) and uses appropriate rel/target attributes.

DimensionReasoningScore

Conciseness

The body is lean and sectioned, but the opening sentence 'Citing authoritative sources is a key trust signal for E-E-A-T, demonstrating that your content is well-researched...' explains background Claude already knows and could be trimmed. Everything else earns its place, matching 'efficient; minor instances of over-explanation' rather than the fully lean anchor 5.

4 / 5

Actionability

Concrete, executable instruction-style guidance is present: 'Add external links to reputable websites (e.g., .gov, .edu, or industry leaders)', 'Use descriptive anchor text when linking', and 'Flag exact routes or templates where search-facing output violates the rule'. For an instruction-only skill the absence of inline code is acceptable since details live in references/rule.md, but no inline good/bad citation example keeps it below the fully executable anchor 5.

4 / 5

Workflow Clarity

The Check -> Fix -> Explain -> Code Review structure gives a clear, coherent sequence, and 'describe how to verify the final page output' serves as a verification checkpoint. It is below anchor 5 because there is no explicit validation step or feedback loop (e.g., confirming links resolve or are not broken), and above anchor 3 because the checkpoints are stated rather than merely implicit.

4 / 5

Progressive Disclosure

The body is a concise overview split into clear sections, and it points to a single one-level-deep reference that exists in the bundle ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which indeed holds the code example and detailed guidance. This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

66%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 an explicit, well-formed trigger clause and reasonable keyword coverage, but it reads like a merged template: the shared audit boilerplate dilutes what the skill actually does about citations. The distinctiveness and citation-specific trigger coverage are the main weaknesses.

Suggestions

Lead with what the skill does about citations specifically (e.g., 'Check that factual claims are backed by links to authoritative external sources and add missing citations'), keeping the rendered-HTML verification note as supporting detail.

Add citation-specific natural trigger terms users would say, such as 'external links', 'citations', 'outbound links', 'authoritative sources', or 'E-E-A-T'.

Differentiate from sibling SEO audit skills by making the citation trigger primary rather than the generic 'metadata, crawlability, structured data, or indexability' list, which would match many other rules in the same family.

DimensionReasoningScore

Specificity

The description names the domain ('auditing metadata, crawlability, structured data, or indexability') and only about two concrete actions ('Verify the rendered HTML and HTTP response rather than relying only on source files'), so it matches the anchor for domain plus 1-2 concrete actions but not comprehensive coverage. It is above anchor 2 because the verify-rendered-output action is specific rather than minimal or generic, but below anchor 4 because it does not list several distinct actions.

3 / 5

Completeness

Both parts are explicitly present: an explicit 'Use when auditing...' trigger clause and a 'what' ('Verify the rendered HTML and HTTP response rather than relying only on source files'). It is not a 5 because the 'what' describes generic audit procedure rather than clearly stating what the skill does about citing authoritative external sources.

4 / 5

Trigger Term Quality

Natural, user-sayable terms are present ('metadata', 'crawlability', 'structured data', 'indexability', 'rendered HTML', 'HTTP response'), giving good keyword coverage for the SEO-audit context. It falls short of anchor 5 because citation-specific synonyms users would naturally say ('external links', 'citations', 'outbound links', 'E-E-A-T', 'sources') are missing or only appear in the awkwardly embedded rule title 'Cite authoritative external sources'.

4 / 5

Distinctiveness Conflict Risk

The trigger set 'metadata, crawlability, structured data, or indexability' reads as boilerplate shared across a whole family of SEO audit rules, so a request about structured data or crawlability would plausibly trigger this citations skill over its siblings. The phrase 'Cite authoritative external sources' does give it a specific niche, placing it at 'somewhat specific but could still overlap with similar skills' rather than the mostly-distinct anchor 4.

3 / 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/citations/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.