Prepare an existing Twenty app for npm or marketplace publication by reviewing its README, listing details, package metadata, logos, and screenshots. The workflow includes checking publication settings, validating the build, and running the publishing command.
Use when the user wants to prepare or verify a Twenty app for npm or marketplace publication, including README/About copy, package metadata, defineApplication marketplace metadata, logos, screenshots, and public assets.
Review the instructions the agent will receive before you install.
Pick this skill when the user wants to make an existing Twenty app presentable — listing copy, branding, public assets, and publication. Representative triggers:
defineApplication marketplace fields"Do not use this skill to scaffold (use create-app), to change app entities (use develop-app), to deploy a private build to a specific Twenty server (use manage-app), or to query workspace records (use use-twenty-mcp).
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.
Use ../../references/publish-app/prepare-for-app-store.md for detailed README, marketplace copy, logo, screenshot, and public asset guidance.
Keep the skill workflow concise:
package.json, README.md, src/application-config.ts, and public/.package.json has a valid bumped version and the twenty-app keyword.defineApplication(), verify marketplace-facing fields such as displayName, description, author, category, logo, galleryImages, aboutDescription, websiteUrl, termsUrl, emailSupport, and issueReportUrl.logo and galleryImages pointed at files in public/. Public assets must not contain secrets, private data, customer records, real tokens, or unreleased confidential material.aboutDescription is omitted, the marketplace uses the package README.md from npm for the About content. The About tab renders markdown text only: images and raw HTML are not rendered.yarn twenty dev:build; publish with yarn twenty app:publish or yarn twenty app:publish --tag <tag>.Use $manage-app for remotes, deploys to a specific server, logs, troubleshooting, and CI/CD operations.
Use $develop-app when the app entities themselves need to change before the listing can be accurate.
If the needed publishing detail is unclear, search the official Twenty docs at https://docs.twenty.com before guessing. When a Twenty docs MCP server is configured (https://docs.twenty.com/mcp), prefer searching through it. That server is an optional enhancement, not a requirement for this skill.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a new app that extends a running Twenty instance. Guide project naming and instance selection, then use the scaffolder to install dependencies, authenticate, initialize Git, and complete the initial sync and installation.
Extend an existing Twenty app with data fields, layouts, custom screens, automated logic, workflows, and permissions. The skill guides code organization, entity creation, type checking, linting, and syncing definitions to the active remote.
Operate an existing Twenty app by syncing changes, managing server connections, building and deploying releases, and inspecting function logs. It also guides troubleshooting and CI/CD, the workflows used to automate testing and deployment.
Check a Twenty pull request through real browser scenarios derived from its changes. Verify database effects and server logs alongside visible results, then produce screenshots, a structured verdict, and a report of any failures or uncertainty.
Implement validation and migration action builders for syncable entities, data types handled by Twenty's synchronization system. This skill covers required fields, uniqueness, reference checks, and orchestration wiring, with validators that return errors without throwing exceptions or changing data.
Implement caching and data conversion for syncable entities in Twenty's server code. Build lookup maps, convert stored records and inputs into flat representations, and resolve references to universal identifiers for later validation and processing.