syncable-entity-builder-and-validation

Create validation logic and migration action builders for syncable entities in Twenty. Use when implementing business rule validation, uniqueness checks, foreign key validation, or building workspace migration actions for syncable entities. Validators never throw and never mutate.

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.

Highly actionable thanks to complete executable code and a clearly sequenced workflow with a gating checklist, but it leans verbose because the validation patterns are repeated and the whole skill is one large inline file rather than an overview pointing to reference materials.

Suggestions

Drop or condense the "Validation Patterns" section — the same four patterns are already shown in the Step 1 validator code; keeping both is redundant.

Move the full Step 1–3 service implementations into reference files (e.g. references/validator-service.ts, references/builder-service.ts) and have SKILL.md show condensed signatures with links, reducing the inline footprint.

Add a brief compile/typecheck verification step to the closing checklist so the migration workflow has an explicit build-time feedback loop before advancing to Step 4.

Dimension	Reasoning	Score
Conciseness	The body is code-centric and avoids explaining concepts Claude already knows, but the "Validation Patterns" section substantially reiterates the four patterns already demonstrated inline in the Step 1 validator implementation, adding redundancy.	2 / 3
Actionability	Provides complete, executable TypeScript services with real import paths and file locations, plus a concrete ❌ BAD / ✅ GOOD indexed-lookup example — effectively copy-paste ready (modulo entity-name substitution).	3 / 3
Workflow Clarity	A clear Step 1 → Step 2 → Step 3 sequence with the critical orchestrator step flagged, and a verification checklist gating progression to Step 4 serves as an explicit validation checkpoint.	3 / 3
Progressive Disclosure	Well-sectioned, but monolithic: the full Step 1–3 service implementations are large inline code blocks that could live in reference files, and no bundle files (references/scripts/assets) are present to offload them.	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.

A strong, well-scoped description: it states concrete capabilities, provides an explicit "Use when" trigger with multiple natural keywords, and stays in third-person voice. The trailing "Validators never throw and never mutate" adds a useful distinguishing constraint without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Create validation logic and migration action builders" plus "business rule validation, uniqueness checks, foreign key validation, or building workspace migration actions" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("Create validation logic and migration action builders for syncable entities in Twenty") and when ("Use when implementing...") with an explicit trigger clause.	3 / 3
Trigger Term Quality	The "Use when implementing business rule validation, uniqueness checks, foreign key validation, or building workspace migration actions" clause covers several natural trigger phrases a developer on this codebase would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche — "syncable entities in Twenty" with validation/migration-specific triggers — making it unlikely to fire for unrelated skills.	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-builder-and-validation/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.