When To Use

Pick this skill when the user wants to operate, troubleshoot, or ship an existing Twenty app, anything between "I have an app" and "it runs in production". Representative triggers:

• "sync my app changes to the server"
• "deploy my Twenty app to production"
• "check the logs for my logic function"
• "switch to a different Twenty remote / instance"
• "add a new remote for staging"
• "set up CI/CD for my Twenty app"
• "troubleshoot a failed deploy / sync / build"
• "uninstall my app from production"
• "run tests for my Twenty app"
• "run my logic function manually for testing"

Do not use this skill to scaffold (use create-app), to change app entities or code (use develop-app), to prepare marketplace assets (use publish-app), or to query workspace records (use use-twenty-mcp).

Boundaries

For background on how Twenty apps work, the SDK packages, remotes, sync lifecycle, and rendering model, read ../../references/concepts/how-apps-work.md. Cross-skill operating rules that apply to every Twenty app task are in ../../references/concepts/operating-rules.md; they are authoritative and not restated per skill.

Do not scaffold a new app here. Use $create-app when the app does not exist.

Do not add or modify app entities here. Use $develop-app for objects, fields, logic functions, roles, views, navigation, page layouts, skills, agents, connection providers, front component registration, and settings menu items.

Do not prepare marketplace README, screenshots, logos, or npm listing copy here. Use $publish-app for public listing work.

Do not retrieve CRM records here. Use $use-twenty-mcp for workspace data retrieval.

Operating Rules

First confirm the current directory is a Twenty app:

test -f package.json
test -f src/application-config.ts

Inspect current app and scripts before running operational commands:

sed -n '1,220p' package.json
twenty remote list