Resources — skills, hooks, sub-agents, rules, commands

Phases 4.2–4.6 + 7.1 · designs: resource management · plugin source & trust

Everything a profile can bundle besides MCP servers lives in one resources store with a kind discriminator: skill, sub_agent, rule, command, hook (MCP servers are managed separately).

Common model

• Identified by kind:key handles; uniqueness is per (key, scope, owner).
• kind and scope are immutable after create — mutate by recreate.
• Scope rules as everywhere: global = admin-mutate / all-read, personal = owner-only.
• Editors produce inline content (markdown) or, for multi-file skills, inline-bundle (SKILL.md + references/ + scripts/).

Kinds

• skill — single file or bundle; may also come from a marketplace as a plugin source (see Skill hub) carrying a computed trust tier (builtin / trusted / community) plus optional pin/provenance.
• sub_agent / rule / command — single-file inline markdown.
• hook — a hooks.json document (event → command map). The supported events depend on the declared target agent; the event × target matrix is data, so adding support is a table edit, not a code change.

Where they go

Resources are consumed two ways: bundled into profiles for deployment, and scanned back in from machines during inventory import.