publish-app

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, actionable overview that delegates detail to references and includes a validation checkpoint before publishing. Its main gaps are the lack of an explicit error-recovery feedback loop and references that point outside the skill bundle rather than to bundled files.

Suggestions

Add an explicit validate->fix->retry loop: after `yarn twenty dev:build`, state that on failure Claude should fix the reported issues and re-run before publishing.

Move or copy the referenced detail files into the skill's own `references/` directory (e.g. `references/publish-app/prepare-for-app-store.md`) so the paths resolve within the bundle and are easier to discover.

For the `defineApplication` field verification step, show a minimal code snippet of the expected field shape so the guidance is copy-paste ready rather than inspection-only.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: it assumes Claude knows the domain, offloads background to references, and presents a tight checklist with no padding or basic-concept explanation; every line earns its place.	5 / 5
Actionability	Concrete commands ('yarn twenty dev:build', 'yarn twenty app:publish --tag <tag>'), named files, and an explicit field list give mostly executable guidance, though several steps are inspection/verification instructions rather than copy-paste code.	4 / 5
Workflow Clarity	A clear sequence runs inspect -> verify metadata -> validate with dev:build -> publish, with a validation checkpoint before the irreversible publish step; it lacks an explicit validate->fix->retry feedback loop, keeping it just below the top anchor.	4 / 5
Progressive Disclosure	Well-organized sections (When To Use, Publishing Checklist, Boundaries, Docs) with clearly signaled one-level-deep references, but the referenced paths ('../../references/...') do not resolve within the skill's own bundle (no local references/ directory), a minor organization/discoverability gap.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed: it pairs a concrete 'what' with an explicit 'Use when' trigger, names a distinctive niche, and lists specific artifacts. Its only weakness is slightly limited action verb diversity and a few missing natural synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates concrete artifacts ('README/About copy, package metadata, defineApplication marketplace metadata, logos, screenshots, and public assets'), but the action verbs are limited to 'prepare or verify', leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ('prepare or verify a Twenty app for npm or marketplace publication, including ...') and when ('Use when the user wants to prepare or verify ...'), matching the concrete-trigger-phrases anchor exactly.	5 / 5
Trigger Term Quality	Strong natural keywords ('publish', 'npm', 'marketplace', 'logos', 'screenshots') with a synonym pair ('publication'/'publish'), though common variations like 'listing' or 'branding' are absent, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Twenty app npm/marketplace publication) with distinct triggers and minimal conflict risk; the body further separates it from scaffold/develop/manage skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: twentyhq/twenty
Path: packages/twenty-codex-plugin/skills/publish-app/SKILL.md
Commit: cbd58da

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.