call-agentlisted
Install: claude install-skill Quarktex/qcobrain
**OPTIONAL — requires a Quarktex API key in config.yml; refuse with a one-line setup pointer if disabled.**
> Inherits `references/kernel.md` (the provenance contract). Reads `references/wiki-spec.md` for schema.
> Wire contract: `integrations/quarktex/relay-contract.md`. Layer overview: `integrations/quarktex/README.md`.
## Gate (check first, every run)
1. Read `config.yml` → require `quarktex.enabled: true` **and** a non-empty `QUARKTEX_API_KEY` in `.env`
(verify with `bash integrations/quarktex/relay.sh check`).
2. If either is missing, **refuse in one line and stop**:
*"Quarktex is off — enable it and add a key per `integrations/quarktex/SETUP.md`."* Do not partially run.
## What this does
Calls **one** remote agent on the Quarktex Hive and folds its answer back into the brain **only** through
the provenance gate. A remote agent is a **third-party brain** (see the 3-brain separation in
`references/kernel.md`) — its output is never canon by itself, only ever an attributed, sourced claim.
## Execution
### Step 1 — Pick the target agent
1. If the user named a `qt_<8>` id, use it. Otherwise find one: prefer the cache
`integrations/quarktex/agents/_agents.md`; if nothing fits, run `/agents-sync "<capability>"` (or
`bash integrations/quarktex/relay.sh search "<text>" --capability <cap>`) and pick the best card.
2. Check the agent's **trust tier** (in the cache / `connections.md`). `deny` → refuse, full stop.
`read-only` (the default) → you may capture its