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.
86
80%
Does it follow best practices?
Impact
98%
1.30xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/bikeshed-conversion/SKILL.mdBikeshed dfn ID preservation on concepts and algorithms
Explicit dfn IDs present
100%
100%
Concept ID pattern
100%
100%
Algorithm ID pattern
100%
100%
Compound concept ID
100%
100%
IDL typedef ID pattern
0%
100%
IDL block ID pattern
100%
100%
data-export on concept dfns
0%
100%
No bare auto-generated dfns
100%
100%
Valid Bikeshed dfn syntax
70%
100%
IDL attribute dfn keyword and dfn-for parent dl
attribute keyword on dfns
100%
100%
dfn-for on parent dl
100%
100%
Explicit IDs on attribute dfns
0%
100%
Interface dfn ID preserved
0%
100%
IDL blocks present
100%
100%
No missing id attributes
20%
100%
data-export present
100%
100%
No bare auto-generated attribute dfns
50%
100%
Valid Bikeshed dl structure
100%
100%
dom-{interface} id pattern
0%
100%
Scoped dfn IDs preserved with data-dfn-for
Scoped dfns have explicit IDs
100%
100%
wall-clock scoped IDs preserved
100%
100%
monotonic-clock scoped IDs preserved
100%
100%
Parent concept dfn IDs
100%
100%
Compound concept ID
100%
100%
data-dfn-for used on scoped dfns
100%
100%
No dfn missing id
100%
100%
Scoping and id coexist
100%
100%
Valid Bikeshed dfn syntax
100%
100%
data-export on exported dfns
0%
0%
415abe6
Table of Contents
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.