use-twenty-mcp

Use when the user wants Codex to connect to an existing Twenty workspace through MCP, retrieve or inspect workspace records and metadata, or present Twenty CRM data as readable Markdown with formatted dates, values, record links, and compact tables instead of raw API output.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./packages/twenty-codex-plugin/skills/use-twenty-mcp/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

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

The body is well-structured and contains a genuinely concrete Output Contract, but its quality is held back by duplicated disambiguation prose and by Setup/Retrieval sections that delegate to two reference files which are not present in the bundle. Fixing the broken references would most improve the skill.

Suggestions

Remove the duplicated create-app/develop-app distinction (present in both "When To Use" and "What It Is") to tighten conciseness.

Provide the missing bundle files references/use-twenty-mcp/setup.md and result-formatting.md, since the body's Setup and Retrieval sections depend on them but they are absent.

Inline a minimal retrieval checklist or the key formatting rules in the body so the workflow does not rely entirely on the (currently missing) external references.

Dimension	Reasoning	Score
Conciseness	The ~45-line body is mostly lean and assumes Claude's intelligence, but the create-app/develop-app disambiguation is stated twice (in "When To Use" line 19 and again in "What It Is" lines 25-26), so it could be tightened and does not reach the every-token-earns-its-place 3-anchor.	2 / 3
Actionability	The Output Contract is concrete (a real URL template "{workspaceOrigin}/object/{objectNameSingular}/{recordId}" and MUST/never rules), but the core Setup and Retrieval procedures only point to "../../references/use-twenty-mcp/setup.md" and "result-formatting.md", which do not exist, leaving the main workflow's executable guidance incomplete.	2 / 3
Workflow Clarity	A logical flow exists (When To Use → Setup → Retrieval → Output Contract) and the Output Contract supplies a verification fallback (resolve origin, never invent a host), but the retrieval step's detailed checkpoints live in a missing reference, so the sequence has gaps rather than the fully explicit validation of the 3-anchor.	2 / 3
Progressive Disclosure	Sections are well-organized and the two references are clearly signaled and one-level-deep (good structure), but both referenced files are absent from the bundle, so navigation is broken and it cannot reach the easy-navigation 3-anchor; the under-50-line exception does not apply because the skill explicitly relies on external references.	2 / 3
	Total	8 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong: it states concrete actions, opens with an explicit "Use when" trigger, covers natural user phrasings, and occupies a clear niche unlikely to conflict with other skills. It uses third-person/trigger voice with no first- or second-person penalty.

Dimension	Reasoning	Score
Specificity	It names several concrete actions — "connect to an existing Twenty workspace through MCP", "retrieve or inspect workspace records and metadata", and "present Twenty CRM data as readable Markdown with formatted dates, values, record links, and compact tables" — matching the multi-action 3-anchor rather than the domain-only 2-anchor.	3 / 3
Completeness	It explicitly answers both what (connect, retrieve/inspect, present as readable Markdown) and when ("Use when the user wants Codex to connect..."), with an explicit "Use when" clause, so it is not capped at 2 for a missing trigger.	3 / 3
Trigger Term Quality	Natural terms a user would say are well covered ("Twenty workspace", "workspace records and metadata", "Twenty CRM data", "record links"); the framing "Use when the user wants..." matches the explicit-trigger pattern, and it does not fall to 2 because the common variations are present rather than sparse.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and product-specific (Twenty CRM workspace via MCP), giving it distinct triggers unlikely to collide with generic skills, fitting the clear-niche 3-anchor rather than the overlapping 2-anchor.	3 / 3
	Total	12 / 12 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/use-twenty-mcp/SKILL.md
Commit: bb4e427

Reviewed: 6 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.