CtrlK
BlogDocsLog inGet started
Tessl Logo

syncable-entity-builder-and-validation

Contributing to the Twenty codebase itself (twentyhq/twenty server internals), not for building apps on top of Twenty. 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.

66

Quality

80%

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 ./.claude/skills/syncable-entity-builder-and-validation/SKILL.md

The canonical home for this skill is syncable-entity-builder-and-validation in twentyhq/twenty

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A highly actionable, well-sequenced code skill with executable TypeScript examples and a strong verification checklist. Its main weakness is conciseness: the distilled patterns and performance sections duplicate code already shown inline.

Suggestions

Remove or collapse the 'Validation Patterns' section since each pattern is already demonstrated in the full validator service with inline comments; keep it only as a one-line index if needed.

Drop the standalone BAD/GOOD performance example — the indexed-map lookup is already shown in the validator code with an 'O(1)' comment — and instead state the rule once in 'Key principles'.

In the orchestrator step, replace '// ... existing code' with a minimal concrete diff (constructor injection line + the exact return-spread) so the wiring is fully copy-pasteable.

DimensionReasoningScore

Conciseness

Mostly efficient and code-dense, but the 'Validation Patterns' section and the BAD/GOOD performance example restate patterns and the indexed-map lookup already shown inline with comments, adding redundant tokens.

3 / 5

Actionability

Provides complete, copy-paste-ready NestJS services with concrete file paths and imports for the validator and builder, but the orchestrator step uses '// ... existing code' elisions and references a couple of unimported types, leaving minor gaps.

4 / 5

Workflow Clarity

Three steps are clearly sequenced with a CRITICAL flag on orchestrator wiring and a thorough end-of-step checklist; the only gap is the absence of an explicit fix-and-retry loop, which the checklist largely compensates for.

4 / 5

Progressive Disclosure

Well-sectioned single file with a clear one-level next-step reference and no bundle files to navigate, but the large inline code blocks are not split into reference files, leaving minor organization gaps.

4 / 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.

A strong, third-person description that states a distinct niche, concrete actions, and explicit trigger conditions with a helpful disambiguation clause. Only minor room for improvement on trigger-term synonyms.

DimensionReasoningScore

Specificity

Names the domain and 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' — giving comprehensive coverage.

5 / 5

Completeness

Explicitly 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 natural-keyword coverage ('business rule validation', 'uniqueness checks', 'foreign key validation', 'workspace migration actions', 'syncable entities') but lacks synonyms or file extensions, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche with an explicit boundary clause — 'Contributing to the Twenty codebase itself (twentyhq/twenty server internals), not for building apps on top of Twenty' — minimizing overlap with other skills.

5 / 5

Total

19

/

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.