Skill · v2.0
Autonomous Improvement Session
Autonomous Improvement Session is the skill you run when you have capacity to spare and want your system improving without watching it. You invoke it, it works, it shows you what it did and surfaces only the decisions that genuinely need you. The flywheel grows with every cycle.
Install
Claude Code (CLI / WSL / Git Bash)
/plugin marketplace add https://www.infinitegameos.io/marketplace.json
/plugin install autonomous-improvement-session@igos-libraryClaude Code (VS Code)
Install in VS CodeOpens the Claude Code plugins dialog with the marketplace and skill prefilled. Requires the Claude Code VS Code extension installed and signed in. Or paste the snippet below into .claude/settings.json for VS Code, JetBrains or any setup that prefers manual config.
{
"extraKnownMarketplaces": {
"igos-library": {
"source": {
"source": "url",
"url": "https://www.infinitegameos.io/marketplace.json"
}
}
},
"enabledPlugins": {
"autonomous-improvement-session@igos-library": true
}
}Direct markdown URL (Claude Code, Cursor, Codex CLI)
https://www.infinitegameos.io/markdown/skills/autonomous-improvement-sessionThis URL returns the narrative concept page. The plugin install path above delivers the operational SKILL.md instruction file.
Cursor (.mdc rules file)
curl -O https://www.infinitegameos.io/install/cursor/autonomous-improvement-session.mdcAider, Cline, any agent with --read
curl -O https://www.infinitegameos.io/markdown/skills/autonomous-improvement-session
aider --read autonomous-improvement-session.mdThis skill ships in both homes, the Sovereign Ecosystem Foundation and this library.
Definition
Autonomous Improvement Session is an operator-invoked hygiene and improvement engine. When you have extra capacity, you fire it and it runs a menu of safe, additive, system-internal work: broken references repaired in place, index entries added for active files, superseded files archived, inbox items routed. Every menu item carries one verb. Acts items land their edits. Reports items are read-only scans whose findings fold into the decision board. Proposes items wait for your yes and do not run. A verb moves only through a decision you ratify after reviewing a run. The menu is grouped into bundles that read the same surface, and two bundles run each time. Menu growth is fast and wide; execution authority is slow and earned. The decision board arrives in full as the run's closing message, in four buckets (Done, Your decisions, Your hands, Plans to approve), and the run log entry is its only stored copy. No report files land in your inbox. The run log entry and version control commit are the durable trail. It also ships inside the Sovereign Ecosystem Foundation, the starting workspace where these disciplines live together.
Two speeds on purpose
The skill runs at two speeds simultaneously. Menu growth is fast and wide: a research rotation casts a wide net for categories and mechanisms of improvement, and the menu of things the skill knows how to do grows every cycle. Execution authority is slow and earned: each item carries a verb, and a verb moves only through a decision you ratify after reviewing the board. A wide net for ideas. A narrow gate for action. The gate widens with proof, never with time.
Acts items execute and log. Reports items scan and report. Proposes items wait for you. The default verb is DO, not propose. If an action is additive, reversible, system-internal and touches no deletion, no canonical governance file and no outward surface, the skill does it and records it. Safe work is act-then-show. The Permanent Floor is the hard ceiling that holds whatever verbs you ratify: no deletions, no voice or copy changes on live surfaces, no outward broadcasts, no direct push to main, no self-modification.
The decision board and the return session
Every run closes with a four-bucket decision board, delivered in full in the closing message so you can answer it without opening a file. Done is a skim record: what ran, each item reversible. Your decisions holds the genuine judgment forks, anything near the Permanent Floor and the menu candidates the skill recommends. Your hands holds only what you alone can physically do. Plans to approve holds anything bigger than one session. Every decision carries the live check its claim passed. A clean run leaves Your decisions near empty, because safe work is already done.
The return session is how the flywheel learns. You answer decisions, encode forward rules, accept or decline menu candidates and ratify any verb moves. An accepted candidate adds a new menu item. A ratified move gives one item a new verb, one proven step at a time. The skill never edits its own menu or verbs autonomously, and every edit to its own files shows you the diff first. Every move is explicit and operator-triggered.
Use Cases
End-of-session hygiene when capacity remains
A build session wraps with tokens and time to spare. You invoke Autonomous Improvement. The skill checks eligibility across the starter menu, runs five reference-integrity repairs and two index additions, surfaces two ambiguous routing decisions and one menu candidate from the research rotation. You close the session knowing the system is cleaner than when you started and the decision board is waiting when you're ready.
Heading out with a messy system
You're leaving for a few hours and your system has accumulated drift: references that moved, index entries not added, inbox notes nobody routed. You fire Autonomous Improvement with a full-sweep hint. The skill works every due item, runs its read-only scans and renders the board in its closing message. You come back to a cleaner system and a decision board to skim, not a to-do list to build from scratch.
Growing the menu through the research rotation
After five runs the starter menu starts feeling thin relative to what the system actually accumulates. The research rotation surfaces a new candidate: broken wikilink detection across a notes directory. You review it in Your decisions, accept it and the return session adds it to a bundle with its verb. The next run includes the new item. The skill's reach grew through proven operation, not by assumption.
FAQ
Why operator-invoked only and never scheduled?
Scheduling is a future direction gated on a track record of clean review-and-climb cycles, not a date. Autonomous improvement on a cron job with unproven verbs is a liability. Operator invocation keeps you in the loop until the track record has earned the right to run without you watching. The cadence comes after the proof.
What is the Permanent Floor and why does it never move?
The floor is the hard ceiling on what the skill does whatever verbs you ratify: no deletions, no voice or copy changes on live surfaces, no outward broadcasts, no direct push to main, no self-modification. The floor is drawn by action type, not location. A ratified climb, an accepted candidate and a forward rule can never breach it. The safety guard is in the floor, not in the verb moves.
How is this different from just asking my AI to clean things up?
An ad-hoc cleanup request has no memory, no eligibility tracking, no verbs and no decision board. It does the work once and forgets it happened. Autonomous Improvement Session carries state across runs in the log frontmatter, tracks what ran and when, grows a menu with each cycle and escalates execution authority only through ratified decisions. The difference is a flywheel versus a one-shot.
Related
Skill
Session Closeout
A fast three-action close for a git-tracked workspace. Breadcrumbs as you work, a refreshed primer, a readable commit as the session summary and a paste-ready prompt when the work continues.
Skill
Pattern Harvest
Reflective session-level pattern extraction. Three parallel lenses produce a numbered recommendation list the operator selects from.
Skill
Self-Healing
Autonomous error recovery during implementation sessions. Diagnose the root cause, apply a fix, continue without stalling on recoverable mistakes.
Free · Your AI’s Charter
Before you install a skill, give your AI a charter. Your AI’s Charter is a free CLAUDE.md for how Claude works with you: what it runs on its own, what it asks you first and how it acts in your name.
Get the Charter · freeAutonomous Improvement Session pairs naturally with Session Closeout: run improvement when you have capacity to spare, then run closeout to seal the session. Pattern Harvest works the same flywheel from the reflective side. All three ship inside the Sovereign Ecosystem Foundation. System 8 of The Alive Business, The Business That Improves Itself, gives the improving a weekly rhythm: one half-hour where the business reports to its owner and one rule change comes out.
See The Alive Business