What is broken
docs/spec/inspect/README.md defines skill as an AgBOM component type (line 38) but the "Triggers for AgBOM updates" section (line 79) lists seven triggers and none for a skill being registered, loaded, or unloaded.
Where
docs/spec/inspect/README.md, section "Triggers for AgBOM updates"
What the specification says, and what happens instead
The component table says a skill carries definition.ref and definition.digest and belongs in the AgBOM. hooks/skill-register.json and hooks/skill-unload.json describe registration and removal, and skillUnload is allowed to fold into agbom/changed. The trigger list should therefore read "Skill registered, unloaded, or definition-changed", but the list stops at seven component types and skill is the eighth.
Impact on implementers
An implementer reading only the trigger list emits no agbom/changed when a skill enters or leaves the component set, so the AgBOM drifts from the hook stream. Low severity, one-line fix; I found it while widening the hook-taxonomy guard in #63 and can send the PR.
Current Priority Scope
Feeds conformance evidence
What is broken
docs/spec/inspect/README.mddefinesskillas an AgBOM component type (line 38) but the "Triggers for AgBOM updates" section (line 79) lists seven triggers and none for a skill being registered, loaded, or unloaded.Where
docs/spec/inspect/README.md, section "Triggers for AgBOM updates"
What the specification says, and what happens instead
The component table says a
skillcarriesdefinition.refanddefinition.digestand belongs in the AgBOM.hooks/skill-register.jsonandhooks/skill-unload.jsondescribe registration and removal, andskillUnloadis allowed to fold intoagbom/changed. The trigger list should therefore read "Skill registered, unloaded, or definition-changed", but the list stops at seven component types and skill is the eighth.Impact on implementers
An implementer reading only the trigger list emits no
agbom/changedwhen a skill enters or leaves the component set, so the AgBOM drifts from the hook stream. Low severity, one-line fix; I found it while widening the hook-taxonomy guard in #63 and can send the PR.Current Priority Scope
Feeds conformance evidence