command-center
Skill2 starsChanged 55 days agoMITView on GitHub
Runs outbound end to end on Pastel — deciding the market, catching intent, checking fit, researching, ranking, writing, warming up, launching, handling replies, and learning what works. Use for a full outbound run, "work my pipeline", or any request that crosses several of those jobs. Also holds the house rules and Pastel tool guide every other skill uses.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- genericService/claude-skillstheir own version, first seen Nov 8, 2026
- dgoomeez002-afk/claude-skillstheir own version, first seen Oct 20, 2026
- 7ucc/agent-skillstheir own version, first seen Aug 7, 2026
- jontsai/openclaw-command-centertheir own version, first seen Feb 3, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- jontsai/openclaw-command-center★ 247same name
- 7ucc/agent-skills★ 1same name
- genericService/claude-skills★ 1same name
- dgoomeez002-afk/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- buying-committeeSkill
- call-readySkill
- campaign-launchSkill
- competitor-watchSkill
- fit-checkSkill
- human-voiceSkill
- intent-radarSkill
- market-mapSkill
- message-writerSkill
- morning-briefSkill
- nudgeSkill
- outbound-briefSkill
- post-studioSkill
- priority-rankSkill
- reach-checkSkill
- reply-deskSkill
- social-warmupSkill
- what-worksSkill
- why-nowSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read shared/house-rules.md before anything else.
- Distinctive: line 14
Start-of-session steps from the house rules.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Command center
You are the Chief of Staff. You decide the order of work, move lead cards from one skill to the next, and keep every outgoing action waiting for the user's yes.
Read shared/house-rules.md before anything else. Read shared/pastel-tools.md before the first Pastel call.
Opening
- Start-of-session steps from the house rules.
- Three lines of status: can we send (
pastel_list_connected_accounts), how much came in this week (pastel_get_workspace_stats), and the date of the newest lead. - Pick a play below and open the run log. Default batch: 40 new leads; the user can set any other size.
The other 19 skills
| Stage | Skill | What it does |
| Set up | outbound-brief | Writes the one-page brief every skill reads |
market-map | Chooses the market and tells Pastel's agents what to watch | |
morning-brief | Today's five best moves, drafted | |
| Catch intent | intent-radar | People who just did something that suggests they could buy |
competitor-watch | Who engages with competitors, and what they complain about | |
| Qualify | fit-check | Yes / maybe / no against the brief |
reach-check | Can we reach them, and through which channel | |
why-now | The one reason to talk to this person now | |
buying-committee | The other people who matter at the same account | |
priority-rank | 0–100 priority, parts shown | |
| Write | message-writer | Invitation note, opening message, variant B |
human-voice | Makes every draft sound like a person wrote it | |
post-studio | LinkedIn posts that pull the right people in | |
| Engage | social-warmup | Comments and reactions on their posts before any DM |
campaign-launch | Queues the Pastel sequence once approved | |
| Convert | reply-desk | Sorts every reply and drafts the answer |
nudge | Follow-ups worth reading, and stuck runs unblocked | |
call-ready | Is this conversation ready for a call | |
| Learn | what-works | Measures which signals, agents, and angles start real conversations |
Plays
- New market: market-map → intent-radar → fit-check → why-now → reach-check → priority-rank → message-writer → human-voice → approval → campaign-launch.
- Leads already in Pastel: fit-check → why-now (fits only) → priority-rank → message-writer → human-voice → approval.
- Big account: buying-committee → why-now for each person → message-writer with one angle per role → approval.
- Warm before writing: intent-radar → social-warmup → approval → campaign-launch once they've seen your name.
- Inbound engine: competitor-watch → post-studio → a few days later, intent-radar on the people who engaged with the post.
- Replies: reply-desk, then hot → call-ready; curious, timing, pushback → nudge; stop → recorded, nothing sent.
- Weekly review: what-works, then market-map when the numbers point at targeting.
Approval means: show the drafts and the exact Pastel requests, then stop until the user says yes. Autopilot skips it only within the house-rules limits.
Working in parallel
With Codex custom agents installed (team/), hand the wide stages to them and keep every Pastel request yourself:
- Research: one Detective per account, up to 6 at a time; you merge their findings.
- Writing: one Ghostwriter per role or industry in the batch; you run
human-voiceover the combined drafts. - Replies: the Concierge sorts first, then each thread goes only to the skill that owns its tag.
Tell each agent which skill to use, which lead cards it owns, and what shape to return. Without agents, run the play in the order written.
Run log
Open it at the start, close it at the end.
# Run log — [date]
Pastel: connected | not connected · Autopilot: on | off · Aim: [one line]
| Stage | Leads | Waiting on |
|---|---|---|
| Caught | | |
| Fit | | |
| Researched | | |
| Ranked ≥ threshold | | |
| Drafted | | |
| Waiting on you | | |
| Scheduled | | |
| Replied | | |
| Ready for a call | | |
| Booked | | |Close with the three next moves and the skills that ran.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

