agent-crm: Skill for Claude Code

Orient yourself first

npm run crm -- app inspect --json

Read valid, then problems[], then limitations[], in that order. Every problem is fixed or reported before anything is built on top of it, and every limitation is a hard boundary on what you may claim. Then read packages[], capabilities[], resources[], actions[], policies[] and providers[]: that list is what exists. A capability absent from the report does not exist, whatever a record name, a label or a document suggests.

If the repository documents this skill names are absent, you are in a project built from this framework rather than in the framework itself. The inspection report is then the source of truth and those documents are optional background — do not guess at their contents, and do not assume a path exists because this skill names it.

providers[] reports declared metadata and the keys of a declared config, never a value. It is never evidence that a signature provider is credentialed, reachable or legally qualified — PROVIDER_HEALTH_UNKNOWN and SECRETS_NOT_INSPECTED are in limitations[] for exactly that reason.

Background, where they exist: ARCHITECTURE.md, DECISIONS.md (ADR-016 and ADR-017) and docs/SIGNATURE_ORDER.md. They are the deeper source for the rules below, not a prerequisite for them — the rules stand on their own.

Sequence an external side effect

1. Never call a provider inside a database transaction, and never claim atomicity between the local database and a remote service. Declare the bounded external-operation shape instead: externalOperation: 1 with intent (transaction A), external (no transaction, bounded timeout), finalize (transaction B) and compensate (its own transaction, only on failure).
2. The external phase gets frozen JSON-safe data plus the provider registry — no database, no modules, no managed writes. If you find yourself wanting a service handle there, the work belongs in intent or finalize.
3. Give every external call a deterministic idempotency key derived from the record it belongs to (here: env:quote-version:<id>, which is also the DB-unique source key). A repeated request must be refused, not retried into a second remote object.
4. On failure, move to a recoverable local state and record the phase and code. The single policy is: never silently retry, always reconcile.
5. A provider answer that is already terminal is a completion, not a status: route every provider state through the one path that creates the artifact and the order, and prefetch what that needs in external. Persisting a terminal state without its evidence is unrecoverable.
6. An idempotency key is a lookup, not an identity: before adopting a provider envelope, check the document hash, the signer set and any known provider envelope id, and fail closed on a mismatch.
7. Do not build a scheduler, an outbox or a workflow DSL.