CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

using-lynx-api-docs

Authoritative Lynx engine references for generating, reviewing, migrating, or debugging Lynx TSX/TTML pages, CSS, layouts, selectors, and elements. Use for Lynx-specific styling and Web-to-Lynx differences; always retrieve the relevant installed docs before changing code.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 instruction/routing skill: concrete file-level routing, Lynx-specific defaults instead of general-knowledge padding, and a scoped repair workflow with a pre-answer verification step. The only improvements are consolidating the repeated retrieval-discipline instructions and adding a fallback step when documentation does not resolve a defect.

DimensionReasoningScore

Conciseness

The body is lean and Lynx-specific with no explanations of concepts Claude already knows, but the retrieval-discipline message is repeated three times ("Follow its exact topic links instead of loading the entire documentation bundle", "Diagnose before expanding retrieval", "Read only topics tied to the observed defect") and could be consolidated. Efficient overall with only minor trimming opportunities, matching the score-4 anchor rather than the every-token-earns-its-place score-5 anchor.

4 / 5

Actionability

Highly actionable for an instruction-only skill: the routing table maps each task to exact file paths (e.g. "lynx-vs-web/css-differences.md", "css/supported-properties.md and css/values-and-units.md"), and the defaults are concrete rules ("Use <view>, <text>, and <image>, not HTML elements; wrap text in <text>", "Lynx defaults to Linear layout", "Margins do not collapse"). Guidance is specific and executable with no gaps.

5 / 5

Workflow Clarity

Both the generation and repair flows are clearly sequenced — diagnose and route symptoms first, read only diagnosed topics, change only what the defect requires — with an explicit pre-answer validation checkpoint ("compare the result with the original and remove every edit not required by the diagnosis"). Not a 5 because there is no error-recovery feedback loop for the case where the retrieved documentation does not resolve the observed defect.

4 / 5

Progressive Disclosure

The SKILL.md is a concise overview that routes tasks to well-signaled, one-level-deep topic files (css/, layout/, elements/, patterns/, examples/), with no nested or chained references and easy task-based navigation. No bundle directory was provided in the evaluation context, so this is scored on the reference structure alone; it fully matches the clear-overview anchor.

5 / 5

Total

18

/

20

Passed

Description

86%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 strong description: it uses third-person voice, states concrete actions over specific Lynx artifact types, and includes an explicit "Use for" trigger clause. The only notable gap is that the when-clause covers fewer triggers than the what-clause enumerates.

DimensionReasoningScore

Specificity

Names the domain and four concrete actions ("generating, reviewing, migrating, or debugging") across five artifact types ("Lynx TSX/TTML pages, CSS, layouts, selectors, and elements"), with only minor coverage gaps. Not a 5 because "Authoritative Lynx engine references" characterizes the resource rather than enumerating additional concrete actions.

4 / 5

Completeness

Both what ("Authoritative Lynx engine references for generating, reviewing, migrating, or debugging...") and when ("Use for Lynx-specific styling and Web-to-Lynx differences") are explicitly present, satisfying the trigger-guidance floor. Not a 5 because the when-clause omits several what-clause triggers (layouts, selectors, elements, generating, reviewing), so it could be more explicit.

4 / 5

Trigger Term Quality

Covers the natural terms a Lynx user would say — "Lynx TSX/TTML pages, CSS, layouts, selectors, and elements", "Lynx-specific styling", "Web-to-Lynx differences" — including formats (TSX/TTML) and synonyms (styling). It does not fit the score-4 anchor since no common natural phrasing for this niche is missing.

5 / 5

Distinctiveness Conflict Risk

"Lynx engine", "TSX/TTML", and "Web-to-Lynx differences" form a clear niche with distinct triggers that no generic web/CSS skill would match, giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

lynx-family/lynx

Path

ai/skills/lynx-api-docs/skills/using-lynx-api-docs/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.