How everything-claude-code hit 145k stars by treating skills, memory, and instincts as a single tunable system — and what you can steal from it today.
Most people think of agent skills as individual files you drop into a folder. The fastest-growing repo in the agent tooling space thinks of them as components in a performance-tunable system. Today we look at what that means for how you structure your own agent setup.
The shift from skill files to skill systems
A year ago, the agent skill conversation was about individual files. You had a SKILL.md that taught your agent to run tests, another that handled deployments, maybe a SOUL.md that gave it a personality. Each file was useful on its own. The mental model was a toolbox — reach in, grab what you need.
That mental model is breaking. The repo everything-claude-code — currently sitting at 145,000 stars — doesn't organize skills as a flat collection. It treats skills, instincts, memory, and security as layers in a single stack. The README doesn't say 'here are some skills.' It says 'here is an agent harness performance optimization system.'
That framing matters. When you think of your agent setup as a system with tunable layers, you stop asking 'which skill should I add?' and start asking 'where is my bottleneck?'
What the harness pattern actually looks like
The pattern that everything-claude-code popularized — and that repos like OpenViking and CowAgent have adopted in their own ways — separates agent configuration into four distinct layers.
First, identity: your SOUL.md and CLAUDE.md files. These set the baseline behavior the agent defaults to when no skill is active. Second, skills: your SKILL.md files, which are conditional — they activate when a trigger matches. Third, memory: persistent context that survives across sessions. Fourth, instincts: lightweight behavioral nudges that sit between identity and skills, shaping how the agent approaches any task without being full skill definitions.
The insight is that these layers interact. A skill that works perfectly with one SOUL.md configuration might behave differently with another. Memory from a previous session might make a skill unnecessary — or critical. When you tune these layers together instead of independently, you get compounding improvements.
AGENTS.md — Minimal harness orchestration layer
# Agent Harness Config
## Identity
- SOUL.md defines baseline voice, role, and constraints
- All skills inherit from SOUL.md unless they explicitly override
## Skill Registry
| Skill | Trigger | Layer |
|-------|---------|-------|
| /commit | User invokes `/commit` or asks to commit | workflow |
| /review-pr | User invokes `/review-pr` or PR number referenced | workflow |
| /deploy | User says "deploy" or "ship it" | workflow |
| /test | User says "run tests" or test file modified | reactive |
| /daily-report | HEARTBEAT.md cron fires at 07:00 | scheduled |
## Memory Policy
- Session memory: conversation-scoped, discarded on exit
- Project memory: saved to `memory/`, survives across sessions
- Feedback memory: user corrections, highest priority recall
## Instincts
- Before any file write: check for existing file, prefer Edit over Write
- Before any git push: confirm with user
- After any error: read the error before retrying
- On ambiguous request: ask one clarifying question, not three
## Skill Composition Rules
- Max 2 skills active simultaneously
- /deploy requires /test to pass first (dependency)
- /commit suppresses /review-pr (mutual exclusion)
- Scheduled skills yield to user-invoked skillsA minimal harness config you can use today
You don't need to adopt an entire framework to use this pattern. Here's a stripped-down version of the layered approach that works in any Claude Code or OpenClaw project right now. The key is the AGENTS.md file acting as the orchestration layer — it tells the agent which skills exist, when to use them, and how they relate to each other.
Drop this into your project root and modify the skill references to match your actual workflow. The important part isn't the specific skills listed — it's the structure that makes the agent aware of the full system instead of treating each skill as an island.
Why the ecosystem is converging on this
Look at the numbers. VoltAgent's awesome-openclaw-skills has catalogued over 5,400 skills. Antigravity's collection has 1,370+. When you have that many skills available, the problem stops being 'I need a skill for X' and becomes 'how do I compose skills without them conflicting?'
OpenViking from ByteDance's Volcengine team attacks this from the infrastructure side — it's a context database that unifies memory, resources, and skills through a file system paradigm. Their bet is that hierarchical context delivery is the missing piece. Instead of loading every skill into the agent's context window, you organize them in a tree and deliver only what's relevant for the current task.
This is the same instinct that drove everything-claude-code to 145k stars. The agent doesn't need all your skills all the time. It needs the right skills at the right time, informed by the right memory, filtered through the right identity layer.
The practical takeaway
If your agent setup is a flat folder of SKILL.md files, you're leaving performance on the table. Start by adding an AGENTS.md that maps which skills apply to which contexts. Add a HEARTBEAT.md if your agent runs on a schedule and needs to know what changed since last session. Make your SOUL.md specific enough that skills can assume a baseline behavior instead of re-establishing it every time.
You're not building a skill collection. You're tuning a system.
The repos that are winning the star race aren't the ones with the most skills — they're the ones that figured out how skills, memory, identity, and instincts compose into something greater than the sum of their parts. Start with the AGENTS.md above, tune it to your workflow, and watch what happens when your agent stops treating skills as isolated tools and starts treating them as a system. The Daily Skill — Teaching AI new tricks, one skill file at a time.