CtrlK
BlogDocsLog inGet started
Tessl Logo

syncable-entity-runner-and-actions

Implement action handlers for executing workspace migrations in Twenty. Use when creating database operations for syncable entities, implementing universal-to-flat entity transpilation, or handling create/update/delete actions in the runner layer.

65

Quality

78%

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-runner-and-actions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, copy-paste-ready code skill with clear sequencing and clean self-contained organization. Its main gaps are a redundant patterns section that repeats the step code and the absence of validation/feedback checkpoints for its destructive database operations.

Suggestions

Remove or condense the 'Action Handler Patterns' section, since it duplicates the code already shown in Steps 1-3; cross-reference those steps instead.

Add an explicit validation checkpoint after the execute phase (e.g., verify affected row counts or run a post-migration check) with a fix-and-retry loop for the destructive delete/update handlers.

DimensionReasoningScore

Conciseness

The content is actionable reference code rather than padded concept explanation, but the 'Action Handler Patterns' section re-presents the same transpile/execute code already shown in Steps 1-3, adding redundant tokens that could be tightened.

2 / 3

Actionability

Each step provides fully executable TypeScript with exact file paths, imports, class signatures, and complete method bodies, making it copy-paste ready.

3 / 3

Workflow Clarity

Steps are clearly sequenced with a numbered checklist, but the skill performs destructive/batch database operations (hard delete, row updates) with no validation checkpoints or validate-fix-retry feedback loop, which caps this dimension at 2 per the rubric notes.

2 / 3

Progressive Disclosure

No bundle files exist; the body is self-contained and well-sectioned (Quick Start, Steps, Patterns, Checklist, Next Step) with only one-level-deep references to the next step skill and the @creating-syncable-entity rule.

3 / 3

Total

10

/

12

Passed

Description

85%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 specific, complete, third-person description with an explicit trigger clause and a clear niche. Its main weakness is trigger-term naturalness: much of the vocabulary is internal Twenty jargon rather than phrasings a user would naturally utter.

Suggestions

Add a few plain-language trigger terms a user might actually say (e.g., 'migrating workspace data', 'creating or updating custom objects') alongside the technical jargon.

Consider softening 'universal-to-flat entity transpilation' in the trigger clause to a more recognizable phrase like 'converting universal entities to flat database rows'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Implement action handlers', 'executing workspace migrations', 'creating database operations', 'implementing universal-to-flat entity transpilation', 'handling create/update/delete actions'), matching the comprehensive-actions anchor.

3 / 3

Completeness

Explicitly answers both what ('Implement action handlers for executing workspace migrations') and when via an explicit 'Use when...' clause with concrete triggers, in third-person voice.

3 / 3

Trigger Term Quality

Some natural keywords appear ('create/update/delete', 'database operations') but they are outweighed by internal jargon ('syncable entities', 'universal-to-flat entity transpilation', 'runner layer') that users would rarely say, so coverage of natural terms is incomplete.

2 / 3

Distinctiveness Conflict Risk

Targets a distinct niche (Twenty workspace-migration action handlers, runner layer) with triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.