publish-app

Prepares Twenty app listings with README copy, marketplace metadata, logos, and screenshots for npm publication.

56.0k|8.9k|Updated Dec 1, 2022
One-click install
npx skills add https://github.com/twentyhq/twenty --skill publish-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-app
Source: https://github.com/twentyhq/twenty/tree/main/packages/twenty-codex-plugin/skills/publish-app
Command: npx skills add https://github.com/twentyhq/twenty --skill publish-app

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Publishing a Twenty app to npm or the marketplace requires consistent README copy, correct package metadata, marketplace fields in defineApplication, and public assets like logos and screenshots, which is easy to get wrong or leave incomplete.

Core Features & Use Cases

  • Listing Preparation: Reviews package.json, README.md, src/application-config.ts, and public/ to verify version bumps, the twenty-app keyword, and marketplace-facing fields such as displayName, description, author, category, logoUrl, and screenshots.
  • Asset & Safety Checks: Ensures logoUrl and screenshots point to files in public/ and that public assets contain no secrets, tokens, customer records, or confidential material.
  • Publication Workflow: Validates the app with yarn twenty dev:build and publishes via yarn twenty app:publish, optionally with a release tag.
  • Use Case: Before shipping a new version of your Twenty app, ask the assistant to review your listing so the marketplace About page, branding, and metadata are complete and accurate.

Quick Start

Use the publish-app skill to review my Twenty app's README, marketplace metadata, and public assets, then prepare it for npm publication.

Frequently Asked Questions about publish-app

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

FAQPage Schema
How do I publish a Twenty app to npm or the marketplace?

Ensure package.json has a bumped version and the twenty-app keyword, complete the defineApplication marketplace fields, then validate with yarn twenty dev:build and publish using yarn twenty app:publish or with a --tag flag.

What marketplace metadata does defineApplication need for a Twenty app listing?

Key fields include displayName, description, author, category, logoUrl, screenshots, aboutDescription, websiteUrl, termsUrl, emailSupport, and issueReportUrl. If aboutDescription is omitted, the marketplace falls back to the package README.md from npm.

Where should logos and screenshots for a Twenty app listing be stored?

Point logoUrl and screenshots at files inside the app's public/ directory. Public assets must not contain secrets, private data, customer records, real tokens, or unreleased confidential material.

When should I not use the publish-app skill?

Use create-app to scaffold a new app, develop-app to change app entities, manage-app for remotes and deploys to a specific server, and use-twenty-mcp to query workspace records. publish-app only covers listing and publication preparation.

How do I validate a Twenty app before publishing?

Run yarn twenty dev:build to validate the app before publication. If the build succeeds, publish with yarn twenty app:publish, optionally appending --tag <tag> for tagged releases.