agent-usage-optimizer-step-5-work-queue-integration
Sub-skill of agent-usage-optimizer: Step 5 — Work Queue Integration.
Best use case
agent-usage-optimizer-step-5-work-queue-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of agent-usage-optimizer: Step 5 — Work Queue Integration.
Teams using agent-usage-optimizer-step-5-work-queue-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/step-5-work-queue-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-usage-optimizer-step-5-work-queue-integration Compares
| Feature / Agent | agent-usage-optimizer-step-5-work-queue-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of agent-usage-optimizer: Step 5 — Work Queue Integration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Step 5 — Work Queue Integration ## Step 5 — Work Queue Integration When showing recommendations before the plan gate in `/work run`: ``` === Agent Allocation Check === Cache age: 12m | Codex: 73% | Codex: 100% | Gemini: 100% Next 3 queue items: WRK-301 [Route B] → Codex Sonnet (primary), Codex (secondary) WRK-302 [Route A] → Codex (primary), Codex Haiku (secondary) WRK-303 [Route C] → Codex Opus (primary), Codex Sonnet (secondary) No providers critical. Proceeding to plan gate. ============================== ``` If any provider is critical (< 20%), show: ``` === Agent Allocation Check === [CRITICAL] Codex quota at 14% — Routes B and C rerouted. WRK-301 [Route B] → Codex (primary), Gemini (secondary) [rerouted] WRK-302 [Route A] → Codex (primary), Codex Haiku (sec) WRK-303 [Route C] → Gemini (primary), Codex (secondary) [rerouted] Approve rerouted allocation? (y/n) ============================== ```
Related Skills
agent-os-framework
Generate standardized .agent-os directory structure with product documentation, mission, tech-stack, roadmap, and decision records. Enables AI-native workflows.
solidworks-to-blender-pipeline
Use when converting SolidWorks .sldprt/.sldasm geometry to Blender for rendering, animation, or visualization, including questions about STEP export settings, FreeCAD as a bridge, or which mesh format (STL/OBJ/GLTF) to choose.
library-evaluation-integration
Create evaluation scripts and integration tests for Python scientific libraries in the digitalmodel package. Follows the established pattern from fluids, ht, meshio, sectionproperties, and pygmt evaluations.
digitalmodel-worktree-test-execution-with-shared-venv
Run digitalmodel tests from isolated worktrees without uv editable-dependency failures by using the main repo's existing virtualenv and PYTHONPATH.
digitalmodel-orcawave-orcaflex-proof-workflows
Class-level digitalmodel OrcaWave/OrcaFlex readiness, semantic-proof, fixture-proof, and closeout workflows.
blender-worktree-test-hardening
Recover and harden digitalmodel Blender automation work in isolated worktrees when uv/editable dependency paths break and local machines lack a Blender executable.
worktree-pre-push-bypass-for-tier1-checks
Handle workspace-hub integration-branch pushes from isolated git worktrees when the pre-push hook incorrectly assumes sibling tier-1 repos exist under the worktree path.
worktree-branch-sync-hygiene
Class-level branch, worktree, dirty-main, stash, sync, and hook hygiene for workspace-hub style multi-repo work.
workspace-knowledge-doc-contracts
Class-level workspace knowledge, LLM-wiki, repo mission contracts, stale doc references, semantic taxonomy, and knowledge-source reconnaissance.
workspace-hub-overnight-plan-monitor
Monitor and reconcile workspace-hub overnight planning or implementation batches, including process status, result artifacts, issue/commit verification, and controlled failed-lane recovery.
verify-Codex-run-commit-vs-working-tree-before-closing
After a Codex implementation run, verify the claimed file set against the actual commit and working tree before treating the issue as fully complete.
work-around-merge-conflicts-in-test-execution
Run tests when repo has unresolved merge conflicts in config files by bypassing broken configs and executing tests directly