CtrlK
BlogDocsLog inGet started
Tessl Logo

webspec-index

Use webspec-index to query WHATWG, W3C, IETF and TC39 web specifications from the command line

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/webspec-index/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The body is highly actionable with comprehensive executable command examples and clear sequenced workflows including validation steps. Its main weakness is mild redundancy in a few examples that could be tightened for token efficiency.

Suggestions

Remove the duplicate `webspec-index query 'DOM#concept-tree'` example in the look-up section to avoid redundancy.

In the Gecko usage-patterns section, reference already-shown command forms rather than re-listing full invocations, or cross-link to the Commands section.

Consider moving the more advanced topics (WHATWG PR previews, graph traversal) into a reference file to keep the main body leaner.

DimensionReasoningScore

Conciseness

Mostly efficient command examples, but includes redundancy such as the literal duplicate `webspec-index query 'DOM#concept-tree'` (lines 36 and 39) and re-shown commands in the Gecko usage section that could be trimmed.

3 / 5

Actionability

Fully executable, copy-paste-ready commands with specific examples covering the common cases across query, search, exists, anchors, list, refs, idl, and graph traversal.

5 / 5

Workflow Clarity

The Gecko usage section gives clear sequenced workflows with explicit Step 1/Step 2 numbering and validation cues (exit-code `exists` checks, `&& echo "valid"`); minor validation gaps remain in a few workflows.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers grouping commands and usage patterns; no nested or buried references and no bundle files, though ~250 lines of inline content could arguably be split for some advanced topics.

4 / 5

Total

16

/

20

Passed

Description

57%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 is clear and distinctive about what the tool does but omits any explicit "Use when..." trigger guidance, which caps its completeness. Trigger-term coverage is adequate but lacks common natural phrasings users would actually say.

Suggestions

Add an explicit trigger clause, e.g. "Use when you need to look up what a web spec says, verify a spec anchor, or trace cross-references between standards."

Broaden natural trigger terms to include phrases users say such as "web spec", "spec section", "web standard", or "spec algorithm".

Optionally enumerate the concrete capabilities (query, search, exists, refs) so the description conveys more than a single action.

DimensionReasoningScore

Specificity

Names the domain (WHATWG/W3C/IETF/TC39 web specs) and one concrete action ("query ... from the command line"), but only a single action with no enumeration of capabilities — matching the score-3 anchor.

3 / 5

Completeness

Clearly states what the tool does ("query ... web specifications from the command line") but provides no "Use when..." trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant terms ("web specifications", "command line", the four standards-body names) but misses common natural phrasings a user would say (e.g. "what does a spec say", "spec section", "web standard").

3 / 5

Distinctiveness Conflict Risk

Names a specific CLI tool and four named standards bodies, carving a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

14

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mozilla/enterprise-firefox
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.