CtrlK
BlogDocsLog inGet started
Tessl Logo

affiliate-disclosure

Use when auditing metadata, crawlability, structured data, or indexability related to Provide clear affiliate disclosures. Verify the rendered HTML and HTTP response rather than relying only on source files.

63

Quality

75%

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

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, concise overview that uses progressive disclosure effectively to hand off detail to references/rule.md. Its main gaps are that the body itself offers no example disclosure text or markup and no in-body verification checkpoint.

Suggestions

Include one short copy-paste disclosure snippet or example phrasing directly in the Fix section so the body is self-sufficient for the common case.

Add a brief in-body verification step (e.g., "Confirm the disclosure renders in the DOM before affiliate links via view-source or a crawl") rather than leaving all verification to the reference.

Tighten the "Explain" section from a meta-instruction ("Explain the legal and ethical importance...") into a concise ready-to-use rationale.

DimensionReasoningScore

Conciseness

The body is lean with short purposeful sections (Quick Reference, Check, Fix, Explain, Code Review) and only a single brief contextual sentence; it assumes Claude's competence without over-explaining SEO basics.

3 / 3

Actionability

It gives concrete placement directives ("Place the disclosure at the top of the page, before any affiliate links appear") but provides no example disclosure wording or markup in the body, deferring specifics to the reference.

2 / 3

Workflow Clarity

The Check→Fix→Explain→Code Review sequence is clear, but the body lacks explicit validation/verification checkpoints, which are only present in the referenced file.

2 / 3

Progressive Disclosure

A concise overview body cleanly signals a single one-level-deep reference ("see `references/rule.md`") that exists on disk, with the rule page URL also linked.

3 / 3

Total

10

/

12

Passed

Description

77%

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 covers concrete actions and an explicit Use-when trigger, but is weighed down by jargon-heavy trigger terms and broad SEO-audit phrasing that risks overlap with sibling skills. The awkwardly embedded rule title "Provide clear affiliate disclosures" also muddies readability.

Suggestions

Rewrite the trigger to use natural phrasing a user would say, e.g. "Use when auditing a page for affiliate or sponsored-link disclosures," and lead with the affiliate-disclosure niche rather than generic SEO terms.

Fix the malformed sentence so "Provide clear affiliate disclosures" is not pasted mid-clause; integrate it as the subject of the audit.

Add common keyword variants ("sponsored links", "FTC disclosure", "SEO disclosure audit") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple 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 multi-action anchor.

3 / 3

Completeness

Explicitly states what it does (audit and verify SEO signals) and when to use it via a clear "Use when..." clause, satisfying both what and when.

3 / 3

Trigger Term Quality

Includes some natural terms ("affiliate disclosures", "rendered HTML") but leans on technical jargon ("indexability", "crawlability", "structured data") and omits common user phrasings like "SEO audit".

2 / 3

Distinctiveness Conflict Risk

The affiliate-disclosure niche is somewhat specific, but the broad trigger terms (metadata, crawlability, structured data, indexability) would overlap with sibling SEO rule skills.

2 / 3

Total

10

/

12

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.

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