Night evolve skills
One iteration tackles one bounded hypothesis, using manage-skills, history-learning, review-code
for the craft. Read the shared contract in ../night/references/loop-interface.md;
this skill supplies the target, evidence and stopping rules.
Activation
- Use for a skill catalog with failures.jsonl, learnings.md or repeated correction evidence.
- Use
history-learning only within existing source consent; unsupported preferences are not rules.
- Read the handoff first and avoid repeating a target resolved by earlier iterations.
Workflow
- Baseline: Use
manage-skills to select one repeated failure pattern with evidence references and frequency.
- Choose: Never modify
skills/night, skills/night-evolve-skills or any running watchdog/supervisor script.
- One change: Represent protected edits as a proposal file in
NIGHT_RESULT.report, never write it to disk;
alternatively validate an authorised isolated worktree copy. Only a human applies those edits.
- Check: For an unprotected skill, make one evidence-backed edit; use
review-code and the catalog validator.
- Hand back: run fast checks and report evidence, including unavailable or failed commands.
The supervisor re-runs checks and decides keep/revert; never weaken tests or assertions.
Evaluation
- Keep: Run
node scripts/validate.mjs when present; validation passes and the cited failure scenario improves.
- Revert: Protected running code changes, unsupported generalisations, alias collisions or validator failures.
- Inconclusive: missing evidence or unavailable checks cannot count as a successful iteration.
- Record baseline and candidate results with exact commands for the supervisor to repeat.
- Creative skills (revamp-ui, build-ui, add-interactions, build-animation, build-3d, create-visuals, replicate-design, audit-design): also run
node --test tests/creative-evals.test.mjs; the held-out cases in evals/creative/routing.json are evidence only and are never edited or tuned against. Repeated defects come from the creative ledger (~/agent-skills/shared/creative/learning.md).
Stop conditions
- Only protected changes remain: return proposals for a human; never self-apply them.
- No repeated failure has a bounded remedy, or required validation cannot run.
- Stop at the supplied time or iteration limit; report the next bounded hypothesis.
Examples
- Day: "run night-evolve-skills on the catalog routing failures" investigates one target with the owner watching.
- Night:
/night evolve-skills repeats bounded iterations within the supplied budget, with each
outcome independently evaluated by the supervisor.
End the final message with NIGHT_RESULT: {json} using the shared contract's fields.
Report evidence rather than grading your own result. Include changed paths and reproducible checks.
1---2name: night-evolve-skills3description: Skill-evolution loop. Improve one catalog skill from recorded failures and repeated corrections, validate the edit, and reserve changes to the active loop or engine for human application. Use for "night-evolve-skills", "night evolve skills" or as /night evolve-skills.4metadata:5 source: https://skillmd.com/skills/amsborse/night-evolve-skills6 aliases: "night-evolve-skills, night evolve skills"7 keywords: "night, loop, evolve, skills"8 composes: "manage-skills, history-learning, review-code"9 requires: "git, shell"10 risk: "high"11 night-loop: "evolve-skills"12 night-writes: "code"13 night-minutes: "30"14 night-signals: "skills"15---1617# Night evolve skills1819One iteration tackles one bounded hypothesis, using `manage-skills`, `history-learning`, `review-code`20for the craft. Read the shared contract in `../night/references/loop-interface.md`;21this skill supplies the target, evidence and stopping rules.2223## Activation2425- Use for a skill catalog with failures.jsonl, learnings.md or repeated correction evidence.26- Use `history-learning` only within existing source consent; unsupported preferences are not rules.27- Read the handoff first and avoid repeating a target resolved by earlier iterations.2829## Workflow30311. **Baseline:** Use `manage-skills` to select one repeated failure pattern with evidence references and frequency.322. **Choose:** Never modify `skills/night`, `skills/night-evolve-skills` or any running watchdog/supervisor script.333. **One change:** Represent protected edits as a proposal file in `NIGHT_RESULT.report`, never write it to disk;34 alternatively validate an authorised isolated worktree copy. Only a human applies those edits.354. **Check:** For an unprotected skill, make one evidence-backed edit; use `review-code` and the catalog validator.365. **Hand back:** run fast checks and report evidence, including unavailable or failed commands.37 The supervisor re-runs checks and decides keep/revert; never weaken tests or assertions.3839## Evaluation4041- Keep: Run `node scripts/validate.mjs` when present; validation passes and the cited failure scenario improves.42- Revert: Protected running code changes, unsupported generalisations, alias collisions or validator failures.43- Inconclusive: missing evidence or unavailable checks cannot count as a successful iteration.44- Record baseline and candidate results with exact commands for the supervisor to repeat.45- Creative skills (revamp-ui, build-ui, add-interactions, build-animation, build-3d, create-visuals, replicate-design, audit-design): also run `node --test tests/creative-evals.test.mjs`; the held-out cases in `evals/creative/routing.json` are evidence only and are never edited or tuned against. Repeated defects come from the creative ledger (`~/agent-skills/shared/creative/learning.md`).4647## Stop conditions4849- Only protected changes remain: return proposals for a human; never self-apply them.50- No repeated failure has a bounded remedy, or required validation cannot run.51- Stop at the supplied time or iteration limit; report the next bounded hypothesis.5253## Examples5455- Day: "run night-evolve-skills on the catalog routing failures" investigates one target with the owner watching.56- Night: `/night evolve-skills` repeats bounded iterations within the supplied budget, with each57 outcome independently evaluated by the supervisor.5859End the final message with `NIGHT_RESULT: {json}` using the shared contract's fields.60Report evidence rather than grading your own result. Include changed paths and reproducible checks.