create-app

Use when the user wants to create or scaffold a new Twenty app

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/twenty-codex-plugin/skills/create-app/SKILL.md

Quality

Content

78%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 highly actionable with clean executable scaffolding commands and a clear workflow, but progressive disclosure is weakened by references to files that are not present in the bundle and some inlined conceptual material.

Suggestions

Verify the referenced paths (../../references/concepts/how-apps-work.md and references/design/front-component-ui.md) exist in the bundle, or move the explanation of how Twenty apps work into a real referenced file.

Trim the enumerated "The scaffolder handles everything: ..." list to reduce token overhead.

Make the pre-scaffold validation checkpoint more explicit by framing the purpose-confirmation step as a required gating check rather than a soft recommendation.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, with only minor instances of over-explanation such as the enumerated "The scaffolder handles everything: ..." list that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready bash commands with flags, an explicit options list, and concrete examples covering the common existing-instance and Docker-fallback cases.	5 / 5
Workflow Clarity	The sequence (choose instance -> confirm purpose -> scaffold -> stop) is clear with a confirmation checkpoint before the one-way scaffold and error-recovery guidance for the Docker fallback, but validation checkpoints are mostly implicit rather than fully explicit.	4 / 5
Progressive Disclosure	Sections are organized and reference paths are signaled, but the referenced files (../../references/concepts/how-apps-work.md, references/design/front-component-ui.md) do not exist in the bundle, and a fair amount of conceptual content is inlined rather than split out.	3 / 5
	Total	16 / 20 Passed

Description

62%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 clearly answers both what and when and is well-scoped to Twenty app creation, but it is sparse on concrete action enumeration and trigger synonyms, leaving it slightly above the midpoint rather than comprehensive.

Suggestions

List one or two more concrete actions (e.g., "bootstrap", "scaffold, configure, and sync") to raise specificity beyond the single create/scaffold action.

Add natural trigger synonyms such as "bootstrap", "set up", or "initialize a Twenty app/project" to broaden keyword coverage.

Optionally append a short trigger-clause tail naming what not to use it for (existing apps) to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase "create or scaffold a new Twenty app" names the domain and one to two concrete actions but is not comprehensive, matching the anchor for naming a domain with minimal actions.	3 / 5
Completeness	It states both what it does ("create or scaffold a new Twenty app") and when to use it ("Use when the user wants to..."), with the "when" reasonably explicit but not fully enumerated with concrete trigger phrases.	4 / 5
Trigger Term Quality	"create" and "scaffold" are natural terms a user might say, but the description field itself lacks common variations and synonyms, leaving it with some relevant keywords rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	Scoping to "Twenty app" creation gives it a clear niche with minimal conflict risk, though there is minor overlap with sibling skills like develop-app for related Twenty work.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: twentyhq/twenty
Path: packages/twenty-codex-plugin/skills/create-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.