skill-authoringlisted

# Managed skill authoring Use this explicit maintainer workflow to create, adapt, or substantially revise an agent skill. Edit only authoritative repository source, never a generated local projection. ## 1. Capture intent Extract established requirements and corrections from the conversation before asking questions. Confirm only unresolved decisions: - capability, user outcome, and non-goals; - situations that should and should not activate it; - inputs, outputs, side effects, tools, and permissions; - objective and subjective success criteria; - supported agents, modes, licensing, and payload constraints. Collect realistic examples, edge cases, and near-misses. Trigger boundaries must be distinguishable and testable. ## 2. Prefer consolidation Search the owned inventory first. Prefer improving an existing skill, folding a small rule into its domain owner, or adapting an audited source. Create a new skill only for a distinct reusable capability. For upstream material, record commit, paths, license evidence, adaptations, and omissions. Keep provenance repository-only and ship one legally sufficient shared notice. Reject mutable guidance, undeclared services, redundant skills, and unreviewed scripts. ## 3. Minimize disclosure and payload Descriptions may be always visible, `SKILL.md` loads on activation, and every reference, script, or asset is stored and synchronized even if unread. Keep `SKILL.md` as the shortest complete workflow. Add a reference only when the act