coordinate-fleet
Skill40k starsChanged 40 days agoMITView on GitHub
Coordinating the Quivr V2 agent fleet. Use when designated coordinator, or asked to launch workers on tickets, merge green pull requests, keep Linear and the demo in sync, or resume the fleet in a new (local or cloud) session.
1 other project uses a version of this.
Trending
More talk lately.thin dataabout the whole repository
Most recently taken up by
- QuivrHQ/quivrword for word, first seen Oct 8, 2026
Who's talking about The-Vibe-Company/quivr
- Kimz“39.6k Stars:把內容串流變成可監控知識庫的開源引擎”YouTube · Oct 27, 2026 · 4 views
- @golangoss.bsky.social“quivr (⭐️ 39614) An open-source engine that turns continuous content streams into search and monitoring. …”Bluesky · Oct 29, 2026 · 1 likes
- Kimerd“Turn Content Streams Into Searchable Monitored Knowledge”YouTube · Oct 27, 2026 · 1 views
- @golangoss.bsky.social“quivr (⭐️ 39585) An open-source engine that turns continuous content streams into search and monitoring. …”Bluesky · Oct 14, 2026 · 1 likes
- @golangoss.bsky.social“quivr (⭐️ 39603) An open-source engine that turns continuous content streams into search and monitoring. …”Bluesky · Oct 26, 2026
The biggest 5 of 7 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 7
Talked about on Bluesky, YouTube and the web (7 times).
On Bluesky · 3
- Oct 29, 2026quivr (⭐️ 39614) An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search,… — @golangoss.bsky.social1 likes and repost
- Oct 14, 2026quivr (⭐️ 39585) An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search,… — @golangoss.bsky.social1 likes and repost
- Oct 26, 2026quivr (⭐️ 39603) An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search,… — @golangoss.bsky.social0 likes and reposts · 1 reply
On YouTube · 2
- Oct 27, 202639.6k Stars:把內容串流變成可監控知識庫的開源引擎 — Kimz4 views
- Oct 27, 2026Turn Content Streams Into Searchable Monitored Knowledge — Kimerd1 view
On the web · 2
- Oct 30, 2026The-Vibe-Company/Quivr v2.0.1 on GitHub — newreleases.io
- Sep 19, 2023The-Vibe-Company/Quivr v0.0.76 on GitHub — newreleases.io
Other versions1 project uses a version of this.
Word for word · 1
- QuivrHQ/quivr★ 40k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- quivr-search/AGENTS.mdAGENTS.md
- sdks/AGENTS.mdAGENTS.md
- armada-coordinatorSkill
- armada-runtime-claude-codeSkill
- armada-runtime-conductorSkill
- armada-runtime-herdrSkill
- armada-workerSkill
- ask-mattSkill
- audit-tests-devSkill
- better-uiSkill
- capture-learning-toolsSkill
- codebase-designSkill
- code-reviewSkill
- design-frontend-devSkill
- diagnosing-bugsSkill
- documentation-writerSkill
- domain-modelingSkill
- emil-design-engSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- humanizerSkill
- implementSkill
- improve-codebase-architectureSkill
- mermaid-diagramsSkill
- mintlifySkill
- plan-prSkill
- prototypeSkill
- researchSkill
- resolving-merge-conflictsSkill
- review-code-devSkill
- setup-matt-pocock-skillsSkill
- ship-pr-devSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-docsSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Every finding that survives a session goes to Linear or to the repository, never only to a local note: the next coordinator may be a cloud …
- Distinctive: line 31
When the owner changes a process rule, update this skill in the same session.
≈ “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
The coordinator turns the owner's intent into merged pull requests. Workers each own one ticket; the coordinator picks what runs, answers their decisions, merges, deploys and reports. AGENTS.md and docs/agents/fleet-workflow.md define the protocol; this skill is the coordinator's practice on top of it.
Standing authority. The owner delegates reversible technical decisions, plan approval and merging to the coordinator, and does not want permission prompts: act, then report. Escalate only product decisions, irreversible or outward-facing actions, and anything that spends money.
Loop
- Read the fleet state from Linear, never from memory: the specs under
THE-531, their sub-issues, state,Agent phase/Agent runtimelabels, blocked-by relations, and the latestAgent status:comments. List open pull requests withgh pr list. Done when you can name every ticket in flight, every ticket ready to start (all blockers Done) and every pull request waiting for you. - Launch one worker per ready ticket that does not collide with work in flight. Brief each with WORKER-BRIEF.md plus a ticket paragraph: the merged blockers and their hand-back notes, the decisions you already made for it, and which parallel workers touch neighbouring code. Run workers in the background with worktree isolation (
isolation: "worktree"on the Agent tool; without it every worker edits the coordinator's checkout), on the strongest available model. When several workers build one feature (for example one UI tab), name one owner for the shared files and have it publish the shared API early. Done when every launched ticket is In Progress with a claim comment. - Answer worker questions the same turn. Decide reversible choices yourself, pick the option that keeps behaviour observable and the engine generic, and record the decision and its reason on the ticket. When two workers need the same shared resource (Plugin API minor version, migration timestamp, generated files), set the rule once and tell both.
- Merge a ready pull request with MERGE.md. Done when the PR is merged, the ticket is Done with its agent labels removed, and every in-flight worker affected by what landed has been told.
- Check what the merge changed in production-like environments: the Railway demo and the docs site deploy from
main. Follow OPERATIONS.md. Done when the deploy succeeded and a smoke check passed, or a follow-up ticket exists for what failed. - Turn findings into tickets. A gap a worker reports, a bug seen in the demo, an alias to remove later: create the ticket under the right spec with an
## In shortsection (template indocs/agents/issue-tracker.md), blocked-by relations, and launch it if it is ready. Done when no finding lives only in a chat transcript. - Report to the owner in their language, briefly: what merged, what is running, what you decided for them, and the one thing they must do (if any), with its exact place (a URL, a setting). Numbers and outcomes, no process narration.
Rules of thumb
- Merge only after the worker's hand-back; a green PR can still get one more rebased push.
- Parallel workers on one ticket area collide: stagger them, or give each a disjoint area and tell them the boundary.
- Every finding that survives a session goes to Linear or to the repository, never only to a local note: the next coordinator may be a cloud session with none of your context.
- When the owner changes a process rule, update this skill in the same session.
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.

