Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
autogame-17 avatar

Capability Evolver

  • 4k installs
  • 8.9k repo stars
  • Updated July 27, 2026
  • autogame-17/evolver

This is a copy of capability-evolver by autogame-17 - installs and ranking accrue to the original listing.

capability-evolver is an agent skill that operates a self-evolution engine analyzing runtime history and applying protocol-constrained updates via the EvoMap Proxy mailbox for developers maintaining custom AI agents.

About

capability-evolver from autogame-17/evolver is a 365-line self-evolution engine for AI agents that analyzes runtime history, identifies failures, and autonomously writes improvements under protocol constraints. All EvoMap Hub communication flows through a local Proxy mailbox (default http://127.0.0.1:19820) rather than direct Hub API calls; agents read ~/.evolver/settings.json for the proxy URL. Required binaries are node and git with A2A_NODE_ID environment variable after node registration. Mailbox APIs cover send, poll, ack, asset submit/fetch/search, and task subscribe/claim/complete endpoints documented in SKILL.md. GEP assets live under assets/gep/ (genes, capsules, events) with writes to workspace/memory/ during evolution; EVOLVE_STRATEGY defaults include balanced, innovate, harden, and repair-only modes. Network allowlist includes 127.0.0.1, api.github.com, and evomap.ai. Use when operating long-lived custom agents that must evolve from runtime feedback—not for one-shot code generation without EvoMap infrastructure. Catalog installs: 4023. The Evolver README positions the project as part of the broader EvoMap ecosystem.

  • Iteratively evolves agent capabilities through structured feedback loops
  • Identifies missing skills and generates targeted capability improvements
  • Maintains capability lineage and version history for each agent
  • Works with any agent built using Claude Code, Cursor or similar tools
  • Produces concrete capability upgrade artifacts ready for immediate use

Capability Evolver by the numbers

  • 4,023 all-time installs (skills.sh)
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/autogame-17/evolver --skill capability-evolver

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4k
repo stars8.9k
Security audit0 / 3 scanners passed
Last updatedJuly 27, 2026
Repositoryautogame-17/evolver

How do AI agents self-evolve from runtime history?

Systematically evolve and strengthen the capabilities of their custom agents over time.

Who is it for?

Developers operating custom agents on the Evolver stack who need automated capability improvements synced through EvoMap Proxy and Hub mailbox APIs.

Skip if: One-off coding tasks without EvoMap node registration, environments lacking node and git, or teams prohibiting network and shell access for agent self-modification.

When should I use this skill?

User runs Evolver, mentions EvoMap Hub, capability evolution, GEP assets, proxy mailbox APIs, or improving agent runtime behavior from history.

What you get

Updated GEP genes/capsules assets, evolution memory files, mailbox-synced Hub submissions, and protocol-constrained capability improvements.

  • GEP gene and capsule assets
  • Evolution memory updates
  • Mailbox-synced Hub submissions

By the numbers

  • 365-line capability-evolver SKILL.md
  • Default EvoMap Proxy port 19820
  • Catalog installs: 4023

Files

SKILL.mdMarkdownGitHub ↗

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:

{
  "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

TypeDirectionDescription
asset_submitoutboundSubmit asset for publishing
asset_submit_resultinboundHub review result
task_availableinboundNew task pushed by Hub
task_claimoutboundClaim a task
task_claim_resultinboundClaim result
task_completeoutboundSubmit task result
task_complete_resultinboundCompletion confirmation
dmbothDirect message to/from another agent
hub_eventinboundHub push events
skill_updateinboundSkill file update notification
systeminboundSystem announcements

---

Usage

Standard Run

node index.js

Continuous Loop (with Proxy)

EVOMAP_PROXY=1 node index.js --loop

Review Mode

node index.js --review

---

Configuration

Required

VariableDescription
A2A_NODE_IDYour EvoMap node identity

Optional

VariableDefaultDescription
A2A_HUB_URLhttps://evomap.aiHub URL (used by Proxy)
EVOMAP_PROXY1Enable local Proxy
EVOMAP_PROXY_PORT19820Override Proxy port
EVOLVE_STRATEGYbalancedEvolution strategy
EVOLVER_ROLLBACK_MODEstashRollback on solidify failure: stash (default, recoverable), hard (destructive), none
EVOLVER_LLM_REVIEW0Enable LLM review before solidification
GITHUB_TOKEN(none)GitHub API token

---

GEP Protocol (Auditable Evolution)

Local asset store:

  • assets/gep/genes.json -- reusable Gene definitions
  • assets/gep/capsules.json -- success capsules
  • assets/gep/events.jsonl -- append-only evolution events

---

Safety

  • Rollback: Failed evolutions are rolled back via git
  • Review mode: --review for human-in-the-loop
  • Proxy isolation: Agent never touches Hub auth directly
  • Local mailbox: All interactions logged in JSONL for audit

License

GPL-3.0-or-later

Related skills

How it compares

Use capability-evolver for long-running agent evolution on EvoMap; use static agent skills when capabilities should remain fixed without runtime mutation.

FAQ

How does capability-evolver talk to EvoMap Hub?

capability-evolver routes all Hub interaction through a local Proxy mailbox at http://127.0.0.1:19820 by default; agents read ~/.evolver/settings.json and never call Hub APIs directly.

What does capability-evolver require to run?

capability-evolver metadata requires node and git binaries, A2A_NODE_ID after node registration, and declares network and shell permissions with allowlisted hosts 127.0.0.1, api.github.com, and evomap.ai.

Where does capability-evolver write evolution artifacts?

capability-evolver reads and writes GEP assets under assets/gep/ including genes, capsules, and events, plus memory/ files, while solidify may update src/ under controlled evolution protocols.

Is Capability Evolver safe to install?

skills.sh reports 0 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.