syncable-entity-integration

Wire syncable entity services into NestJS modules, create service layer and resolvers for Twenty entities. Use when registering builders, validators, and action handlers in modules, creating business services, or exposing entities via GraphQL API with proper exception handling.

Quality

88%

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

77%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 content is highly actionable with real, sequenced NestJS code and a clear workflow plus checklist. Its weaknesses are redundancy (the flat-entity principle restated several times) and a monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

State the flat→DTO layering principle once (e.g. in Quick Start) and remove the repeated restatements in Step 4, Step 5, and the Layer Responsibilities section to tighten conciseness.

Extract the large, reusable code templates (e.g. the service skeleton and flat-to-DTO conversion utility) into reference files under references/ and link to them, so SKILL.md stays a lean overview.

Collapse the duplicated Layer Responsibilities table and bullet lists into the single statement of the service/resolver split to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with real file paths and code, but the flat→DTO / layer-split principle is restated four times (Quick Start, Step 4 "Service pattern", Step 5 "Resolver responsibilities", and the "Layer Responsibilities" section), which is padding that could be tightened.	2 / 3
Actionability	Each step ships concrete, near-copy-paste-ready TypeScript with exact file paths, imports, and full module/service/resolver implementations, matching the score-3 anchor for fully executable examples.	3 / 3
Workflow Clarity	A clearly sequenced 6-step process with per-step file targets and a final completion checklist serving as the verification checkpoint before the mandatory next step, satisfying the score-3 anchor.	3 / 3
Progressive Disclosure	Well-organized into labeled sections but it is a monolithic ~320-line SKILL.md with no bundle files and all large code templates inline; content that could be split into reference files (e.g. the flat→DTO conversion or service template) is not separated, matching the score-2 anchor.	2 / 3
	Total	10 / 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 capabilities and gives an explicit "Use when" trigger covering the three registration tasks plus service/resolver creation, all scoped to a distinct niche. No vague fluff or over-claims are present.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Wire syncable entity services into NestJS modules", "create service layer and resolvers", "registering builders, validators, and action handlers", "creating business services", and "exposing entities via GraphQL API" — matching the score-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly answers both what ("Wire syncable entity services into NestJS modules, create service layer and resolvers") and when (explicit "Use when..." clause with concrete triggers), satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	The "Use when" clause surfaces natural developer terms ("builders, validators, and action handlers", "business services", "GraphQL API", "exception handling") that a user of this codebase would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow niche (Twenty syncable entity integration, Step 5/6) with distinct triggers unlikely to fire for unrelated skills, matching the score-3 anchor for a clear niche.	3 / 3
	Total	12 / 12 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: twentyhq/twenty
Path: .cursor/skills/syncable-entity-integration/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.