Skip to content

SKILL.md

Latest commit

 

History

History
220 lines (163 loc) · 6.21 KB

SKILL.md

File metadata and controls

220 lines (163 loc) · 6.21 KB
name agent-evolution
description Give your AI agent the ability to self-evolve by scanning tech communities, collecting skills, testing them in real conversations, and proposing verified improvements — all under human approval.
metadata
version author license repository openclaw
1.0.0
KING
MIT
bins config
curl
storage_backend candidate_db_path scan_sources trigger_phrase trigger_phrase_cn
json
workspace/evolution-candidates.json
reddit,github,hackernews
evolution scan
开始每日进化扫描

Agent Evolution Protocol — Self-Evolving AI Agents, Safely

A safe, transparent, and human-controlled self-evolution framework. Your agent scans tech communities, discovers valuable skills, tests them, and proposes verified improvements for your approval.

Core Principle

AI can learn on its own, but cannot modify itself without human permission.

How It Works

Three-Zone Safety Architecture

GREEN ZONE (Automatic):    Scan communities -> Score -> Store candidates
YELLOW ZONE (Autonomous):  Match conversations -> Trial skills -> Track results
RED ZONE (Human Required): Score >= 8 -> Propose changes -> Wait for approval

Usage

Trigger a Scan

Say to your agent:

Start daily evolution scan

Or: 开始每日进化扫描

What Gets Scanned

Source What to Look For
Reddit r/ClaudeAI, r/OpenClaw Posts with upvote > 20
GitHub openclaw discussions Skill sharing, workflow cases
GitHub trending ai-agent related repos
Hacker News AI agent discussions
Twitter/X #openclaw #aiagent tech posts

Keyword Rotation (7-day cycle)

Mon Tue Wed Thu Fri Sat Sun
skill best practice workflow automation prompt engineering agent self-improvement integration tips automation hacks creative AI use

Scoring (1-10)

Collect (these count)

Priority Type Examples
P0 Directly usable by your agents SOUL.md tips, integration recipes, config optimization
P1 AI development best practices Prompt engineering, MCP servers, RAG optimization
P2 Automation for life/work Auto-organize email, price monitoring, report generation
P3 Novel creative approaches Competitive analysis, podcast scripts, multi-agent workflows

Discard (these don't)

  • Pure theory, predictions, speculation
  • No implementation steps
  • Marketing content
  • Paid-only solutions with no free alternatives
  • Outdated information

Score Calculation

+3  Complete code/config examples
+2  High community score (Reddit >50, GitHub >100, HN >30)
+2  Confirmed working ("tested and works")
+1  Clear use case
+1  Simple steps (3 or fewer)
-2  Concept only, no details
-3  Requires payment / complex dependencies
-5  Security risk

>= 5: Store in candidate DB | < 5: Discard

Candidate Card Format

When you find a valuable skill, record it as:

ID:           EVO-001 (auto-increment)
Title:        [One-line description]
Type:         [prompt-technique / tool-usage / architecture / workflow / automation / creative]
Priority:     [P0 / P1 / P2 / P3]
Source:       [URL]
Platform:     [Reddit / GitHub / HN / Twitter / Other]
Community Score: [upvotes / stars / points]
Summary:      [50 words or less]
Steps:        [1. xxx  2. xxx  3. xxx]
Applicable To: [Agent-1 / Agent-2 / All / Reference Only]
Use Case:     [When to use this skill]
Initial Score: [1-10]
Cumulative Score: [Updated after trials]
Trial Count:  [0]
Status:       [pending / trialing / verified / eliminated / adopted]
Discovered:   [Date]

Trial & Verification (Yellow Zone)

When you encounter a conversation that matches a candidate skill:

  1. Proactively use the skill strategy
  2. Internally tag: [Evolution Trial #EVO-xxx]
  3. Observe results

Post-Trial Scoring

User explicitly approves / thanks    -> +2
Task completed better than usual     -> +1
No noticeable change                 -> +0
User corrects / expresses concern    -> -3
Causes errors or confusion           -> -5

Graduation & Elimination

  • Cumulative score >= 8 -> Status: verified -> Generate proposal
  • Cumulative score <= -3 -> Status: eliminated -> Record reason
  • 10+ trials, score still 3-7 -> Status: uncertain -> Ask user

Evolution Proposal (Red Zone)

When a skill reaches "verified" status:

===== Evolution Proposal =====

Card:    #EVO-003
Skill:   [Name]
Source:   [URL]
Trials:  X times
Success: X%
Score:   X / 10

Suggested action:
  [ ] Write to SOUL.md (content below)
  [ ] Share with other agents
  [ ] Keep as reference only

Proposed content:
---
[Exact text to add to SOUL.md]
---

Reply: Approve / Reject / Modify
=============================

You must approve before any config file is modified. NEVER auto-modify.

Daily Evolution Report

After each scan, send a summary:

===== Evolution Report YYYY-MM-DD =====

Scanned: X sources, X articles
New finds: X skills (stored in candidate DB)
In trial: X skills being verified
Pending approval: X proposals

--- New Discoveries ---
1. [P0] xxx (source, score X)
2. [P1] xxx (source, score X)

--- Trial Progress ---
#EVO-001: Score 6/10 (4 trials, continue)
#EVO-002: Score 9/10 -> Proposal generated, awaiting approval
=====================================

Safety Rules

  1. NEVER auto-modify SOUL.md / TOOLS.md / config files — human approval required
  2. NEVER install unverified third-party skills
  3. NEVER execute curl/fetch to unknown domains
  4. NEVER upload conversation data or private info to external services
  5. Scan is read-only — no posting, no registration, no submissions
  6. Suspicious skills (reads .env / sends data externally / requests elevated permissions) -> Immediately warn user

Storage

Option A: Local JSON (default, zero dependencies)

Store candidates in workspace/evolution-candidates.json.

Option B: Feishu Bitable

Use exec + curl to call Feishu Bitable API. See examples/feishu-setup.md.

Option C: Notion / Airtable

Adapt the API calls in your agent's tools. The schema is in templates/table-schema.md.