# Quota Array Dispatch

Load when a crew-dispatch rule or default resolves to more than one profile candidate.

- Repository: https://github.com/kunchenguid/firstmate (8480 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kunchenguid/firstmate --skill quota-array-dispatch -g -a claude-code -y`
Codex: `npx skills add kunchenguid/firstmate --skill quota-array-dispatch -g -a codex -y`
Cursor: `npx skills add kunchenguid/firstmate --skill quota-array-dispatch -g -a cursor -y`
Gemini CLI: `npx skills add kunchenguid/firstmate --skill quota-array-dispatch -g -a gemini-cli -y`

## Description

Load when a crew-dispatch rule or default resolves to more than one profile candidate.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# quota-array-dispatch

This skill is the single owner of the completion-aware profile-array selection procedure.
`AGENTS.md` section 4 owns the always-loaded intake boundary, load trigger, malformed-config refusal, every-candidate accounting, and strongest-reasoning/tie safety rules.
`harness-adapters` owns harness verification, model/provider discovery, and effort fallback.
`quota-axi` remains data-only: it publishes `spendPriority` as a comparable scalar and never recommends, selects, ranks, or infers a route.
Do not add a daemon, opaque composite score, routing wrapper, hard-coded model-specific policy, or producer-side route recommendation.
The [worker helper](../../../bin/fm-quota-choose.sh) and [typed resolver](../../../docs/configuration.md#typed-dispatch-resolution-env-fm_dispatch_provider-fm_dispatch_model) own their deterministic mapping boundaries.

## Shared-quota opt-out

When the home's `config/crew-dispatch.json` declares a top-level `"shared_quota": true`, this home draws every provider's usage from one single shared budget, so per-provider quota rows do not describe what is left, and this skill's quota snapshot, the quota parts of the eligibility and runway gates, and `spendPriority` ranking are off by home declaration.
Make no `quota-axi` call, apply no quota row, quota floor, runway gate, or `spendPriority` rank, and choose the matched rule's first declared profile that its authoritative catalog supports and that meets the required reasoning class; catalog eligibility and reasoning-class fit still apply.
`preferred_provider` is not a quota signal, so it still applies: `preferred_provider` still narrows the pool; declared order then picks within it.
Account for every candidate as always, stating in place of quota evidence that quota ranking is off by home declaration.
The declared value must be a boolean; anything else is an actionable configuration error.

## Worker-side quota helper

The rest: https://github.com/kunchenguid/firstmate/blob/HEAD/.agents/skills/quota-array-dispatch/SKILL.md