Menu
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.
Use when turning a qualified Twenty lead — a call-summary brief plus any client braindump/docs — into a partner brief a partner can scope and quote from. Trigger when pointed at a lead folder (e.g. partners-experience/<LEAD>/) and asked to "draft a design doc", "create a partner brief", "translate this into Twenty terms", "scope this for a partner", or "prep the partner handoff". Default output is zero-inference (only what the client said; empty sections get a placeholder). Pass --full for inference mode. Chains after twenty-lead-intro-call-summary.
Match a qualified lead to Twenty partners and generate all intro emails in one run. Use when a lead folder exists and you need to find the right implementation partner, either after running twenty-partner-design-doc or standalone when partner-match-criteria.md is already present. Chains back into twenty-lead-intro-call-summary and twenty-partner-design-doc if the criteria file is missing.
Retrieve and present Twenty CRM records as readable summaries or tables, using the connected Twenty MCP server to discover fields, fetch relevant data, format dates and values, build record links, and avoid raw API output.
Use when the user wants to create or scaffold a new Twenty app
Use when the user wants to add or modify Twenty app entities, including objects, layouts, logic functions, and front components inside an existing Twenty app.
Use when the user wants to manage or troubleshoot tooling, remotes, sync, build, deploy, logs, CI/CD, or operational workflows for an existing Twenty app.
| name | publish-app |
| description | 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. |
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.
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, logoUrl, screenshots, aboutDescription, websiteUrl, termsUrl, emailSupport, and issueReportUrl.logoUrl and screenshots 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.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 through the bundled twenty-docs MCP server before guessing.