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

81%

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

Quality

Content

71%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 content is concise and well-structured with a genuinely actionable output contract, but it leans on two reference files that are missing from the bundle, undercutting both actionability of the primary retrieval path and the progressive-disclosure structure. Supplying the referenced files would lift the two lowest dimensions.

Suggestions

Add the missing references/use-twenty-mcp/setup.md and result-formatting.md so the Setup and Retrieval instructions resolve to real files.

Remove the duplicated app-vs-workspace boundary guidance (stated in both "When To Use" and "What It Is") to tighten conciseness.

Verify the ../../references/use-twenty-mcp/ relative paths match the actual bundle layout so navigation works as written.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding of concepts Claude already knows, but the app-vs-workspace boundary is restated in both "When To Use" and "What It Is", a minor redundancy that could be trimmed.	4 / 5
Actionability	The Output Contract gives a concrete, copy-paste-ready link template and a real data shape ("recordReferences") with a clear fallback path; the main caveat is that the load-bearing instructions to read the referenced setup/formatting files cannot be followed because those files are absent.	4 / 5
Workflow Clarity	Sections are logically sequenced (Setup → Retrieval → Output Contract) for a read-only skill, and the Output Contract includes an explicit fallback checkpoint when the workspace origin cannot be resolved; no destructive/batch cap applies.	4 / 5
Progressive Disclosure	The SKILL.md is well-organized into clear sections and the references are clearly signaled by name, but the two referenced files (setup.md, result-formatting.md) do not exist in the bundle, so the navigation promise is broken—a genuine structure defect beyond a minor gap.	3 / 5
	Total	15 / 20 Passed

Description

92%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 specific, complete, and well-differentiated, clearly stating both capabilities and trigger conditions in neutral third-person voice. It would benefit only from a few more natural user phrasings to round out trigger-term quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—"connect to an existing Twenty workspace through MCP", "retrieve or inspect workspace records and metadata", and presenting data as "readable Markdown with formatted dates, values, record links, and compact tables"—giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (connect/retrieve/inspect/present data) and when ("Use when the user wants Codex to connect to an existing Twenty workspace...") with concrete trigger framing.	5 / 5
Trigger Term Quality	Good domain keyword coverage ("Twenty workspace", "MCP", "CRM", "records", "metadata", "Markdown") but leans operational/technical rather than the casual phrases a user would actually say (e.g., "list my companies in Twenty"), so it falls just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to inspecting an existing Twenty workspace via MCP and framed as distinct from app work, giving it a clear niche with minimal overlap risk against the other Twenty skills.	5 / 5
	Total	19 / 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/use-twenty-mcp/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.