manage-app

Use when the user wants to manage or troubleshoot tooling, remotes, sync, build, deploy, logs, CI/CD, or operational workflows for an existing Twenty app.

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.

A highly actionable, well-structured operational skill body built on concrete commands and sensible validation/confirmation guardrails for destructive and production operations. Main improvement areas are mild conciseness trimming and tightening the split between inlined commands and the referenced CLI detail file.

Suggestions

Trim the inlined command catalog in sections like Remotes and Build And Deploy where the same detail is covered by ../../references/manage-app/cli-and-sync.md, keeping only the most common commands inline and deferring the rest to the reference.

Convert the Troubleshooting section's layered checklist into an explicit validate→fix→retry loop per layer to push workflow clarity toward a 5.

Consider shortening definitional lines (e.g. 'A remote is a Twenty server...') since the surrounding commands already convey the concept to a competent model.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable commands and avoids explaining concepts Claude already knows; a few definitional lines ('A remote is a Twenty server...') and some command listing that overlaps the referenced cli-and-sync.md could be trimmed slightly.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands throughout (yarn twenty remote:add/list/use, apply, dev:build, app:publish/install/uninstall, dev:function:logs/exec) covering the common operational cases with concrete flags and payloads.	5 / 5
Workflow Clarity	Clear sequencing with validation checkpoints (confirm before production actions, start the isolated test instance before integration tests, build before deploy, semver bump before redeploy) and feedback loops (re-add/switch remote on auth failure); slightly below a 5 because troubleshooting is organized as a layered checklist rather than a single explicit validate→fix→retry loop.	4 / 5
Progressive Disclosure	Well-signaled one-level-deep references to ../../references/concepts/how-apps-work.md, ../../references/manage-app/cli-and-sync.md, and ../../references/develop-app/tests.md with clear section headers; held back from 5 because substantial CLI command detail is inlined that the referenced cli-and-sync.md is meant to cover, creating mild redundancy, and the referenced paths live outside this bundle.	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.

A strong, well-scoped description that pairs an explicit 'Use when' trigger with a comprehensive list of operational domains and tight scoping to existing Twenty apps. Minor gains possible by enumerating a few more concrete verbs or user phrasings.

Dimension	Reasoning	Score
Specificity	Names the domain (Twenty app operations) and lists several concrete operational areas — 'tooling, remotes, sync, build, deploy, logs, CI/CD, or operational workflows' — but the verbs are limited to 'manage or troubleshoot', leaving minor coverage gaps versus a fully enumerated action set.	4 / 5
Completeness	Explicitly answers both what ('manage or troubleshoot tooling, remotes, sync, build, deploy, logs, CI/CD, or operational workflows') and when ('Use when the user wants to... for an existing Twenty app') with concrete trigger areas.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('deploy', 'sync', 'logs', 'build', 'CI/CD', 'remotes') with good coverage, though a few common phrasings like 'ship my app' or 'publish' are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to operational management of an existing Twenty app, a clear niche with minimal conflict risk against scaffolding, development, publishing, or data-retrieval 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/manage-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.