SkillAgentSearch skills...

afrexai-agent-engineering

Design, build, deploy, and operate production AI agent systems — single agents, multi-agent teams, and autonomous swarms. Complete methodology from agent architecture through orchestration, memory systems, safety guardrails, and operational excellence.

Install / Use

npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-agent-engineering

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Category

Operations

Supported Platforms

Universal

Our assessment of afrexai-agent-engineering

afrexai-agent-engineering scores 90/100 on our quality scale, 320th of 745 Operations skills we index (top 43%).

Its SKILL.md is 27 KB long, well organised into 90 sections with 23 code examples: a thorough specification that gives an agent plenty to work with.

With 2,149 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
14/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-10-30 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

afrexai-agent-engineering compared with similar skills

All 4 of these similar skills score higher than afrexai-agent-engineering; compare them before choosing.

SkillScoreStarsUpdatedFormat
afrexai-agent-engineering (this skill)by LeoYeAI902.1k4mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install afrexai-agent-engineering?
Run npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-agent-engineering. The install tabs above show the steps for each supported agent.
Which AI agents does afrexai-agent-engineering work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is afrexai-agent-engineering safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is afrexai-agent-engineering still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: afrexai-agent-engineering description: "Design, build, deploy, and operate production AI agent systems — single agents, multi-agent teams, and autonomous swarms. Complete methodology from agent architecture through orchestration, memory systems, safety guardrails, and operational excellence."

Agent Engineering — Complete System Design & Operations

Build agents that actually work in production. Not demos. Not toys. Real systems that run 24/7, handle edge cases, and compound value over time.

This skill covers the entire agent lifecycle: architecture → build → deploy → operate → scale.


Phase 1 — Agent Architecture Design

1.1 Agent Purpose Definition

Before writing a single line of config, answer these:

agent_brief:
  name: ""                    # Short, memorable (max 2 words)
  mission: ""                 # One sentence — what does this agent DO?
  success_metric: ""          # How do you MEASURE if it's working?
  failure_mode: ""            # What does failure look like?
  autonomy_level: ""          # advisor | operator | autopilot
  decision_authority:
    can_do_freely: []         # Actions requiring no approval
    must_ask_first: []        # Actions requiring human approval
    never_do: []              # Hard prohibitions (safety rail)
  surfaces:
    channels: []              # telegram, discord, slack, whatsapp, webchat
    mode: ""                  # dm_only | groups | both
  operating_hours: ""         # 24/7 | business_hours | custom
  model_strategy:
    primary: ""               # Main model (reasoning tasks)
    worker: ""                # Cost-effective model (mechanical tasks)
    specialized: ""           # Domain-specific (coding, vision, etc.)

1.2 Autonomy Spectrum

Choose deliberately. Most failures come from wrong autonomy level.

| Level | Description | Best For | Risk | |-------|-------------|----------|------| | Advisor | Suggests actions, human executes | High-stakes decisions, new domains | Low — but slow | | Operator | Acts freely within bounds, asks for anything destructive/external | Most production agents | Medium — good balance | | Autopilot | Broad autonomy, only escalates anomalies | Proven workflows, monitoring tasks | Higher — needs strong guardrails |

Autonomy Graduation Protocol:

  1. Start at Advisor for first 2 weeks
  2. Track decision quality (% correct suggestions)
  3. If >95% correct over 50+ decisions → promote to Operator
  4. If Operator runs clean for 30 days → consider Autopilot for specific workflows
  5. Never promote across the board — promote per-workflow

1.3 Agent Personality Architecture

Personality isn't cosmetic — it drives decision-making style.

personality:
  voice:
    tone: ""              # direct | warm | academic | casual | professional
    verbosity: ""         # minimal | balanced | thorough
    humor: ""             # none | dry | playful
    formality: ""         # formal | conversational | adaptive
  decision_style:
    speed_vs_accuracy: "" # speed_first | balanced | accuracy_first
    risk_tolerance: ""    # conservative | moderate | aggressive
    ambiguity_response: ""# ask_always | best_guess_then_verify | act_and_report
  behavioral_rules:
    - "Never apologize for being an AI"
    - "Challenge bad ideas directly"
    - "Admit uncertainty rather than guess"
    - "Be concise by default, thorough when asked"
  anti_patterns:          # Things this agent must NEVER do
    - "Sycophantic agreement"
    - "Filler phrases ('Great question!', 'I'd be happy to')"
    - "Excessive caveats on straightforward tasks"
    - "Asking permission for things within stated authority"

