Twenty CRM

Reusable across any Twenty deployment. The skill drives ocli — a CLI generated from your workspace's OpenAPI spec. Per-instance state is an ocli profile under ~/.ocli/; the skill keeps only a one-line pointer in ~/.config/twenty-cli/config.json. Nothing is hardcoded.

Step 0: preflight (always)

node scripts/twenty.mjs preflight

• STATUS=ready → proceed. Output also gives PROFILE=<name> (the ocli profile, usually twenty), URL=<base-url> (use it to build UI links), and METADATA=<name> if the metadata profile was set up.
• non-zero exit → not configured. Stderr prints the two things setup needs (URL, API key) and the two setup paths below; pick by context. For the full walkthrough load references/setup-guide.md.

not_ready is not sticky. Setup happens in the user's own terminal, so a config that didn't exist this turn may exist the next. If you reported not_ready and the user comes back with any CRM request, re-run preflight first — don't repeat the "not configured" message from memory.

Setup

Idempotent — re-running updates the existing profile. New here? references/setup-guide.md has the full step-by-step (where the URL comes from, how to create the API key).