CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-content

Use when auditing metadata, crawlability, structured data, or indexability related to Audit and refine AI-generated content. Verify the rendered HTML and HTTP response rather than relying only on source files.

60

Quality

70%

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

Quality

Content

62%

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

The content is a clean, brief overview that uses progressive disclosure well with a single real one-level reference, but its top-level guidance is instruction-only without executable specifics and the workflow lacks explicit validation checkpoints, capping actionability and workflow clarity.

Suggestions

Move or trim the conceptual restatement in the intro and the duplicated 'verify rendered HTML' guidance so the body adds only what is not already obvious.

Add one concrete, executable verification step at the top level (e.g., a command to fetch rendered HTML or inspect a specific meta/byline tag) rather than deferring all specifics to rule.md.

Add an explicit validation checkpoint to the workflow (e.g., 'After rewriting, re-check rendered HTML and confirm factual claims before treating the rule as satisfied').

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-sectioned, but it restates concepts Claude already knows ('Search engines prioritize helpful, reliable, people-first content') and the 'Code Review' section partly duplicates the description's verify-rendered-HTML guidance, so it could be tightened.

2 / 3

Actionability

It gives some concrete direction ('Review the content to see if it provides unique value', 'Rewrite AI-generated sections to include original research, personal experiences'), but the guidance is instruction-level with no concrete command, selector, or executable example in SKILL.md itself (those live in rule.md), leaving key details missing at the top level.

2 / 3

Workflow Clarity

Quick Reference / Check / Fix / Explain sections imply a sequence, but there are no explicit validation checkpoints or error-recovery loops at the SKILL.md level for what is a review-and-revise workflow; the verification detail is deferred to the reference.

2 / 3

Progressive Disclosure

The body is a short overview that signals a single one-level-deep reference ('see references/rule.md'), the referenced file exists, and content is appropriately split rather than inlined, matching the anchor for a clear overview with well-signaled one-level-deep references.

3 / 3

Total

9

/

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 is reasonably specific and includes an explicit 'Use when' trigger with both what and when answered, but a malformed 'related to Audit and refine AI-generated content' fragment reads like a template bug and weakens natural trigger-term quality and distinctiveness.

Suggestions

Rewrite the description as clean prose — the phrase 'related to Audit and refine AI-generated content' appears to be an accidentally concatenated rule title and should be integrated into a natural sentence.

Add broader natural trigger terms a user would actually say (e.g., 'AI content', 'AI-generated text', 'helpful content review', 'E-E-A-T') alongside the current SEO jargon.

Sharpen the niche so it is distinguishable from generic crawlability/structured-data skills, e.g., emphasize reviewing AI-generated or AI-assisted content specifically.

DimensionReasoningScore

Specificity

Names 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 anchor for listing several specific concrete actions.

3 / 3

Completeness

It explicitly answers both what to do (audit/verify rendered HTML and HTTP responses) and when (the explicit 'Use when ...' clause), satisfying the anchor for clearly answering both.

3 / 3

Trigger Term Quality

It opens with 'Use when auditing metadata, crawlability, structured data, or indexability', providing relevant trigger terms, but the vocabulary is SEO-jargon-heavy and the garbled 'related to Audit and refine AI-generated content' fragment is not a natural user phrase, so common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The metadata/crawlability/structured-data framing is SEO-specific, but these terms overlap heavily with sibling SEO crawlability skills, so it could still trigger for the wrong skill rather than occupying a clearly distinct niche.

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.