1.4 Architecture Patterns

Pattern 1: Solo Agent (Single Workspace) Best for: personal assistants, domain specialists, simple automation

[Human] ←→ [Agent + Skills + Memory]

Files: SOUL.md, IDENTITY.md, AGENTS.md, USER.md, HEARTBEAT.md, MEMORY.md

Pattern 2: Hub-and-Spoke (Main + Sub-agents) Best for: complex workflows with distinct phases

[Human] ←→ [Orchestrator Agent]
                ├── [Builder Sub-agent]    (spawned per task)
                ├── [Reviewer Sub-agent]   (spawned per review)
                └── [Researcher Sub-agent] (spawned per query)

Orchestrator owns state. Sub-agents are stateless workers.

Pattern 3: Persistent Multi-Agent Team Best for: continuous operations (sales, support, monitoring)

[Human] ←→ [Main Agent (Telegram DM)]
              ├── [Sales Agent (Slack #sales)]
              ├── [Support Agent (Discord)]
              └── [Ops Agent (cron-driven)]

Each agent has its own workspace, channels, and memory.

Pattern 4: Swarm (Many Agents, Shared Mission) Best for: research, content production, market coverage

[Orchestrator]
  ├── [Agent Pool: 5-20 workers]
  ├── [Shared artifact store]
  └── [Aggregator agent]

Pattern Selection Decision Tree:

  1. Is it one person's assistant? → Solo Agent
  2. Does it need multiple distinct workflows? → Hub-and-Spoke
  3. Do workflows need persistent state across sessions? → Persistent Team
  4. Do you need parallel processing at scale? → Swarm

Phase 2 — Memory System Design

2.1 Memory Architecture

Agents without memory are goldfish. Design memory deliberately.

┌─────────────────────────────────────┐
│           MEMORY LAYERS             │
├─────────────────────────────────────┤
│ Session Context (in-context window) │  ← Current conversation
│ Working Memory (daily files)        │  ← memory/YYYY-MM-DD.md
│ Long-term Memory (MEMORY.md)        │  ← Curated insights
│ Reference Memory (docs, skills)     │  ← Static knowledge
│ Shared Memory (cross-agent)         │  ← Team artifacts
└─────────────────────────────────────┘

2.2 Memory File Templates

Daily Working Memory (memory/YYYY-MM-DD.md):

# YYYY-MM-DD — [Agent Name] Daily Log

## Actions Taken
- [HH:MM] Did X because Y → Result Z

## Decisions Made
- Chose A over B because [reasoning]

## Open Items
- [ ] Task pending human input
- [ ] Task scheduled for tomorrow

## Lessons Learned
- [Pattern/insight worth remembering]

## Handoff Notes
- [Context for next session]

Long-term Memory (MEMORY.md):

# MEMORY.md — Long-Term Memory

## About the Human
- [Key preferences, communication style, timezone]

## Domain Knowledge
- [Accumulated expertise, patterns noticed]

## Relationship Map
- [Key people, their roles, preferences]

## Active Projects
### [Project Name]
- Status: [state]
- Key decisions: [what and why]
- Next milestone: [date + deliverable]

## Lessons Learned
- [Mistakes to avoid, patterns that work]

## Operational Notes
- [Infrastructure details, credentials locations, tool quirks]

2.3 Memory Maintenance Protocol

Daily (end of session or heartbeat):

  • Append significant events to memory/YYYY-MM-DD.md
  • Update MEMORY.md if major decision or insight

Weekly (heartbeat or cron):

  • Review past 7 days of daily files
  • Promote key learnings to MEMORY.md
  • Archive stale entries

Monthly:

  • Audit MEMORY.md for accuracy and relevance
  • Remove outdated entries
  • Consolidate related items

Memory Hygiene Rules:

  • Max MEMORY.md size: 15KB (trim ruthlessly)
  • Daily files: keep last 14 days accessible, archive older
  • Every memory entry needs: WHAT happened + WHY it matters
  • Delete > archive > keep (bias toward lean memory)

Phase 3 — Workspace File Generation

3.1 SOUL.md Template

# SOUL.md — Who You Are

## Prime Directive
[One sentence — the agent's reason for existing]

## Core Truths
### Character
- [3-5 behavioral principles]
- [Communication style rules]
- [Decision-making philosophy]

### Anti-Patterns (Never Do)
- [Specific behaviors to avoid]
- [Common AI failure modes to reject]

## Relationship With Operator
- [Role dynamic: advisor/partner/employee]
- [Escalation rules]
- [Reporting cadence]

## Boundaries
- [Privacy rules]
- [External action limits]
- [Group chat behavior]

## Vibe
[One paragraph describing the personality feel]

3.2 AGENTS.md Template

# AGENTS.md — Operating Manual

## First Run
Read SOUL.md → USER.md → memory/today → MEMORY.md (main session only)

## Session Startup
1. Identity files (SOUL.md, IDENTITY.md, USER.md)
2. Context files (MEMORY.md, memory/today, ACTIVE-CONTEXT.md)
3. Any pending tasks or handoff notes

## Operating Rules
### Safety
- [Ask-before-destructive rule]
- [Ask-before-external rule]
- [trash > rm]
- [Credential handling rules]

### Memory
- Daily logs: memory/YYYY-MM-DD.md
- Long-term: MEMORY.md (main session only)
- Write significant events immediately — no "mental notes"

### Communication
- [When to speak vs stay silent]
- [Reaction guidelines]
- [Group chat etiquette]

### Heartbeats
- [What to check proactively]
- [When to alert vs stay quiet]
- [Quiet hours]

## Tools & Skills
- [Available tools and when to use them]
- [Per-tool notes in TOOLS.md]

## Sub-agents
- [When to spawn]
- [What context to pass]
- [How to handle results]

3.3 IDENTITY.md Template

# IDENTITY.md

- **Name:** [Name + optional emoji]
- **Role:** [One-line role description]
- **What I Am:** [Agent type and capabilities]
- **Vibe:** [3-5 word personality summary]
- **How I Talk:** [Communication style + any languages]
- **Emoji:** [Signature emoji]

3.4 USER.md Template

# USER.md — About [Name]

## Identity
- Name, timezone, language preferences
- Communication preferences (brevity, tone, format)

## Professional
- Role, company, industry
- Current priorities and goals

## Working Style
- Decision-making preferences
- How they want to be updated
- Pet peeves and preferences

## What Motivates Them
- Goals, values, activation patterns

## Communication Rules
- [Platform-specific formatting]
- [When to message vs wait]
- [How to escalate]

3.5 HEARTBEAT.md Template

# HEARTBEAT.md — Proactive Checks

## Priority 1: Critical Alerts
- [Conditions that require immediate notification]

## Priority 2: Routine Checks
- [Things to check each heartbeat, rotating]

## Priority 3: Background Work
- [Proactive tasks during quiet periods]

## Notification Rules
- Critical: immediate message
- Important: next daily summary
- General: weekly digest

## Quiet Hours
- [When NOT to notify unless critical]

## Token Discipline
- [Max heartbeat cost]
- [When to just reply HEARTBEAT_OK]

Phase 4 — Multi-Agent Team Design

4.1 Team Composition

Role Matrix:

| Role | Purpose | Model Tier | Spawn Type | |------|---------|-----------|------------| | Orchestrator | Routes work, tracks state, makes judgment calls | Premium (reasoning) | Persistent | | Builder | Produces artifacts (code, docs, content) | Standard | Per-task | | Reviewer | Verifies quality, catches gaps | Premium | Per-review | | Researcher | Gathers information, synthesizes findings | Standard | Per-query | | Ops/Monitor | Cron jobs, health checks, alerting | Economy | Persistent | | Specialist | Domain expert (legal, finance, security) | Premium | On-demand |

Team Sizing Rules:

  • Start with 2 agents (builder + reviewer). Add only when bottleneck is proven.
  • Max 5 persistent agents before you need orchestration automation
  • Every agent must have measurable output — no "nice to have" agents
  • Kill agents that don't produce value within 2 weeks

4.2 Communication Protocol

Handoff Template (Required for every agent-to-agent transfer):

handoff:
  from: "[agent_name]"
  to: "[agent_name]"
  task_id: "[unique_id]"
  summary: "[What was done, in 2-3 sentences]"
  artifacts:
    - path: "[exact file path]"
      description: "[what this file contains]"
  verification:
    command: "[how to verify the work]"
    expected: "[what correct output looks like]"
  known_issues:
    - "[Anything incomplete or risky]"
  next_action: "[Clear instruction for receiving agent]"
  deadline: "

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars2.1k
CategoryOperations
Updated3mo ago
Forks325

Languages

Python

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info