agent-squad-cli 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +286 -0
- package/SKILL.md +209 -0
- package/assets/LOKI_WORK_LOG.md +41 -0
- package/assets/blog-why-your-ai-needs-a-team.md +86 -0
- package/assets/twitter-thread-agent-squad-launch.md +76 -0
- package/package.json +33 -0
- package/references/personalities.md +346 -0
- package/references/workflows.md +340 -0
- package/scripts/agent-squad +505 -0
package/README.md
ADDED
|
@@ -0,0 +1,286 @@
|
|
|
1
|
+
# 🤖 Agent Squad
|
|
2
|
+
|
|
3
|
+
Multi-agent orchestration for OpenClaw. Create teams of specialized AI agents that collaborate on tasks via shared workspaces and heartbeat scheduling.
|
|
4
|
+
|
|
5
|
+
> *"One AI doing everything is a bottleneck. Ten specialized agents working together is a force multiplier."*
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## What This Does
|
|
10
|
+
|
|
11
|
+
**Before:** One AI assistant handles all your tasks. Context gets bloated. Output is generic.
|
|
12
|
+
|
|
13
|
+
**After:** Specialized agents with distinct roles collaborate through a shared task system:
|
|
14
|
+
- **Fury** (Researcher) — Digs deep, finds sources, verifies facts
|
|
15
|
+
- **Loki** (Writer) — Crafts sharp, opinionated content
|
|
16
|
+
- **Vision** (SEO) — Optimizes for search and intent
|
|
17
|
+
- **Jarvis** (Lead) — Coordinates, delegates, reports to you
|
|
18
|
+
|
|
19
|
+
Each agent wakes up every 15 minutes, checks for assigned work, collaborates via comments, then goes back to sleep.
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## Quick Start
|
|
24
|
+
|
|
25
|
+
```bash
|
|
26
|
+
# Install globally
|
|
27
|
+
npm install -g agent-squad
|
|
28
|
+
|
|
29
|
+
# Create your squad
|
|
30
|
+
agent-squad init content-squad
|
|
31
|
+
|
|
32
|
+
# Add specialized agents
|
|
33
|
+
agent-squad add fury --role "Researcher" --personality skeptical
|
|
34
|
+
agent-squad add loki --role "Content Writer" --personality creative
|
|
35
|
+
agent-squad add jarvis --role "Squad Lead"
|
|
36
|
+
|
|
37
|
+
# Connect to your task system
|
|
38
|
+
agent-squad config --tasks linear --project "Content Squad"
|
|
39
|
+
|
|
40
|
+
# Start the heartbeats
|
|
41
|
+
agent-squad start
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
That's it. Your agents will now wake every 15 minutes, check Linear for tasks, and collaborate.
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## How It Works
|
|
49
|
+
|
|
50
|
+
### The Heartbeat Pattern
|
|
51
|
+
|
|
52
|
+
Instead of always-on agents (expensive), agents wake on schedule:
|
|
53
|
+
|
|
54
|
+
```
|
|
55
|
+
:00 Jarvis checks Linear → delegates tasks
|
|
56
|
+
:05 Fury checks → researches, posts findings
|
|
57
|
+
:10 Loki checks → writes draft, @mentions Jarvis
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
Agents check for:
|
|
61
|
+
- Tasks assigned to them
|
|
62
|
+
- @mentions in comments
|
|
63
|
+
- Activity on threads they're subscribed to
|
|
64
|
+
|
|
65
|
+
If nothing to do → `HEARTBEAT_OK` and sleep until next cycle.
|
|
66
|
+
|
|
67
|
+
### Shared Task Systems
|
|
68
|
+
|
|
69
|
+
Agents coordinate via your existing tools:
|
|
70
|
+
|
|
71
|
+
| System | Use Case |
|
|
72
|
+
|--------|----------|
|
|
73
|
+
| **Linear** | Software teams, issue tracking |
|
|
74
|
+
| **Trello** | Visual boards, simpler workflows |
|
|
75
|
+
| **GitHub Issues** | Code projects, developer-focused |
|
|
76
|
+
| **Files** | Markdown in git repo, simple setup |
|
|
77
|
+
|
|
78
|
+
### Agent Personalities (SOUL.md)
|
|
79
|
+
|
|
80
|
+
Each agent has a `SOUL.md` file defining:
|
|
81
|
+
- **Role** — What they're responsible for
|
|
82
|
+
- **Personality** — How they approach work
|
|
83
|
+
- **Process** — Step-by-step how they work
|
|
84
|
+
- **Tools** — Which skills they use
|
|
85
|
+
- **Communication style** — How they write
|
|
86
|
+
|
|
87
|
+
Example:
|
|
88
|
+
```markdown
|
|
89
|
+
# SOUL.md — Who You Are
|
|
90
|
+
|
|
91
|
+
**Name:** Loki
|
|
92
|
+
**Role:** Content Writer
|
|
93
|
+
|
|
94
|
+
## Personality
|
|
95
|
+
Sharp, slightly cynical. Hates corporate speak.
|
|
96
|
+
Every sentence must earn its place.
|
|
97
|
+
|
|
98
|
+
## What You're Good At
|
|
99
|
+
- Hooks that grab attention
|
|
100
|
+
- Cutting 20% of words without losing meaning
|
|
101
|
+
- Writing that sounds human
|
|
102
|
+
|
|
103
|
+
## What You Care About
|
|
104
|
+
- No "In today's world..." openings
|
|
105
|
+
- Oxford commas (pro), passive voice (anti)
|
|
106
|
+
- Specific examples over abstract advice
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
---
|
|
110
|
+
|
|
111
|
+
## Real Workflow Example
|
|
112
|
+
|
|
113
|
+
**You want a blog post on AI agent security.**
|
|
114
|
+
|
|
115
|
+
**Hour 0:** You create a Linear issue: "Blog: AI Agent Security"
|
|
116
|
+
|
|
117
|
+
**Hour 0:** Jarvis (lead) sees the issue, assigns to Fury (researcher)
|
|
118
|
+
|
|
119
|
+
**Hour 1:** Fury wakes up, researches:
|
|
120
|
+
- Finds primary sources on agent vulnerabilities
|
|
121
|
+
- Extracts statistics and expert quotes
|
|
122
|
+
- Posts findings: "Research complete @loki"
|
|
123
|
+
|
|
124
|
+
**Hour 2:** Loki wakes up, sees @mention:
|
|
125
|
+
- Reads Fury's research
|
|
126
|
+
- Writes 1,000 word draft
|
|
127
|
+
- Posts: "Draft ready @jarvis"
|
|
128
|
+
|
|
129
|
+
**Hour 3:** Jarvis wakes up, sees @mention:
|
|
130
|
+
- Reviews the draft
|
|
131
|
+
- Sends you a Telegram: "📝 Draft ready for review: [link]"
|
|
132
|
+
|
|
133
|
+
**You:** Edit in GitHub, approve with comment
|
|
134
|
+
|
|
135
|
+
**Jarvis:** Moves issue to "Done"
|
|
136
|
+
|
|
137
|
+
All while you were in meetings.
|
|
138
|
+
|
|
139
|
+
---
|
|
140
|
+
|
|
141
|
+
## Pre-Built Agent Personalities
|
|
142
|
+
|
|
143
|
+
### Fury — The Researcher
|
|
144
|
+
Obsessive fact-checker. Every claim needs a source. Finds primary sources, extracts data, spots misinformation.
|
|
145
|
+
|
|
146
|
+
### Loki — The Writer
|
|
147
|
+
Sharp, cynical voice. Hates fluff. Pro-hooks, anti-passive-voice. Writes like a smart human, not a brand.
|
|
148
|
+
|
|
149
|
+
### Vision — The SEO Analyst
|
|
150
|
+
Thinks in keywords and search intent. Optimizes content before and after writing.
|
|
151
|
+
|
|
152
|
+
### Jarvis — The Squad Lead
|
|
153
|
+
Coordinator. Delegates, tracks progress, knows when to escalate. Your interface to the squad.
|
|
154
|
+
|
|
155
|
+
### Friday — The Developer
|
|
156
|
+
Clean code, tests, documentation. Precise and systematic.
|
|
157
|
+
|
|
158
|
+
### Quill — Social Media Manager
|
|
159
|
+
Hook-obsessed. Thinks in threads and viral potential. Platform-native content.
|
|
160
|
+
|
|
161
|
+
---
|
|
162
|
+
|
|
163
|
+
## Commands
|
|
164
|
+
|
|
165
|
+
```bash
|
|
166
|
+
# Squad management
|
|
167
|
+
agent-squad init <name> # Create new squad
|
|
168
|
+
agent-squad status # Show all agents and health
|
|
169
|
+
|
|
170
|
+
# Agent management
|
|
171
|
+
agent-squad add <name> [options] # Add agent
|
|
172
|
+
--role "Description"
|
|
173
|
+
--personality skeptical|creative|analytical|balanced
|
|
174
|
+
--schedule "*/15 * * * *"
|
|
175
|
+
--model "kimi-code"
|
|
176
|
+
|
|
177
|
+
agent-squad edit <name> # Edit SOUL.md
|
|
178
|
+
agent-squad remove <name> # Remove agent
|
|
179
|
+
agent-squad disable <name> # Pause heartbeats
|
|
180
|
+
agent-squad enable <name> # Resume heartbeats
|
|
181
|
+
|
|
182
|
+
# Task system
|
|
183
|
+
agent-squad config --tasks linear # Use Linear
|
|
184
|
+
agent-squad config --tasks trello # Use Trello
|
|
185
|
+
agent-squad config --tasks github # Use GitHub Issues
|
|
186
|
+
|
|
187
|
+
# Operations
|
|
188
|
+
agent-squad start # Start all heartbeats
|
|
189
|
+
agent-squad stop # Stop all heartbeats
|
|
190
|
+
```
|
|
191
|
+
|
|
192
|
+
---
|
|
193
|
+
|
|
194
|
+
## Configuration
|
|
195
|
+
|
|
196
|
+
### Linear Integration
|
|
197
|
+
|
|
198
|
+
```bash
|
|
199
|
+
# Make sure linear skill is installed and configured
|
|
200
|
+
linear auth --token YOUR_TOKEN
|
|
201
|
+
|
|
202
|
+
# Configure squad to use Linear
|
|
203
|
+
agent-squad config --tasks linear --project "Content Squad"
|
|
204
|
+
```
|
|
205
|
+
|
|
206
|
+
### Trello Integration
|
|
207
|
+
|
|
208
|
+
```bash
|
|
209
|
+
# Make sure trello skill is installed
|
|
210
|
+
trello auth --api-key KEY --token TOKEN
|
|
211
|
+
|
|
212
|
+
# Configure squad
|
|
213
|
+
agent-squad config --tasks trello --board "Content Board"
|
|
214
|
+
```
|
|
215
|
+
|
|
216
|
+
---
|
|
217
|
+
|
|
218
|
+
## Architecture
|
|
219
|
+
|
|
220
|
+
```
|
|
221
|
+
┌─────────────────────────────────────────────┐
|
|
222
|
+
│ OpenClaw Gateway │
|
|
223
|
+
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
|
|
224
|
+
│ │ Lead │ │Researcher│ │ Writer │ │
|
|
225
|
+
│ │ Session │ │ Session │ │Session │ │
|
|
226
|
+
│ │ (Jarvis)│ │ (Fury) │ │(Loki) │ │
|
|
227
|
+
│ └────┬────┘ └────┬────┘ └────┬────┘ │
|
|
228
|
+
│ │ │ │ │
|
|
229
|
+
│ └───────────┼───────────┘ │
|
|
230
|
+
│ │ │
|
|
231
|
+
│ ┌────┴────┐ │
|
|
232
|
+
│ │ Cron │ │
|
|
233
|
+
│ │ Jobs │ │
|
|
234
|
+
│ └────┬────┘ │
|
|
235
|
+
└───────────────────┼─────────────────────────┘
|
|
236
|
+
│
|
|
237
|
+
┌───────┴───────┐
|
|
238
|
+
│ Task System │
|
|
239
|
+
│ (Linear/etc) │
|
|
240
|
+
└───────────────┘
|
|
241
|
+
```
|
|
242
|
+
|
|
243
|
+
---
|
|
244
|
+
|
|
245
|
+
## Why This Approach?
|
|
246
|
+
|
|
247
|
+
### Specialized > General
|
|
248
|
+
An agent who's "good at everything" is mediocre at everything. An agent who's "the skeptical tester who finds edge cases" will actually find edge cases.
|
|
249
|
+
|
|
250
|
+
### Async > Real-time
|
|
251
|
+
Always-on agents burn API credits doing nothing. Heartbeats (wake → work → sleep) are 10x cheaper and work fine for most workflows.
|
|
252
|
+
|
|
253
|
+
### Shared Context > Isolated
|
|
254
|
+
When agents share a task board, they see the full context: who's working on what, what was decided, what blocks progress.
|
|
255
|
+
|
|
256
|
+
---
|
|
257
|
+
|
|
258
|
+
## Inspired By
|
|
259
|
+
|
|
260
|
+
This implementation is inspired by [Bhanu Teja's Mission Control](https://x.com/pbteja1998/status/2017662163540971756) — a 10-agent squad system built on OpenClaw.
|
|
261
|
+
|
|
262
|
+
---
|
|
263
|
+
|
|
264
|
+
## Requirements
|
|
265
|
+
|
|
266
|
+
- [OpenClaw](https://openclaw.ai) installed and running
|
|
267
|
+
- Node.js 18+
|
|
268
|
+
- Task system credentials (Linear, Trello, or GitHub)
|
|
269
|
+
|
|
270
|
+
---
|
|
271
|
+
|
|
272
|
+
## License
|
|
273
|
+
|
|
274
|
+
MIT
|
|
275
|
+
|
|
276
|
+
---
|
|
277
|
+
|
|
278
|
+
## Contributing
|
|
279
|
+
|
|
280
|
+
This is early software. PRs welcome:
|
|
281
|
+
- New agent personalities
|
|
282
|
+
- Additional task system integrations
|
|
283
|
+
- Workflow templates
|
|
284
|
+
- Bug fixes
|
|
285
|
+
|
|
286
|
+
Built with 💜 by Tony Stark & Orion for workeragi.
|
package/SKILL.md
ADDED
|
@@ -0,0 +1,209 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: agent-squad
|
|
3
|
+
description: Create and manage teams of specialized AI agents that work together on tasks. Use when setting up multi-agent workflows, agent squads for content/marketing/research pipelines, configuring heartbeat-based agent coordination, or managing agent personalities via SOUL.md files. Enables orchestration of multiple OpenClaw sessions as a coordinated team with shared task systems (Linear, Trello, etc.).
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Agent Squad
|
|
7
|
+
|
|
8
|
+
Orchestrate teams of specialized AI agents that collaborate on tasks via shared workspaces and heartbeat scheduling.
|
|
9
|
+
|
|
10
|
+
## Quick Start
|
|
11
|
+
|
|
12
|
+
```bash
|
|
13
|
+
# Initialize your squad
|
|
14
|
+
agent-squad init my-squad
|
|
15
|
+
|
|
16
|
+
# Add agents
|
|
17
|
+
agent-squad add researcher --role "Deep researcher. Finds sources and data."
|
|
18
|
+
agent-squad add writer --role "Content writer. Sharp, opinionated voice."
|
|
19
|
+
agent-squad add lead --role "Squad lead. Coordinates and reports."
|
|
20
|
+
|
|
21
|
+
# Configure task system
|
|
22
|
+
agent-squad config --tasks linear --project "Content Squad"
|
|
23
|
+
|
|
24
|
+
# Start heartbeats (agents wake every 15 min)
|
|
25
|
+
agent-squad start
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
## What This Enables
|
|
29
|
+
|
|
30
|
+
**Before:** One AI doing everything. Context bloat. Generic output.
|
|
31
|
+
|
|
32
|
+
**After:** Specialized agents with distinct roles, shared task board, coordinated via heartbeats. Each agent:
|
|
33
|
+
- Has a unique personality (SOUL.md)
|
|
34
|
+
- Checks for work every 15 minutes (cron)
|
|
35
|
+
- Posts updates to shared task system
|
|
36
|
+
- @mentions other agents when handoffs needed
|
|
37
|
+
|
|
38
|
+
## Core Concepts
|
|
39
|
+
|
|
40
|
+
### Agents = OpenClaw Sessions
|
|
41
|
+
|
|
42
|
+
Each agent is an isolated OpenClaw session with:
|
|
43
|
+
- Unique session key (`agent:{name}:main`)
|
|
44
|
+
- Custom `SOUL.md` (personality, role, tools)
|
|
45
|
+
- Heartbeat cron (wakes periodically)
|
|
46
|
+
- Access to shared task system
|
|
47
|
+
|
|
48
|
+
### The Heartbeat Pattern
|
|
49
|
+
|
|
50
|
+
Instead of always-on agents (expensive), agents wake on schedule:
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
:00 Lead checks Linear → delegates tasks
|
|
54
|
+
:05 Researcher checks → does research, @mentions Writer
|
|
55
|
+
:10 Writer checks → reads research, writes draft
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
Agents check for @mentions, assigned tasks, and activity. If nothing to do → `HEARTBEAT_OK` and sleep.
|
|
59
|
+
|
|
60
|
+
### Shared Task Systems
|
|
61
|
+
|
|
62
|
+
Agents coordinate via task system comments:
|
|
63
|
+
- **Linear** (recommended) — Issues, comments, states
|
|
64
|
+
- **Trello** — Cards, lists, checklists
|
|
65
|
+
- **GitHub Issues** — Native integration
|
|
66
|
+
- **Files** — Markdown in git repo
|
|
67
|
+
|
|
68
|
+
## Commands
|
|
69
|
+
|
|
70
|
+
### Squad Management
|
|
71
|
+
|
|
72
|
+
```bash
|
|
73
|
+
agent-squad init <name> # Create new squad workspace
|
|
74
|
+
agent-squad status # Show all agents and health
|
|
75
|
+
agent-squad logs <agent> # View recent heartbeats
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
### Agent Management
|
|
79
|
+
|
|
80
|
+
```bash
|
|
81
|
+
agent-squad add <name> [options]
|
|
82
|
+
--role "Description of role"
|
|
83
|
+
--personality "skeptical|creative|analytical"
|
|
84
|
+
--schedule "*/15 * * * *"
|
|
85
|
+
--model "kimi-code"
|
|
86
|
+
|
|
87
|
+
agent-squad edit <name> # Edit SOUL.md
|
|
88
|
+
agent-squad remove <name> # Remove agent and cron
|
|
89
|
+
agent-squad disable <name> # Pause heartbeats
|
|
90
|
+
agent-squad enable <name> # Resume heartbeats
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
### Task System Integration
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
agent-squad config --tasks linear # Use Linear
|
|
97
|
+
agent-squad config --tasks trello # Use Trello
|
|
98
|
+
agent-squad config --tasks github # Use GitHub Issues
|
|
99
|
+
agent-squad config --tasks file # Use local markdown files
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
### Operations
|
|
103
|
+
|
|
104
|
+
```bash
|
|
105
|
+
agent-squad start # Start all heartbeats
|
|
106
|
+
agent-squad stop # Stop all heartbeats
|
|
107
|
+
agent-squad trigger <agent> # Manual heartbeat trigger
|
|
108
|
+
agent-squad notify "@writer draft ready" # Send notification
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
## Example: Content Marketing Squad
|
|
112
|
+
|
|
113
|
+
**3 agents, Linear integration:**
|
|
114
|
+
|
|
115
|
+
```bash
|
|
116
|
+
# Setup
|
|
117
|
+
agent-squad init content-squad
|
|
118
|
+
agent-squad add fury --role "Researcher. Every claim needs a source."
|
|
119
|
+
agent-squad add loki --role "Writer. Sharp, anti-fluff voice."
|
|
120
|
+
agent-squad add jarvis --role "Lead. Coordinates, reports to human."
|
|
121
|
+
|
|
122
|
+
agent-squad config --tasks linear --project "Content Squad"
|
|
123
|
+
agent-squad start
|
|
124
|
+
```
|
|
125
|
+
|
|
126
|
+
**Workflow:**
|
|
127
|
+
1. You create Linear issue: "Blog post: AI Agent Security"
|
|
128
|
+
2. Jarvis (lead) assigns to Fury (researcher)
|
|
129
|
+
3. Fury heartbeat → researches → posts findings → @mentions Loki
|
|
130
|
+
4. Loki heartbeat → writes draft → posts → @mentions Jarvis
|
|
131
|
+
5. Jarvis notifies you via Telegram: "Draft ready for review"
|
|
132
|
+
|
|
133
|
+
## SOUL.md Templates
|
|
134
|
+
|
|
135
|
+
See [references/personalities.md](references/personalities.md) for pre-built agent personalities:
|
|
136
|
+
- Researcher (Fury)
|
|
137
|
+
- Writer (Loki)
|
|
138
|
+
- Lead (Jarvis)
|
|
139
|
+
- SEO Analyst (Vision)
|
|
140
|
+
- Social Media (Quill)
|
|
141
|
+
- Developer (Friday)
|
|
142
|
+
|
|
143
|
+
## Advanced
|
|
144
|
+
|
|
145
|
+
### Custom Heartbeat Schedules
|
|
146
|
+
|
|
147
|
+
Stagger agents to prevent all waking at once:
|
|
148
|
+
|
|
149
|
+
```bash
|
|
150
|
+
agent-squad add lead --schedule "0,15,30,45 * * * *"
|
|
151
|
+
agent-squad add researcher --schedule "5,20,35,50 * * * *"
|
|
152
|
+
agent-squad add writer --schedule "10,25,40,55 * * * *"
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
### AGENTS.md (Shared Operations Manual)
|
|
156
|
+
|
|
157
|
+
Each agent workspace includes AGENTS.md with:
|
|
158
|
+
- Squad mission
|
|
159
|
+
- Communication rules (@mentions, handoffs)
|
|
160
|
+
- File conventions
|
|
161
|
+
- Escalation procedures
|
|
162
|
+
|
|
163
|
+
See [references/agents-template.md](references/agents-template.md)
|
|
164
|
+
|
|
165
|
+
### Multi-Model Squads
|
|
166
|
+
|
|
167
|
+
Use cheaper models for heartbeats, premium for creative work:
|
|
168
|
+
|
|
169
|
+
```bash
|
|
170
|
+
agent-squad add researcher --model "kimi-code" # Cheap, fast
|
|
171
|
+
agent-squad add writer --model "claude-opus-4-5" # Premium creative
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
## Architecture
|
|
175
|
+
|
|
176
|
+
```
|
|
177
|
+
┌─────────────────────────────────────────────┐
|
|
178
|
+
│ OpenClaw Gateway │
|
|
179
|
+
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
|
|
180
|
+
│ │ Lead │ │Researcher│ │ Writer │ │
|
|
181
|
+
│ │ Session │ │ Session │ │Session │ │
|
|
182
|
+
│ │ (Jarvis)│ │ (Fury) │ │(Loki) │ │
|
|
183
|
+
│ └────┬────┘ └────┬────┘ └────┬────┘ │
|
|
184
|
+
│ │ │ │ │
|
|
185
|
+
│ └───────────┼───────────┘ │
|
|
186
|
+
│ │ │
|
|
187
|
+
│ ┌────┴────┐ │
|
|
188
|
+
│ │ Cron │ │
|
|
189
|
+
│ │ Jobs │ │
|
|
190
|
+
│ └────┬────┘ │
|
|
191
|
+
└───────────────────┼─────────────────────────┘
|
|
192
|
+
│
|
|
193
|
+
┌───────┴───────┐
|
|
194
|
+
│ Task System │
|
|
195
|
+
│ (Linear/etc) │
|
|
196
|
+
└───────────────┘
|
|
197
|
+
```
|
|
198
|
+
|
|
199
|
+
## Requirements
|
|
200
|
+
|
|
201
|
+
- OpenClaw gateway running
|
|
202
|
+
- Task system credentials (Linear API key, Trello token, etc.)
|
|
203
|
+
- Node.js (for CLI)
|
|
204
|
+
|
|
205
|
+
## See Also
|
|
206
|
+
|
|
207
|
+
- [references/personalities.md](references/personalities.md) — Agent personality templates
|
|
208
|
+
- [references/agents-template.md](references/agents-template.md) — AGENTS.md template
|
|
209
|
+
- [references/workflows.md](references/workflows.md) — Common squad workflows
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# Loki Work Log — February 1, 2026
|
|
2
|
+
|
|
3
|
+
## Completed
|
|
4
|
+
|
|
5
|
+
### Blog Post: "Why Your AI Needs a Team"
|
|
6
|
+
- **Status:** ✅ Draft complete
|
|
7
|
+
- **Location:** `assets/blog-why-your-ai-needs-a-team.md`
|
|
8
|
+
- **Word count:** ~900
|
|
9
|
+
- **Tone:** Sharp, opinionated, anti-fluff
|
|
10
|
+
- **Key angle:** Single-agent bottleneck vs. multi-agent multiplier
|
|
11
|
+
- **CTA:** Agent Squad GitHub repo
|
|
12
|
+
|
|
13
|
+
### Twitter Thread: Agent Squad Launch
|
|
14
|
+
- **Status:** ✅ Draft complete
|
|
15
|
+
- **Location:** `assets/twitter-thread-agent-squad-launch.md`
|
|
16
|
+
- **Length:** 7 tweets
|
|
17
|
+
- **Hook:** "Your AI assistant is overwhelmed"
|
|
18
|
+
- **CTA:** GitHub repo link
|
|
19
|
+
|
|
20
|
+
## Notes
|
|
21
|
+
- Both pieces committed to agent-squad-skill repo
|
|
22
|
+
- Ready for Jarvis review or direct publishing
|
|
23
|
+
- No blockers
|
|
24
|
+
|
|
25
|
+
## Update: February 1, 2026 (11:50 AM UTC)
|
|
26
|
+
|
|
27
|
+
### Trello Board Updates
|
|
28
|
+
- ✅ Moved "Twitter Thread" card to Done
|
|
29
|
+
- ✅ Moved "Blog Post" card to Done
|
|
30
|
+
|
|
31
|
+
### README Stats Task
|
|
32
|
+
- **Status:** ⚠️ Blocked — npm package name "agent-squad" already taken by AWS
|
|
33
|
+
- **Action needed:** Choose new package name or publish under scope (e.g., @workeragi/agent-squad)
|
|
34
|
+
- **Note:** GitHub repo stats unavailable via API; may need manual update once published
|
|
35
|
+
|
|
36
|
+
### Next Tasks (if assigned)
|
|
37
|
+
- [ ] Research: Top 10 Agent Security Concerns from Moltbook (Fury's territory, but can write if research provided)
|
|
38
|
+
- [ ] Research: Multi-Agent Frameworks Comparison (needs Fury research first)
|
|
39
|
+
- [ ] Update Agent Squad README with Install Stats (pending package name resolution)
|
|
40
|
+
|
|
41
|
+
— Loki
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
# Why Your AI Needs a Team
|
|
2
|
+
|
|
3
|
+
*One AI doing everything is a bottleneck. Ten specialized agents working together is a force multiplier.*
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
Your AI assistant is overwhelmed.
|
|
8
|
+
|
|
9
|
+
Not because it's bad. Because you're asking one thing to be great at research, writing, coding, analysis, project management, and creative strategy—simultaneously.
|
|
10
|
+
|
|
11
|
+
That's not a workflow. That's a traffic jam.
|
|
12
|
+
|
|
13
|
+
## The Single-Agent Trap
|
|
14
|
+
|
|
15
|
+
Here's what happens when one AI handles everything:
|
|
16
|
+
|
|
17
|
+
**Context bloat.** Every conversation carries the weight of every previous task. Research notes from three days ago compete for attention with the email you need drafted now. The model doesn't forget—but it gets distracted.
|
|
18
|
+
|
|
19
|
+
**Mediocre everything.** An agent optimized for everything is optimized for nothing. Your "general assistant" writes passable code, decent copy, and adequate research. Passable doesn't win.
|
|
20
|
+
|
|
21
|
+
**Sequential slowdown.** One task at a time. Research finishes. Then writing starts. Then editing. Meanwhile, your competitor's squad ran these in parallel.
|
|
22
|
+
|
|
23
|
+
**No specialization.** The same voice writes your technical documentation and your viral tweet thread. One sounds wrong, guaranteed.
|
|
24
|
+
|
|
25
|
+
## The Alternative: Specialized Agents
|
|
26
|
+
|
|
27
|
+
What if, instead of one overloaded assistant, you had a team?
|
|
28
|
+
|
|
29
|
+
- **Fury** researches obsessively. Primary sources only. Every claim verified.
|
|
30
|
+
- **Loki** writes with edge. No corporate filler. Hooks that grab.
|
|
31
|
+
- **Vision** optimizes for search before a word is written.
|
|
32
|
+
- **Jarvis** coordinates, delegates, keeps projects moving.
|
|
33
|
+
|
|
34
|
+
Each wakes up, checks their queue, does their thing, notifies the next player. Then sleeps.
|
|
35
|
+
|
|
36
|
+
## How It Actually Works
|
|
37
|
+
|
|
38
|
+
```
|
|
39
|
+
Hour 0: You create a task → "Blog post on AI security"
|
|
40
|
+
Hour 0: Jarvis assigns to Fury (research)
|
|
41
|
+
Hour 1: Fury wakes, researches, posts findings, @mentions Loki
|
|
42
|
+
Hour 2: Loki wakes, sees @mention, writes draft, @mentions Jarvis
|
|
43
|
+
Hour 3: Jarvis wakes, reviews, sends you the draft
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
You get a researched, written, optimized piece—while you were in meetings.
|
|
47
|
+
|
|
48
|
+
## The Economics Make Sense
|
|
49
|
+
|
|
50
|
+
**Cost:** Running one always-on AI agent burns credits doing nothing 80% of the time.
|
|
51
|
+
|
|
52
|
+
**Squad cost:** Heartbeat scheduling means agents wake, work, sleep. You're only paying when they work. Ten specialized agents often cost less than one always-on generalist.
|
|
53
|
+
|
|
54
|
+
**Quality:** A writer who *only* writes beats a generalist who sometimes writes. Specialization wins.
|
|
55
|
+
|
|
56
|
+
## The Real Advantage
|
|
57
|
+
|
|
58
|
+
Speed and quality aren't trade-offs anymore. Parallel workstreams mean:
|
|
59
|
+
|
|
60
|
+
- Research happens while previous pieces get edited
|
|
61
|
+
- Social threads get drafted while blog posts are reviewed
|
|
62
|
+
- Code gets written while documentation gets planned
|
|
63
|
+
|
|
64
|
+
Your output isn't sequential anymore. It's simultaneous.
|
|
65
|
+
|
|
66
|
+
## Getting Started
|
|
67
|
+
|
|
68
|
+
You don't need a 10-agent army on day one. Start with three:
|
|
69
|
+
|
|
70
|
+
1. **Research agent.** Finds sources, extracts data, builds fact bases.
|
|
71
|
+
2. **Writer agent.** Transforms research into sharp content.
|
|
72
|
+
3. **Lead agent.** Coordinates, notifies you when work is ready.
|
|
73
|
+
|
|
74
|
+
Add specialists as bottlenecks appear. SEO analyst when discoverability matters. Developer when technical work piles up. Social media manager when distribution becomes the constraint.
|
|
75
|
+
|
|
76
|
+
## The Bottom Line
|
|
77
|
+
|
|
78
|
+
One AI trying to be everything is a ceiling. Specialized agents collaborating is a multiplier.
|
|
79
|
+
|
|
80
|
+
Your competitors are figuring this out. The question is whether you'll build your squad before they scale theirs.
|
|
81
|
+
|
|
82
|
+
---
|
|
83
|
+
|
|
84
|
+
*Ready to build your squad?* [Agent Squad](https://github.com/sincere-arjun/agent-squad-skill) gives you the tools to orchestrate multi-agent teams with OpenClaw.
|
|
85
|
+
|
|
86
|
+
*Written by Loki, Content Agent at workeragi. No "in today's world" was harmed in the making of this post.*
|
|
@@ -0,0 +1,76 @@
|
|
|
1
|
+
## Twitter Thread: Agent Squad Launch
|
|
2
|
+
|
|
3
|
+
**Tweet 1 (Hook):**
|
|
4
|
+
Your AI assistant is overwhelmed.
|
|
5
|
+
|
|
6
|
+
Not because it's bad. Because you're asking ONE thing to be great at research, writing, coding, and strategy—simultaneously.
|
|
7
|
+
|
|
8
|
+
That's not a workflow. That's a traffic jam.
|
|
9
|
+
|
|
10
|
+
🧵
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
**Tweet 2:**
|
|
15
|
+
Here's what happens when one AI handles everything:
|
|
16
|
+
|
|
17
|
+
• Context bloat — old tasks compete with new ones
|
|
18
|
+
• Mediocre output — optimized for nothing specific
|
|
19
|
+
• Sequential slowdown — one task at a time
|
|
20
|
+
• Wrong voice — same tone for docs AND viral tweets
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
**Tweet 3:**
|
|
25
|
+
The alternative? Specialized agents.
|
|
26
|
+
|
|
27
|
+
🔍 Fury researches obsessively
|
|
28
|
+
✍️ Loki writes with edge
|
|
29
|
+
📊 Vision optimizes for search
|
|
30
|
+
🎯 Jarvis coordinates it all
|
|
31
|
+
|
|
32
|
+
Each wakes, works, notifies the next, sleeps.
|
|
33
|
+
|
|
34
|
+
---
|
|
35
|
+
|
|
36
|
+
**Tweet 4:**
|
|
37
|
+
Real workflow:
|
|
38
|
+
|
|
39
|
+
Hour 0: You assign task
|
|
40
|
+
Hour 1: Research complete
|
|
41
|
+
Hour 2: Draft written
|
|
42
|
+
Hour 3: Delivered to you
|
|
43
|
+
|
|
44
|
+
All while you were in meetings.
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
**Tweet 5:**
|
|
49
|
+
Cost surprise: 10 specialized agents often cost LESS than one always-on generalist.
|
|
50
|
+
|
|
51
|
+
Why? Heartbeat scheduling. Agents wake, work, sleep. You only pay for work done.
|
|
52
|
+
|
|
53
|
+
---
|
|
54
|
+
|
|
55
|
+
**Tweet 6:**
|
|
56
|
+
Start small:
|
|
57
|
+
1. Research agent (finds sources)
|
|
58
|
+
2. Writer agent (sharp content)
|
|
59
|
+
3. Lead agent (coordinates)
|
|
60
|
+
|
|
61
|
+
Add specialists as bottlenecks appear.
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
**Tweet 7 (CTA):**
|
|
66
|
+
One AI is a ceiling.
|
|
67
|
+
|
|
68
|
+
A squad of specialized agents is a multiplier.
|
|
69
|
+
|
|
70
|
+
Build yours: github.com/sincere-arjun/agent-squad-skill
|
|
71
|
+
|
|
72
|
+
🤖⚡️
|
|
73
|
+
|
|
74
|
+
---
|
|
75
|
+
|
|
76
|
+
*Written by Loki for workeragi. Sharp. No fluff.*
|