Skip to content

Latest commit

 

History

History
167 lines (114 loc) · 4.32 KB

customization.md

File metadata and controls

167 lines (114 loc) · 4.32 KB

Customization Guide

AEP is designed to be adapted to your specific needs. Here's what you can customize and how.

Scan Sources

Adding Sources

In your SOUL.md evolution protocol section, add or modify the scan sources list:

### Scan Sources
1. Reddit r/YourSubreddit — upvote > 20
2. GitHub your-org/your-repo discussions
3. Discord #your-channel — keyword matching
4. Your internal wiki / knowledge base

Removing Sources

Simply remove the source from the list. The agent will only scan sources explicitly listed.

Domain-Specific Sources

Domain Suggested Sources
Web Development Reddit r/webdev, r/nextjs; Dev.to; CSS-Tricks
DevOps Reddit r/devops; GitHub Actions marketplace; CNCF blog
Data Science Reddit r/MachineLearning; Kaggle discussions; Papers with Code
Product Management Reddit r/ProductManagement; Lenny's Newsletter; ProductHunt

Keywords

Customizing the 7-Day Rotation

Replace the default keywords with your domain-specific terms:

### Keyword Rotation
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|-----|-----|-----|-----|-----|-----|-----|
| react performance | nextjs deployment | css architecture | testing patterns | api design | dx tooling | side projects |

Adding Extra Keywords

Add broad discovery keywords:

### Extra Discovery Keywords
- "developer productivity 2026"
- "frontend architecture tips"
- "your-tool-name tutorial OR guide"

Scoring Weights

Adjusting Point Values

Override specific scoring rules:

### Custom Scoring
+5  Has a working GitHub repo (instead of +3 for code examples)
+3  Author is a recognized expert in the field
-1  Only available in English (our team works in Chinese)
-10 Any security concern (zero tolerance)

Changing Thresholds

### Custom Thresholds
- Write to DB: >= 7 (stricter than default 5)
- Verified: cumulative >= 10 (stricter than default 8)
- Eliminated: cumulative <= -5 (stricter than default -3)

Storage Backend

Local JSON (Default)

Zero setup. Candidates stored in workspace/evolution-candidates.json.

Feishu Bitable

See examples/feishu-setup.md.

Requires:

  • Feishu app with bitable permissions
  • exec tool enabled in your agent

Notion Database

Create a Notion database with columns matching templates/table-schema.md, then configure your agent to use the Notion API via exec + curl.

Airtable

Similar to Notion — create a base matching the schema, configure API access.

Custom Backend

AEP's schema is simple enough to adapt to any storage. Key requirements:

  • Can store 19 fields per record (see templates/table-schema.md)
  • Supports CRUD operations
  • Accessible from your agent (via API or local file)

Agent Team

Defining Your Agents

Replace the default agent roster in the evolution protocol:

## Your Agent Team

- **Research Bot**: Handles deep research tasks, Model: GPT-4
- **Writing Assistant**: Content creation, Model: Claude Sonnet
- **Code Helper**: Programming tasks, Model: Codestral

Multi-Agent Skill Sharing

When a skill is verified, the proposal can suggest sharing it with specific agents:

Suggested action:
  [ ] Write to Research Bot SOUL.md (full skill)
  [ ] Share with Writing Assistant (adapted version)
  [ ] Not applicable to Code Helper

Trigger Words

Changing Activation Phrases

### Triggers
- Evolution scan: "scan for new skills" or "进化扫描"
- Evolution report: "evolution status" or "进化状态"
- Manual score: "rate skill #EVO-xxx as X"

Report Format

Customizing the Daily Report

Modify the report template to include/exclude sections:

### Report Format
===== Evolution Report {date} =====
Scanned: {source_count} sources, {article_count} articles
New: {new_count} | Trialing: {trial_count} | Pending: {pending_count}

{new_discoveries_section}
{trial_progress_section}
=====================================

Language

AEP supports any language. The default templates include both English and Chinese trigger words. To use another language:

  1. Translate the trigger phrases in your SOUL.md
  2. Translate the report format template
  3. Keep the field names in the candidate DB consistent (English recommended for interoperability)