Credentials. Publishing sends app code to your Twenty workspace, so give the agent access only to a workspace you control and review what it publishes.
Who it is forA developer who already uses a coding agent and wants it to build CRM extensions for their Twenty workspace.
The problemA coding agent does not know Twenty's app conventions, so its output may not match the SDK or publish flow.
The outcomeThe agent works from the official Twenty app skills to scaffold and publish a CRM app to your workspace.
What you need first
- A computer with Node.js and npm, since the README uses npx commands (inferred)
- A Twenty workspace to publish to, from twenty.com or a self-hosted instance
- Docker, if you plan to self-host with Docker Compose
Steps
- Run
npx skills add https://github.com/twentyhq/twenty/tree/agent-skills --listto see the available skills. - If that branch does not exist yet, follow the local build instructions in packages/twenty-agent-skills before continuing.
- Install the listed skills into your agent following the skills CLI output. (inferred, check the README)
- Read SKILLS.md in the repo to choose the skill family that fits your task.
- Ask your agent to scaffold an app and publish it with the Twenty CLI, then review the code it wrote before publishing.
Prompt for your agent
Install the Twenty app skills from https://github.com/twentyhq/twenty/tree/agent-skills by running `npx skills add https://github.com/twentyhq/twenty/tree/agent-skills --list` and report the skills it lists. Then use them to scaffold an app named <app-name> for <use-case>. Verify that the generated objects follow the defineObject pattern shown in the README.
Caveat. The agent-skills branch is only created by the first successful publish from main, so until then you must use the local build instructions in the repo.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer