Skills are missing the frontmatter and regulatory function their contract requires

The skill document contract requires #+type: skill and #+level: cross in frontmatter, and requires each skill to declare the regulatory function it implements, on the grounds that a skill is the one document type whose function cannot be inferred from its type.

Fifty-one of eighty skills carry neither frontmatter field. None of the eighty declares a regulatory function. The scaffold compass add skill emits neither, which is why the gap is uniform rather than scattered.

The declaration is not decoration. Regulatory Functions states that a skill may be a principle, a method or an action, so its function genuinely cannot be read off the type. Dispatch depends on knowing which, and the attenuator that selects a slice of the catalogue by level depends on the level field.

Both are therefore prerequisites of work already planned rather than tidiness. The catalogue cannot be attenuated by level while most skills carry no level, and it cannot be dispatched over while none declares what it implements.

Fix the scaffold first, so new skills are correct on creation, then sweep the existing eighty. The sweep is mechanical for the frontmatter and a judgement per skill for the function.

• Document type: skill — the contract these skills do not meet.
• Regulatory Functions — why the declaration cannot be inferred.

• Skill naming conventions — the other policy the registers govern.