Improve Queue
Run the guided, end-to-end loop that makes one Duvo Queue — and the producer→consumer workflow around it — better. Use when the user wants to "improve this Queue", "this Queue keeps backing up, fix it", or take a Queue to a concrete, applied improvement — not just a read-only audit. You drive the conversation: pin the Queue, survey its whole shape (producers and consumers, backlog and case state, both Agents' AOPs at the seam, triggers and concurrency, the Runs flowing through), agree what to base the improvement on (the user's feedback or the evidence in the Runs/backlog), propose a Run/case
Install
/plugin marketplace add duvoai/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add duvoai/skills --skill improve-queuegit clone --depth 1 https://github.com/duvoai/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/improve-queue ~/.claude/skills/improve-queuePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Improve a Queue ## What this skill is This is the **guided improvement loop** for a Queue and the workflow around it: the conversational shell that takes the user from "this Queue could work better" to a change that is actually applied. A Queue is rarely improved alone — it sits between a **producer** that pushes cases in and a **consumer** triggered to work them, and most of what makes it slow, inconsistent, or backed-up lives in that structure and in the AOPs at the seam between the two Agents. You own the loop and the judgement calls — _which_ Queue, _what to base the improvement on_, _which Runs and cases to look at_, _what to change_, _whether to apply it_. You do **not** re-derive the analysis or the AOP rewrites yourself: `workflow-debugger` already knows how to audit a producer→consumer workflow from its topology, backlog, and the AOPs at the seam, and `aop-writer` already knows how to rewrite an AOP. You orchestrate them. The value you add over running `workflow-debugger` directly is the loop around it: pinning the Queue, surveying its full shape, getting the user to choose the basis, proposing and confirming a range, and closing the loop by applying what they accept. ## Where this sits among the skills - **`workflow-debugger`** — the read-only audit of a Queue workflow: topology and `problems`, the backlog, both producer and consumer AOPs, and a sample of Runs. You call it for the analysis in step 5; you don't reproduce its taxonomy here.
Details
- Skill name
improve-queue- Repository
- duvoai/skills
- Path
skills/improve-queue/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Improve Queue skill do?
Run the guided, end-to-end loop that makes one Duvo Queue — and the producer→consumer workflow around it — better. Use when the user wants to "improve this Queue", "this Queue keeps backing up, fix it", or take a Queue to a concrete, applied improvement — not just a read-only audit. You drive the conversation: pin the Queue, survey its whole shape (producers and consumers, backlog and case state, both Agents' AOPs at the seam, triggers and concurrency, the Runs flowing through), agree what to base the improvement on (the user's feedback or the evidence in the Runs/backlog), propose a Run/case
How do I install the Improve Queue skill?
Claude Code plugin: /plugin marketplace add duvoai/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Improve Queue popular?
It lives in duvoai/skills, which has 9 GitHub stars and 4 forks.
Related skills
Aop Writer
9duvoai/skills
Draft, rewrite, or critique a Duvo Agent AOP. Use when the user wants to improve an existing AOP or write a new one from a brief. Returns the AOP as a single complete markdown document in the canonical GOAL / STEPS / NOTES shape.
Clarity Mapping
9duvoai/skills
Map how a process works with Duvo Clarity. Use when the user asks to map, document or understand how their team does a piece of work, to interview people about a process, or to analyze what those interviews found. Sets up a Duvo workspace if the user has none, creates the process, invites people to short voice interviews within the plan's allowance, tracks who has done theirs, and analyzes the process map.
Code Step Author
9duvoai/skills
Answer questions about writing the Python program of a Duvo code step and the `duvo` SDK it calls. Use when the user asks how a code step reads its case, claims or settles work on a Queue, reaches a Connection, reads Policy values or attached files, what `duvo.execution` holds, which errors the SDK raises, or wants a snippet for a code step. Grounds every answer in the SDK surface that actually ships into the sandbox, and hands the writing of the program itself to the step's own AI generation rather than pasting code the user must transcribe.
Orby
9prismatic-io/agent-skills
Explore, operate, and troubleshoot Prismatic environments. Use when a user asks about their Prismatic organization, customers, integrations, instances, executions, logs, deployment, configuration, documentation, GraphQL API, or an end-to-end outcome involving the Prismatic platform.
Benchmark Fileops
9claudekit/skillmark
Execute 21-step file operations workflow for benchmarking prompt adherence. Use for Skills vs Commands comparison testing.
API Test Executor
101ikeadragon/awesome-offsec-claude
Execute a predefined API test plan deterministically with complete request-level evidence and final verdicts.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.