skill-enabler

To enable disabled skills, you dispatch the task with a comma-separated list of slugs to flip enabled: false to enabled: true in aeon.yml. This validates slugs against the skills/ directory and generates a dedicated pull request.

The safest way to flip enabled flags for multiple slugs is using slug-scoped edits with dry-run validation. This approach ensures each slug exists in the skills/ directory, is currently disabled, and is not part of chains before applying a patch to aeon.yml.

The validation process guards against conflicts by checking that each slug is disabled, not part of chains, and not already enabled. It normalizes input through deduplication and trimming before applying safety gates and patching aeon.yml.

Yes, you can use dry-run validation to verify slugs and their state before changes are applied. This ensures each slug exists in the skills/ directory and meets all safety requirements before a final patch is generated.

A limitation is that skills already part of chains cannot be enabled. The safety gates explicitly block enabling any slug that is part of a chain, currently enabled, or missing from the skills/ directory to prevent conflicts.