ayobamiseun 0898b52faa feat(validator): reject frontmatter keys outside the Agent Skills spec set ...

docs/advanced-per-agent-configuration.md says vendor and runtime fields
such as model, tools, max_turns and context must not appear at the top
level of a SKILL.md: hosts do not promise to ignore unknown keys and a
strict client can reject the file. Nothing enforced it; a skill with
model: at the top level passed CI.

Add SPEC_FRONTMATTER_KEYS (name, description, license, compatibility,
metadata, allowed-tools) and an error for any other column-zero key,
naming the key and pointing at the guide. Nested lines under metadata and
list items are children of a spec key and are left alone. Export
topLevelFrontmatterKeys for direct tests. validate-commands.js shares only
frontmatterYamlErrors, so command frontmatter is unaffected.

All 25 skills use only name and description, so the rule fires on nothing
today and follows the #571 pattern of errors for rules nothing violates.
The self-exemption test now expects two errors, since exempt: is also not
a spec key.

2026-09-26 18:53:01 +01:00

..

skill-lint-test.js

feat(validator): reject frontmatter keys outside the Agent Skills spec set

2026-09-26 18:53:01 +01:00

skill-lint.js

feat(validator): reject frontmatter keys outside the Agent Skills spec set

2026-09-26 18:53:01 +01:00