contributing

To safely modify skills in .claude/skills without breaking the lockfile, follow a structured checklist that enforces frontmatter validity, hook compatibility, and idempotency standards before submitting changes.

Required frontmatter for a new skill must include a valid name and description. The system checks for these required fields and validates optional resources like scripts, references, and assets when present.

You validate skill changes for hook contracts and idempotency by applying a checklist that verifies frontmatter structure, checks required sections, and aligns modifications with evidence standards across all skill categories.

You need a skill contribution guide when introducing a new skill or updating an existing one in .claude/skills, ensuring your changes land cleanly without disrupting lockfile accuracy or existing hook contracts.

Limitations when updating skills include maintaining strict lockfile integrity and avoiding hook contract violations. Changes must enforce a consistent structure and cannot bypass frontmatter validity or idempotency requirements.