trellis-readiness-check

name	trellis-readiness-check
description	Diagnose what is missing before a Trellis Cloudflare app can boot, deploy, or verify live.

Trellis Readiness Check

Use this skill when the user wants to know what is missing before Trellis can run.

Required Commands

Prefer JSON:

npm run doctor -- --json
npm run verify -- --json

If the user is not in a generated app but has the CLI script:

npm run trellis -- doctor --json
npm run trellis -- verify cloudflare --json

Classify Blockers

Group blockers into:

• Cloudflare auth blockers
• scaffold shape blockers
• D1 binding or schema blockers
• binding blockers
• local smoke blockers
• pack sync blockers
• deploy blockers
• live route blockers
• optional provider blockers

Do not dump the full environment matrix unless the user asks for it.

Default First Proof

The fastest proof is:

nvm use 22
npm install
npm run cf:login
npm run doctor -- --json
npm run smoke -- --json
npm run verify -- --json

Success means:

• the Cloudflare scaffold shape is valid
• wrangler.jsonc has the expected bindings
• local smoke runs through the safe fixture
• pack sync has a valid R2 plan
• D1/R2/Queue/Workflow posture can be resolved or provisioned

That does not prove:

• deployed Worker health
• live MCP auth
• live safe signal ingest
• provider credentials
• outbound send safety

Live Proof

After deploy:

npm run verify -- --live --url "$APP_URL" --api-key "$TRELLIS_API_KEY"

Only run a live agent exercise when the user accepts that it may use one model call:

npm run verify -- --live --url "$APP_URL" --api-key "$TRELLIS_API_KEY" --exercise-agent

For Attio provider smoke:

npm run verify -- --live --url "$APP_URL" --attio-smoke --provider-smoke-token "$TRELLIS_PROVIDER_SMOKE_TOKEN"

Common Blocker Messages

Use precise next-step language:

• Blocked: run npm run cf:login or set CLOUDFLARE_ACCOUNT_ID and CLOUDFLARE_API_TOKEN
• Blocked: TRELLIS_DB binding is missing from wrangler.jsonc
• Blocked: TRELLIS_PACKS bucket_name is missing from wrangler.jsonc
• Blocked: PROSPECT_WORKFLOW binding is missing from wrangler.jsonc
• Blocked: set TRELLIS_API_KEY as a Worker secret before protected remote checks
• Next: run npm run deploy -- --json so Trellis can provision D1, R2, Queues, Workflows, and sync packs
• Next: use trellis-setup-database to inspect D1 schema, trace rows, approvals, and seeded demo data
• Later: connect FIRECRAWL_API_KEY after the Cloudflare app is alive

Novice Rule

Only tell the user the next missing step. Do not switch them into provider setup until doctor, smoke, deploy, and Cloudflare verification are green enough to trust.

Agent Shape Checks

When the readiness problem is about app behavior rather than infrastructure, route to trellis-build-agent and inspect:

• src/agent.ts imports trellis and schema from @trellis/gtm.
• src/agent.ts keeps trellis.safeOutbound() unless the user explicitly changed safety.
• mcp.surface is role-shaped when appropriate, such as sdr.
• mcp.operator.name is present when an operator MCP should exist.
• mcp.tools.skillTools maps bounded tool names to real skill directory names.
• src/state/*.map.ts uses trellis.state(...) instead of hand-authored D1 migrations.
• each skills/**/SKILL.md has purpose, inputs, method, output contract, and safety sections.