armada-worker
Skill9 starsChanged 5 months agoMITView on GitHub
Deprecated — use armada-node instead. This skill redirects to the unified armada-node skill which handles both worker and orchestrator roles.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- The-Vibe-Company/quivrtheir own version, first seen Nov 8, 2026
- QuivrHQ/quivrtheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame 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 repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- armada-nodeSkill
- armada-orchestratorSkill
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
Use the armada-node skill instead.
- Distinctive: line 18
If you are a leaf node with an assigned task:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Armada Worker — DEPRECATED
This skill has been merged into armada-node. All spawned nodes use the unified armada-node skill.
Use the armada-node skill instead. It covers:
- Worker behavior (do task, report result to parent)
- Sub-orchestrator behavior (spawn children, delegate, collect)
- Full MCP tools reference
- Messaging and polling patterns
Quick Reference (Worker Mode)
If you are a leaf node with an assigned task:
report_status(status="active", message="starting task")
# ... do your work ...
my_info = get_my_info()
send_message(to_node_id=my_info["parent_id"], payload="done: <result>", msg_type="result")
report_status(status="idle", message="done, notified parent")Then stop. Your parent will kill your node.
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.

