manage-app

Manages remotes, sync, build, deploy, logs, and CI/CD for Twenty apps.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/masoodtalha/twenty --skill manage-app-masoodtalha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-app
Source: https://github.com/masoodtalha/twenty/tree/main/packages/twenty-codex-plugin/skills/manage-app
Command: npx skills add https://github.com/masoodtalha/twenty --skill manage-app-masoodtalha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Operating an existing Twenty app involves many moving parts: configuring remotes, syncing changes, building, deploying, reading function logs, and wiring CI/CD. This Skill guides the AI through those operational workflows safely, with confirmation gates for production-affecting actions. ## Core Features & Use Cases - Remote Management: Add, list, and switch Twenty server remotes, including local and production targets with stored credentials. - Sync, Build & Deploy: Run one-shot syncs with yarn twenty apply, build packages, publish privately or to npm, and install or uninstall apps on target workspaces. - Troubleshooting & Logs: Diagnose failures across remote, sync, build, deploy, and runtime layers using verbose sync output and function logs, and execute logic functions manually with test payloads. - Use Case: You changed your app and want it live. Ask the AI to sync changes to the staging remote, verify with function logs, then publish and install a new version to production after confirmation. ## Quick Start Use the manage-app skill to sync my Twenty app changes to the active remote and show me the recent function logs.

Frequently Asked Questions about manage-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync my Twenty app changes to a server?▼

Run yarn twenty apply for a one-shot sync to the active remote. Avoid bare yarn twenty dev watch mode, and re-run apply each time changes need to be pushed. If authentication fails, re-add or switch the remote first.

How do I deploy a Twenty app to production?▼

Build with yarn twenty dev:build, then publish with yarn twenty app:publish --private --remote production and install with yarn twenty app:install. Ensure package.json has a strictly higher semver version than the deployed one, since re-deploying the same version is rejected.

How do I add or switch Twenty remotes?▼

Use yarn twenty remote:add interactively, --local for a local server, or --url with --api-key and --as for non-interactive setup. List remotes with yarn twenty remote:list and switch with yarn twenty remote:use <name>. Credentials are stored in ~/.twenty/config.json.

How do I debug a Twenty logic function at runtime?▼

Inspect execution with yarn twenty dev:function:logs, optionally filtered by -n <function-name>. To reproduce behavior without its trigger, run yarn twenty dev:function:exec -n <function-name> -p '<json>' with a controlled payload.

Why does my Twenty app test run fail or affect my dev server?▼

Full test suites include integration tests that install and uninstall the app on their target server. Start the isolated test instance with yarn twenty docker:start --test and run TWENTY_API_URL=http://localhost:2021 yarn test instead of using the dev instance on port 2020.

When should I not use the manage-app skill?▼

Do not use it to scaffold a new app (use create-app), modify app entities like objects or logic functions (use develop-app), prepare marketplace listings (use publish-app), or query CRM records (use use-twenty-mcp). It only covers operations on an existing app.