skill-enabler

Batch-enable Aeon skills in aeon.yml and open an operator-reviewed PR.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill skill-enabler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-enabler
Source: https://github.com/aaronjmars/aeon/tree/main/skills/skill-enabler
Command: npx skills add https://github.com/aaronjmars/aeon --skill skill-enabler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive friction of manually editing aeon.yml to flip multiple skills from enabled:false to enabled:true, including the validation and PR workflow that operators otherwise have to do one-by-one.

Core Features & Use Cases

  • Batch enable with guardrails: Enables a comma-separated list of skill slugs only when each slug exists, is disabled, and is not referenced under chains to prevent double-runs.
  • Validation-first execution: Fails loudly when slugs are missing directories, not present in aeon.yml, already enabled, or otherwise unparseable, and supports dry-run validation.
  • Operator-approved rollout: Writes a new branch, commits the aeon.yml change, and opens a PR with per-skill rationale and a clear eligible/ineligible breakdown.
  • Use Case: When preparing an autonomous “operator sprint,” you can enable several previously staged skills in one dispatch, get a single PR for review, and activate them on the next scheduled tick after merge.

Quick Start

Enable two skills by dispatching skill-enabler with var set to skill-a,skill-b (optionally using dry-run:skill-a,skill-b first to validate without committing).

Frequently Asked Questions about skill-enabler

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch enable multiple skills in aeon.yml with a single pull request?

To batch enable skills, you provide a comma-separated list of slugs as input to trigger a workflow_dispatch, which patches aeon.yml and opens a single GitHub PR for operator review.

Can I validate skill slugs before committing changes to aeon.yml?

Yes, dry-run validation checks that slugs exist, are disabled, and avoid chain conflicts without writing a Git branch or opening a GitHub PR.

Why does enabling a skill fail when it is already referenced under chains?

Enabling a skill fails when referenced under chains to prevent double-runs and chain conflicts, ensuring strict slug-scoped patching and safe autonomous agent workflows.

Does the skill enablement workflow support manual dispatch only?

Yes, skill enablement requires workflow_dispatch-only execution with explicit opt-in via a non-empty comma-separated variable, ensuring operators control autonomous agent activations.

What happens if a skill slug directory is missing during configuration management?

If a skill slug directory is missing, the workflow fails loudly during validation and reports the slug as ineligible, providing an eligible versus ineligible breakdown in the GitHub PR.