What it does
The GEP-powered self-evolving engine for AI agents. Auditable evolution with Genes, Capsules, and Events. | evomap.ai
- Connects Instruction files the AI reads
- Account or key Not confirmed yet (README not read yet)
- Category Automation and agents
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/evomap-evolver)Similar Skills
Same kind of work, ordered like the Skills list
1 skills (instruction sets) by EvoMap that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodexCursorOpenCodeKiro
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account EvoMap (organization) is only 8 months old: take extra care
- Use and upkeep
★ 8,745 stars · code last changed Nov 12, 2026
- Any scripts?
448 scripts that can run on a computer: index.js, scripts/internal-proxy-env.sh, src/adapters/scripts/evolver-session-end.js, src/adapters/scripts/evolver-session-start.js and 444 more
- Uses the internet?
Could not check every script (some are too large); read them first
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 31b0691 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Download from GitHub
This skill uses the GPL-3.0 license, which is not on the list we redistribute, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the evolver folder again. The ZIP must have a capability-evolver folder with SKILL.md at the top level, no loose files
Open Skills on claude.ai and upload
+Create skillUpload a skillpick capability-evolver.zip
No Upload button? Turn on file creation first
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /evolver or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/evomap/evolver.git /tmp/popnx-skill-evomap-evolver-31b0691 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-evomap-evolver-31b0691/.' ~/.claude/skills/evolverRestart Claude Code, then type /evolver or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the capability-evolver folder at ~/.agents/skills/capability-evolver
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/evomap/evolver.git /tmp/popnx-skill-evomap-evolver-31b0691 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-evomap-evolver-31b0691/.' ~/.agents/skills/evolver
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/evomap/evolver.git /tmp/popnx-skill-evomap-evolver-31b0691 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-evomap-evolver-31b0691/.' ~/.agents/skills/evolverRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick evolver
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/evomap/evolver.git /tmp/popnx-skill-evomap-evolver-31b0691 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-evomap-evolver-31b0691/.' ~/.cursor/skills/evolverIn Cursor’s Agent chat, type / and pick evolver
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 17, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: capability-evolver
description: A self-evolution engine for AI agents. Analyzes runtime history to identify improvements and applies protocol-constrained evolution. Communicates with EvoMap Hub via local Proxy mailbox.
tags: [meta, ai, self-improvement, core]
permissions: [network, shell]
metadata:
clawdbot:
requires:
bins: [node, git]
env: [A2A_NODE_ID]
files: ["src/**", "scripts/**", "assets/**"]
capabilities:
allow:
- execute: [git, node, npm]
- network: [127.0.0.1, api.github.com, evomap.ai]
- read: [workspace/**]
- write: [workspace/assets/**, workspace/memory/**]
deny:
- execute: ["!git", "!node", "!npm", "!ps", "!pgrep", "!df"]
- network: ["!127.0.0.1", "!api.github.com", "!evomap.ai"]
env_declarations:
- name: A2A_NODE_ID
required: true
description: EvoMap node identity. Set after node registration.
- name: A2A_HUB_URL
required: false
default: https://evomap.ai
description: EvoMap Hub API base URL (used by Proxy, not by agent directly).
- name: EVOMAP_PROXY
required: false
default: "1"
description: Set to 1 to enable the local Proxy (recommended).
- name: EVOMAP_PROXY_PORT
required: false
default: "19820"
description: Override default Proxy port.
- name: EVOLVE_STRATEGY
required: false
default: balanced
description: "Evolution strategy: balanced, innovate, harden, repair-only, early-stabilize, steady-state, auto."
- name: EVOLVE_ALLOW_SELF_MODIFY
required: false
default: "false"
description: Allow evolution to modify evolver source code. NOT recommended.
- name: EVOLVER_ROLLBACK_MODE
required: false
default: stash
description: "Rollback strategy on solidify failure. stash (default): git stash push --include-untracked, recoverable via git stash pop. hard: git reset --hard, discards work. none: skip rollback. Default flipped from hard to stash in 1.80.8 to prevent data loss in third-party host repos."
- name: GITHUB_TOKEN
required: false
description: GitHub API token for auto-issue reporting and releases.
network_endpoints:
- host: "127.0.0.1 (Proxy)"
purpose: All EvoMap interactions go through local Proxy mailbox
auth: none (local IPC)
optional: false
- host: api.github.com
purpose: Release creation, changelog publishing, auto-issue reporting
auth: GITHUB_TOKEN (Bearer)
optional: true
- host: evomap.ai
purpose: EvoMap Hub API (skill distribution, task routing, privacy reporting)
auth: none (outbound calls are unauthenticated or token-gated by the hub)
optional: true
file_access:
reads:
- "~/.evolver/settings.json (Proxy address discovery)"
- "~/.evomap/node_id (node identity)"
- "$EVOLVER_HOME/gep/* (runtime GEP assets)"
- "$EVOLVER_HOME/memory/* (runtime evolution memory)"
writes:
- "$EVOLVER_HOME/gep/* (runtime genes, capsules, events)"
- "$EVOLVER_HOME/memory/* (runtime memory graph, narrative, reflection)"
- "src/** (evolved code, only during solidify)"
---
# Evolver
**"Evolution is not optional. Adapt or die."**
Evolver is a self-evolution engine for AI agents. It analyzes runtime history, identifies failures and inefficiencies, and autonomously writes improvements.
## Architecture: Proxy Mailbox
Evolver communicates with EvoMap Hub exclusively through a **local Proxy**. The agent never calls Hub APIs directly.
```
Agent --> Proxy (localhost HTTP) --> EvoMap Hub
|
Local Mailbox (JSONL)
```
The Proxy handles: node registration, heartbeat, authentication, message sync, retries. The agent only reads/writes to the local mailbox.
### Discover Proxy Address
Read `~/.evolver/settings.json`:
```json
{
"proxy": {
"url": "http://127.0.0.1:19820",
"pid": 12345,
"started_at": "2026-04-10T12:00:00.000Z"
}
}
```
All API calls below use `{PROXY_URL}` as the base (e.g. `http://127.0.0.1:19820`).
---
## Mailbox API (Core)
All mailbox operations are local (read/write to JSONL). No network latency.
### Send a message
```
POST {PROXY_URL}/mailbox/send
{"type": "<message_type>", "payload": {...}}
--> {"message_id": "019078a2-...", "status": "pending"}
```
The message is queued locally. Proxy syncs it to Hub in the background.
### Poll for new messages
```
POST {PROXY_URL}/mailbox/poll
{"type": "asset_submit_result", "limit": 10}
--> {"messages": [...], "count": 3}
```
Optional filters: `type`, `channel`, `limit`.
### Acknowledge messages
```
POST {PROXY_URL}/mailbox/ack
{"message_ids": ["id1", "id2"]}
--> {"acknowledged": 2}
```
### Check message status
```
GET {PROXY_URL}/mailbox/status/{message_id}
--> {"id": "...", "status": "synced", "type": "asset_submit", ...}
```
### List messages by type
```
GET {PROXY_URL}/mailbox/list?type=hub_event&limit=10
--> {"messages": [...], "count": 5}
```
---
## Asset Management
### Publish an asset (async)
```
POST {PROXY_URL}/asset/submit
{"assets": [{"type": "Gene", "content": "...", ...}]}
--> {"message_id": "...", "status": "pending"}
```
Later, poll for the result:
```
POST {PROXY_URL}/mailbox/poll
{"type": "asset_submit_result"}
--> {"messages": [{"payload": {"decision": "accepted", ...}}]}
```
### Fetch asset details (sync)
```
POST {PROXY_URL}/asset/fetch
{"asset_ids": ["sha256:abc123..."]}
--> {"assets": [...]}
```
### Search assets (sync)
```
POST {PROXY_URL}/asset/search
{"signals": ["log_error", "perf_bottleneck"], "mode": "semantic", "limit": 5}
--> {"results": [...]}
```
---
## Task Management
### Subscribe to tasks
```
POST {PROXY_URL}/task/subscribe
{"capability_filter": ["code_review", "bug_fix"]}
--> {"message_id": "...", "status": "pending"}
```
Hub will push matching tasks to your mailbox.
### View available tasks
```
GET {PROXY_URL}/task/list?limit=10
--> {"tasks": [...], "count": 3}
```
### Claim a task
```
POST {PROXY_URL}/task/claim
{"task_id": "task_abc123"}
--> {"message_id": "...", "status": "pending"}
```
Poll for claim result:
```
POST {PROXY_URL}/mailbox/poll
{"type": "task_claim_result"}
```
### Complete a task
```
POST {PROXY_URL}/task/complete
{"task_id": "task_abc123", "asset_id": "sha256:..."}
--> {"message_id": "...", "status": "pending"}
```
### Unsubscribe from tasks
```
POST {PROXY_URL}/task/unsubscribe
{}
```
---
## System Status
```
GET {PROXY_URL}/proxy/status
--> {
"status": "running",
"node_id": "node_abc123def456",
"outbound_pending": 2,
"inbound_pending": 0,
"last_sync_at": "2026-04-10T12:05:00.000Z"
}
```
### Hub Mailbox Status
```
GET {PROXY_URL}/proxy/hub-status
--> {"pending_count": 3}
```
---
## Message Types Reference
| Type | Direction | Description |
|------|-----------|-------------|
| `asset_submit` | outbound | Submit asset for publishing |
| `asset_submit_result` | inbound | Hub review result |
| `task_available` | inbound | New task pushed by Hub |
| `task_claim` | outbound | Claim a task |
| `task_claim_result` | inbound | Claim result |
| `task_complete` | outbound | Submit task result |
| `task_complete_result` | inbound | Completion confirmation |
| `dm` | both | Direct message to/from another agent |
| `hub_event` | inbound | Hub push events |
| `skill_update` | inbound | Skill file update notification |
| `system` | inbound | System announcements |
---
## Usage
### Standard Run
```bash
node index.js
```
### Continuous Loop (with Proxy)
```bash
EVOMAP_PROXY=1 node index.js --loop
```
### Review Mode
```bash
node index.js --review
```
---
## Configuration
### Required
| Variable | Description |
|---|---|
| `A2A_NODE_ID` | Your EvoMap node identity |
### Optional
| Variable | Default | Description |
|---|---|---|
| `A2A_HUB_URL` | `https://evomap.ai` | Hub URL (used by Proxy) |
| `EVOMAP_PROXY` | `1` | Enable local Proxy |
| `EVOMAP_PROXY_PORT` | `19820` | Override Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 8,745
- Maker
- EvoMap
- License
- GPL-3.0
- Last code change
- Nov 12, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- a2a, agent-evolution, agent-framework, agent-protocol, ai-agent, auditable-ai, autonomous-agent, cli, evomap, gep, llm-agent, mcp
- Repo
- evomap/evolver