CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

llm-parsability

Use when auditing content pages for AI discoverability. Applies to any informational page intended to appear in AI-generated answers, search snippets, or knowledge base extraction.

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/llm-parsability/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 tight, well-structured skill body with an exemplary progressive-disclosure split — a concise overview that defers examples to a real, clearly labeled reference file. Its weaknesses are a fully duplicated check list (Check vs. Code Review) and an Explain section that tells Claude things it already knows.

Suggestions

Merge the "Check" and "Code Review" sections — they list the same five checks (heading hierarchy, semantic elements, JS-free content, JSON-LD, hidden content) — and keep one as the audit list.

Trim or repurpose the "Explain" section: that LLMs extract text from HTML and prefer semantic markup is background Claude already has; keep only the checklist-specific rationale.

Add one minimal inline example (e.g., a two-line JSON-LD FAQPage snippet) so the body's most important fix is executable without opening the reference.

DimensionReasoningScore

Conciseness

The body is mostly lean, but "Check" and "Code Review" repeat nearly the same five items (heading hierarchy, semantic elements, content visible without JS, JSON-LD, hidden modal/tab content), and "Explain" restates concepts Claude already knows ("Large language models and answer engines process web content by extracting text from HTML"). It could be meaningfully tightened, so it sits below the efficient anchor 4.

3 / 5

Actionability

Guidance is concrete and specific — exact tags to check ("<h1>–<h6>, <p>, <ul>, <ol>, <table>"), exact schema types ("JSON-LD schema (Article, FAQPage, HowTo)"), and specific fixes ("Replace JavaScript-rendered content with server-side rendered HTML"). It stops short of fully executable copy-paste material in the body since all code examples are deferred to references/rule.md, so it does not reach anchor 5.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review flow gives a clear sequence for a simple, single-purpose audit skill, and no validation cap applies since the task is non-destructive. However, the near-duplicate "Check" and "Code Review" lists leave mild ambiguity about which list actually drives the audit, keeping it below the fully unambiguous anchor 5.

4 / 5

Progressive Disclosure

The 45-line body is a well-organized overview with a clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`". The referenced file exists and holds the good/bad HTML examples and detailed guidance, exactly the split the top anchor rewards.

5 / 5

Total

16

/

20

Passed

Description

70%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 solid description with an explicit "Use when" trigger and natural, domain-appropriate keywords. Its main weakness is that the capability side stays abstract — "auditing for AI discoverability" without naming the concrete checks the skill actually performs.

Suggestions

Enumerate the concrete actions in the description (e.g., "Checks semantic HTML structure, JavaScript-free content access, and JSON-LD structured data for LLM extractability") to raise specificity.

Add natural trigger synonyms users actually say, such as "LLM visibility", "AI Overviews", "answer engine optimization", or "generative engine optimization (GEO)", to broaden trigger coverage.

Mention what the skill produces (e.g., an audit report or a fix list) so the 'what' is as concrete as the 'when'.

DimensionReasoningScore

Specificity

The description names the domain and a single concrete action ("auditing content pages for AI discoverability") but never enumerates the underlying checks it performs (semantic HTML, server-rendered content, JSON-LD). It matches the "1-2 concrete actions, but not comprehensive" anchor rather than the several-specific-actions anchor above.

3 / 5

Completeness

It answers both parts: the what is "auditing content pages for AI discoverability" and the when is explicit via "Use when auditing content pages...". The 'when' is explicit but the 'what' stays high-level without concrete trigger sub-tasks, so it does not reach the fully explicit anchor 5.

4 / 5

Trigger Term Quality

It includes natural phrases users would say — "AI-generated answers", "search snippets", "knowledge base extraction", "AI discoverability" — giving good keyword coverage. Not a 5 because common synonyms such as "LLM visibility", "AI Overviews", or "generative engine optimization" are missing.

4 / 5

Distinctiveness Conflict Risk

"AI discoverability" and "AI-generated answers" carve out a fairly distinct niche with clear triggers, distinct from generic file-processing skills. Minor overlap risk remains with broader SEO/structured-data skills, so it is mostly distinct rather than a clear no-conflict niche.

4 / 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/llm-parsability/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.