| name | skills-constitution |
| description | Define governance for creating, updating, and auditing skills. Use whenever a task involves skill design standards, change control, quality evaluation, or generating skill assessment reports. |
Skills Constitution
Purpose
Use this skill as the governance entrypoint for skill lifecycle management:
- Create new skills with consistent structure and trigger quality.
- Update existing skills with compatibility and regression control.
- Audit skills with a weighted rubric and produce standardized reports.
Scope And Boundaries
- Keep this file minimal: only core principles and routing.
- Put all operational details in
references/ module documents.
- Do not invent business rules when requirements are unclear; clarify first.
- Prioritize practical, maintainable, and non-over-engineered guidance.
- Keep folder conventions aligned with spec: prefer
references/, assets/, and scripts/; avoid creating extra top-level folders unless necessary.
Core Principles
- Clarity first: every rule must be actionable and testable.
- Single source of truth: each topic has one owner document.
- Backward safety: updates must evaluate trigger/behavior regressions.
- Evidence-based quality: audits require reproducible evidence, not opinions.
- Iterative improvement: evaluate, fix, and re-evaluate until pass criteria are met.
Module Routing
Read the following modules based on user intent:
- Create a new skill
- Update an existing skill
- Audit and evaluate a skill
- Generate a formal assessment output
Quick Decision Flow
- Identify whether the request is create, update, or audit.
- Route immediately to the corresponding module.
- Execute module checklist and collect evidence.
- If audit is required, score with rubric and output report template.
Minimal Output Contract
For any lifecycle task, always provide:
- Chosen module and why it applies.
- Completed checklist items.
- Risks or open questions.
- Final status (pass / needs revision) with next actions.