bikeshed-conversion

Guidelines for converting W3C specs to Bikeshed format. Covers anchor ID preservation, dfn handling, and common pitfalls. Read this before any Bikeshed conversion or migration work.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/SKILL.md

Quality

Content

85%Scale 1-3

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

This is a well-crafted, focused skill that addresses a specific and non-obvious pitfall in Bikeshed conversion. Its strengths are the concrete HTML examples, the comprehensive ID pattern table drawn from a real PR, and the clear verification checklist. The only weakness is mild redundancy between the introduction and the 'Problem' section, which could be consolidated.

Dimension	Reasoning	Score
Conciseness	The 'Problem' section explains cross-spec linking in a way that's somewhat redundant with the introduction. The content is mostly efficient but could be tightened—the problem/fix framing repeats the same point made in the opening paragraph.	2 / 3
Actionability	Provides concrete HTML examples (good vs bad), a detailed table of ID patterns with real examples from an actual PR, and a step-by-step checklist with specific tools (xref) and techniques. Fully actionable guidance.	3 / 3
Workflow Clarity	The checklist provides a clear 5-step sequence: inventory → check cross-refs → add IDs → verify build → check scoping. It includes a verification step (step 4) and addresses edge cases (step 5). For this type of task, the workflow is well-structured with appropriate validation.	3 / 3
Progressive Disclosure	For a focused, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections (Problem, Fix, Patterns table, Checklist). No bundle files are needed for this scope.	3 / 3
	Total	11 / 12 Passed

Description

75%Scale 1-3

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 effectively identifies a clear niche (W3C-to-Bikeshed conversion) and includes an explicit 'when to use' clause, making it strong on completeness and distinctiveness. However, it could be more specific about the concrete actions it covers and include more natural trigger term variations that users might employ when seeking this skill.

Suggestions

Add more specific concrete actions, e.g., 'Converts W3C ReSpec documents to Bikeshed (.bs) format, preserves anchor IDs, handles <dfn> elements, resolves cross-references, and avoids common formatting pitfalls.'

Include additional trigger term variations users might naturally say, such as 'respec', '.bs file', 'spec migration', 'markup format conversion', or 'Bikeshed markup'.

Dimension	Reasoning	Score
Specificity	Names the domain (W3C specs to Bikeshed format) and some actions (anchor ID preservation, dfn handling, common pitfalls), but doesn't list multiple concrete actions comprehensively—e.g., what specific conversion steps, what pitfalls, what outputs.	2 / 3
Completeness	Clearly answers both 'what' (guidelines for converting W3C specs to Bikeshed format, covering anchor ID preservation, dfn handling, pitfalls) and 'when' ('Read this before any Bikeshed conversion or migration work'), providing an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes relevant keywords like 'Bikeshed', 'W3C specs', 'conversion', 'migration', 'dfn', and 'anchor ID', but misses common variations users might say such as 'respec to bikeshed', '.bs files', 'spec format', or 'markup conversion'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche—Bikeshed format conversion for W3C specs is highly distinctive and unlikely to conflict with other skills. The trigger terms are domain-specific enough to avoid false matches.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: w3c/web-performance
Path: skills/SKILL.md
Commit: 415abe6

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.