Starlight queen queue
Skill frankxai/starlight-automation-agent-skills/skills/starlight-queen-queue
Portable automation agent skills for the Starlight substrate — scheduling, pipelines, and fleet ops.
npx -y skills add frankxai/starlight-automation-agent-skills --skill starlight-queen-queueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Define bounded Starlight swarm queue jobs, queen/worker lanes, handoff packets, safety gates, and validation evidence for multi-agent or cross-repo work. Use when a user asks for a swarm, council, fanout, queen queue, multi-agent execution, long-running agent wave, context-preserving handoff, or Starlight automation operating model.
SKILL.md
1.5 KB, 242 tokens by cl100k_base, as published. Nobody here has run it
Starlight Queen Queue
Use a Starlight queue when one linear automation is the wrong shape and work needs bounded multi-agent execution with a synthesis owner.
Queue Job Contract
Every job needs:
- objective
- repo or workspace
- source context
- worker lanes
- allowed tools
- write scopes
- stop condition
- validation evidence
- risk gates
- handoff format
Lane Types
- Doctrine lane: decision rules, docs, memory.
- Build lane: code, repo, plugin, skill changes.
- Safety lane: secrets, private/public split, policy gates.
- Verification lane: tests, validation scripts, release checks.
- Synthesis lane: final decision and user handoff.
Safety Spine
- One coordinator owns the final risk call.
- Workers do not revert each other's changes.
- Public releases pass a private-memory and secret scan.
- Human approval is required for irreversible external actions.
- Payments and spend actions are verify-only unless the human explicitly approves.
Handoff Format
Return:
- swarm objective
- worker lanes
- context packet
- execution waves
- validation evidence
- risks
- next handoff
Gives 0 of the 12 instructions most agent orchestration skills give in 242 tokens
Counted across 742 of the 995 authors here whose files we hold, read 2026-08-06
- run the full test suite after integrating changesin 53 of 742, across 20 files
- reference existing artifacts by path or URLin 52 of 742, across 22 files
- dispatch one agent per independent problem domainin 50 of 742, across 17 files
- verify fixes do not conflictin 45 of 742, across 13 files
- include a suggested skills section in the documentin 45 of 742, across 15 files
- redact sensitive informationin 41 of 742, across 11 files
- save to the temporary directory of the operating systemin 39 of 742, across 9 files
- tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
- spot check agent changes for systematic errorsin 34 of 742, across 7 files
- write a handoff document summarising the current conversationin 31 of 742, across 6 files
- assign each agent a specific scopein 23 of 742, across 8 files
- provide specific scope and clear goalin 23 of 742, across 5 files
Said here and by no other author read
- define a queue job for bounded multi-agent execution
- assign one coordinator to own the final risk call
- require stop condition and validation evidence per job
- apply safety gates before public releases
- return handoff packets with context and validation evidence
- specify allowed tools and write scopes per job
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.