Index of every page on this site: llms.txt
All skills
twentyhq avatar

/publish-app

@13c9027
by Twentytwentyhq/twenty61k stars
10,139
Run it yourself

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 this Skill: https://skilld.dev/gh/twentyhq/twenty/publish-app

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈58 tokens for metadata: the name and description. ≈678 when used: this file. ≈56 more on demand in 1 file.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈233 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

When To Use

Pick this skill when the user wants to make an existing Twenty app presentable — listing copy, branding, public assets, and publication. Representative triggers:

  • "prepare my Twenty app for the marketplace"
  • "write the README for my Twenty app"
  • "publish my app to npm"
  • "add a logo / screenshots / marketplace metadata"
  • "set up defineApplication marketplace fields"
  • "review my app listing before going live"
  • "ship a new version of my published app"

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).

Publishing Checklist

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:

  • Inspect package.json, README.md, src/application-config.ts, and public/.
  • For npm marketplace publication, ensure package.json has a valid bumped version and the twenty-app keyword.
  • In defineApplication(), verify marketplace-facing fields such as displayName, description, author, category, logo, galleryImages, aboutDescription, websiteUrl, termsUrl, emailSupport, and issueReportUrl.
  • Keep logo and galleryImages pointed at files in public/. Public assets must not contain secrets, private data, customer records, real tokens, or unreleased confidential material.
  • Remember that if 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.
  • Validate with twenty app build; publish with twenty app publish or twenty app publish --tag <tag>.

Boundaries

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.

Docs

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts26d3 checks · Risk SAFE
  • Gen Agent Trust Hub26d

    The skill is designed to help users prepare and publish Twenty apps. It involves reading local project files and executing standard build/publish commands using the Twenty CLI. No security issues were detected.

  • Socket26d

    No alerts

  • Snyk26d

    Risk: LOW · No issues

Signed by skilld at 13c9027. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 16 minutes ago.

Activeupdated last month

README badge

README badge for twentyhq/twenty/publish-app