CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/syncable-entity-builder-and-validation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body is highly actionable with executable code, exact file paths, and a clear three-step workflow plus checklist. It loses points for duplicated content across the full example and the patterns summary, placeholder gaps in the orchestrator snippet, and the absence of bundle files for the large code blocks.

Suggestions

Move the large validator/builder/orchestrator code blocks into reference files under references/ and link to them from SKILL.md to improve progressive disclosure and reduce inline duplication.

Remove or compress the 'Validation Patterns' and 'Performance warning' sections since they restate logic already shown verbatim in Step 1, or keep only the abbreviated patterns and drop the duplicated code.

Replace the orchestrator's '// ... existing code' placeholders and define or import the referenced 'AllFlatEntityMapsByMetadataName' type so the example is fully copy-paste-ready.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code, but the 'Validation Patterns' section and the 'Performance warning' code block largely duplicate logic already shown in full in Step 1's validator service, and the checklist restates principles already stated, so it could be tightened.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready TypeScript with exact file paths for the validator and builder, but the orchestrator example uses '// ... existing code' placeholders and references an undefined 'AllFlatEntityMapsByMetadataName' type, leaving minor gaps.

4 / 5

Workflow Clarity

Three steps are clearly sequenced with the orchestrator step flagged as CRITICAL and a verification checklist closing the workflow; validation is embedded via error arrays and a checklist, though there is no explicit fix-and-retry loop.

4 / 5

Progressive Disclosure

Good section structure and a one-level 'Next Step' link, but no bundle files exist and large executable code blocks that would fit reference files are inlined in a single ~390-line document, so content that should be separate is inline.

3 / 5

Total

14

/

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.

The description is specific, complete, and distinctive, with concrete trigger phrases and a clear niche. It is slightly jargon-heavy and lacks synonym/extension coverage, capping trigger term quality and specificity just below the top anchor.

DimensionReasoningScore

Specificity

Lists several concrete actions ('validation logic', 'migration action builders', 'uniqueness checks', 'foreign key validation', 'workspace migration actions') for a named domain, but they are variations of two core builder tasks rather than a maximally diverse set, leaving minor coverage gaps.

4 / 5

Completeness

Clearly answers both 'what' ('Create validation logic and migration action builders for syncable entities in Twenty') and 'when' ('Use when implementing business rule validation, uniqueness checks, foreign key validation, or building workspace migration actions') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with developer-natural phrases ('business rule validation', 'uniqueness checks', 'foreign key validation', 'workspace migration actions for syncable entities'), though it lacks synonyms or file/extension variants a user might also say.

4 / 5

Distinctiveness Conflict Risk

A clear niche ('syncable entities in Twenty' with validators that 'never throw and never mutate') gives it distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
twentyhq/twenty
Reviewed

Table of Contents

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.