evolve

Records per-user adjustments to installed aos capabilities in MOD.md so they survive upgrades.

3|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/AlmogBaku/aos --skill evolve-almogbaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evolve
Source: https://github.com/AlmogBaku/aos/tree/main/capabilities/capability-lifecycle/skills/evolve
Command: npx skills add https://github.com/AlmogBaku/aos --skill evolve-almogbaku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you tweak an installed aos capability — rescheduling a job, changing a threshold, adjusting a tone — a hand-edit to the rendered files gets silently wiped out by the next upgrade. This Skill captures every per-user change into a MOD.md overlay file so your personalizations persist across every upgrade. ## Core Features & Use Cases - Change classification: Routes each request to the right place — updating an onboarding answer, rewriting an existing MOD statement, adding a new imperative statement, or handing upstream fixes to the contribute skill. - Overlay-first writes: Writes the MOD.md change before applying it to the pinned render, then refreshes recorded hashes with aos-cap rehash so verification stays clean. - Capture mode: When drift is detected (a hand-edited render), folds the existing on-disk change back into MOD.md so upgrades no longer drop it. - Use Case: You ask your agent to make the steward capability run at 22:00 instead of the default. The Skill records the new schedule in your MOD.md, applies it to the render, and confirms it will survive every future upgrade. ## Quick Start Ask your agent to change an installed capability's behavior, for example: make the steward run at 22:00 and record it so it survives upgrades.

Frequently Asked Questions about evolve

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

FAQPage Schema
How do I change an installed aos capability without losing the change on upgrade?▼

Ask for the change in natural language, such as rescheduling a job or adjusting a threshold. The Skill writes the change to your MOD.md overlay first, then applies it to the pinned render, so every future upgrade re-applies your customization.

What is the MOD.md file in aos capabilities?▼

MOD.md is the per-user overlay that states your desired differences from the shipped capability defaults. It is edited in place rather than appended, only states differences from defaults, and is re-applied on every upgrade.

What happens if I hand-edit a capability's rendered files directly?▼

A hand-edit exists on disk but nowhere in the overlay, so the next upgrade silently drops it. Capture mode detects this drift and folds the existing change back into MOD.md without re-applying it to the render.

When should a change go upstream instead of into my MOD.md?▼

If the change fixes an upstream bug or is explicitly meant for all users, it is handed to the contribute skill, which modifies the shipped source with approval gating. Nothing lands in your MOD.md for upstream changes.

Does the evolve skill install, upgrade, or remove capabilities?▼

No. Installation, upgrade, and removal are handled by their own dedicated skills. This Skill only adjusts the behavior of an already-installed capability and records the adjustment in the overlay.