Level Up
Use when someone asks to level up their AIOS, close an audit gap, find what to automate...
Install
npx skills add nateherkai/AIS-OS --skill level-up -g -a claude-code -y- Repository
- nateherkai/AIS-OS1.8k
- Category
- Engineering
- Updated
- 2mo ago
- License
- See repository
- Context cost
- Mediumabout 2,598 tokens
- Runs scripts
- No, instructions only
What it does
Use when someone asks to level up their AIOS, close an audit gap, find what to automate next, or improve one workflow. Walks the 3Ms from choosing the constraint to shipping one useful artifact or verified repair.
Adapted from The Three Ms of AI™. © 2026 Nate Herk. All rights reserved. The Three Ms of AI™ is a trademark of Nate Herk.
What this skill does
Walks the user through the 3Ms each week to surface and ship one new automation. One interview = one artifact. It also installs the 3Ms framework into the user's head over time, after 4-6 runs, the user starts spotting opportunities mid-week without prompting because the questions have become internal defaults.
This is the brain-rewire mechanism. The kit doesn't need cron jobs to anchor behavior; it needs /level-up running every Friday.
What /level-up is NOT
- Not
/audit./auditis structural ("is the AIOS built right?")./level-upis functional ("what business leverage am I missing?"). Run/auditfirst if structure is messy. - Not a multi-candidate planner. One run = one shipped artifact.
- Not a coach. The user does the thinking. The skill conducts the interview.
When /level-up runs
- First run: Day 14. After the user has connected ≥1 MCP/script and run
/auditonce. Earlier yields trivial output. - Cadence: weekly, Friday afternoon. Review the week, surface one automation, ship Monday.
- On-demand any time. Mid-week if a manual task itches.
Inputs the skill reads
First read the applicable operating manual. The paths below are starter-kit defaults: resolve priorities, identity, and connections through the current project's declared routes when it uses different locations. Do not create duplicate context files because these defaults are absent. Use references/3ms-framework.md if present; otherwise read the bundled 3Ms framework. Ask only for information unavailable in the existing sources.
