CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-app

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

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A strong, disciplined single-purpose skill: copy-paste-ready commands, an explicit pre-flight confirmation step, deliberate scope boundaries (do not re-validate after scaffolding), and clean outward references. The only real improvement is consolidating the Docker-fallback rule, which is repeated across three sections.

Suggestions

State the Docker-fallback decision rule once (in "Choose A Twenty Instance") and have later sections reference it instead of restating it.

Consider adding a one-line post-scaffold sanity check (e.g. confirming the OAuth remote was stored in ~/.twenty/config.json) before declaring the job done.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with no concept padding, but the Docker-fallback rule is stated three times ("Choose A Twenty Instance", "Scaffolding", and "Docker Fallback Troubleshooting") — minor over-explanation that could be trimmed, which fits the efficient-with-minor-trims anchor rather than the 'could be tightened' 3 anchor.

4 / 5

Actionability

It provides three copy-paste-ready command variants (`npx create-twenty-app@latest <app-name> --url <twenty-instance-url>`, the Docker fallback, and the --name/--display-name/--description pass-through), the exact supported option list, a name-normalization rule, and a concrete Docker download URL — fully executable and covering the common cases.

5 / 5

Workflow Clarity

The sequence (explain instance need → choose instance → repeat back purpose/shape → scaffold → report and stop) is clear, with an explicit pre-scaffold confirmation checkpoint ("Scaffolding is one-way — confirming here avoids re-scaffolds later") and a Docker-failure recovery loop; the happy path deliberately omits post-scaffold verification, a minor checkpoint gap that keeps it below 5.

4 / 5

Progressive Disclosure

A single-purpose, well-sectioned overview that delegates background and cross-skill rules to clearly signaled one-level-deep references ("read ../../references/concepts/how-apps-work.md", "operating-rules.md... they are authoritative and not restated per skill", "Use ../../references/design/front-component-ui.md") instead of inlining them — easy navigation with no nested references.

5 / 5

Total

18

/

20

Passed

Description

71%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 concise, explicit, and safe: it has a clear 'Use when' trigger with a concrete action and domain. Its main weakness is thin keyword coverage — it omits the natural trigger variations (start, set up, bootstrap, plugin/extension) that the body enumerates, which would improve both trigger quality and specificity.

Suggestions

Add 2-3 natural trigger synonyms to the description, e.g. "Use when the user wants to create, scaffold, or bootstrap a new Twenty app, plugin, or extension".

Briefly enumerate the concrete capabilities (choose/authenticate a Twenty instance, scaffold the project, initial sync) so the 'what' goes beyond a single action.

DimensionReasoningScore

Specificity

"create or scaffold a new Twenty app" names the domain plus 1-2 concrete actions, matching the anchor for a non-comprehensive action list; it does not list several specific actions (instance setup, naming, flags, post-scaffold steps), which keeps it below 4.

3 / 5

Completeness

It explicitly answers both: what ("create or scaffold a new Twenty app") and when ("Use when the user wants to create or scaffold a new Twenty app") with a concrete trigger phrase, matching the anchor that requires both what AND when explicitly; the 'when' clause is fully explicit, so it is not the 4 anchor where 'when' could be more specific.

5 / 5

Trigger Term Quality

"create", "scaffold", and "new Twenty app" are natural trigger terms, but common variations users would say ("start", "set up", "bootstrap", "scaffold a plugin/extension") are missing, which the body itself lists as representative triggers — some relevant keywords, missing variations.

3 / 5

Distinctiveness Conflict Risk

"Twenty app" is a clear niche and "new" separates it from sibling skills (develop-app, manage-app, publish-app), but those closely related skills create minor overlap risk — mostly distinct with minor overlap, not the minimal-conflict 5 anchor.

4 / 5

Total

15

/

20

Passed

Validation

100%

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-agent-skills/skills/create-app/SKILL.md

Reviewed

Table of Contents

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.