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.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/syncable-entity-runner-and-actions/SKILL.md

Quality

Content

57%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 content is highly actionable with complete, file-located code, but it is held back by a redundant patterns section, missing validation steps for destructive database operations, and an absence of progressive disclosure via reference files.

Suggestions

Remove or trim the 'Action Handler Patterns' section since it duplicates the transpilation code already shown in Steps 1-3, reducing token cost.

Add an explicit validation/verification checkpoint (e.g., run the migration in a test workspace and assert the handlers produced the expected rows) before the checklist, since create/update/delete are destructive operations.

Move the full per-handler code templates into reference files under ./references/ and keep SKILL.md as an overview with one-level-deep links, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The code is mostly lean with brief comments, but the 'Action Handler Patterns' section duplicates the transpilation logic already shown in Steps 1-3, which is padding that could be trimmed; not 4 because of this redundancy.	3 / 5
Actionability	Full, copy-paste-ready TypeScript implementations with concrete file paths and helper usage, but several referenced types (UniversalUpdateMyEntityAction, FlatUpdateMyEntityAction, AllFlatEntityMapsByMetadataName) are used without imports in the update/delete examples, leaving minor gaps below anchor 5.	4 / 5
Workflow Clarity	Four sub-steps are clearly sequenced with a checklist, but this skill performs destructive database create/update/delete operations with no validation or verification checkpoint and no error-recovery loop, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and all four full code implementations are inlined in a 355-line document with good headers but no reference files; content that could be split into separate files is inline, matching anchor 3 rather than 4.	3 / 5
	Total	13 / 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 strong: it pairs a concrete 'what' with an explicit, multi-clause 'when' trigger and occupies a distinct niche. The main weakness is trigger-term phrasing that leans on domain jargon rather than natural user synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Implement action handlers', 'creating database operations for syncable entities', 'universal-to-flat entity transpilation', 'create/update/delete actions'), matching anchor 4 rather than 5 because the actions are slightly abstract and coverage has minor gaps.	4 / 5
Completeness	Clearly answers both 'what' ('Implement action handlers for executing workspace migrations in Twenty') and 'when' ('Use when creating database operations... or handling create/update/delete actions in the runner layer') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of domain terms a Twenty developer would naturally say ('syncable entities', 'universal-to-flat entity transpilation', 'runner layer', 'create/update/delete actions') with three enumerated scenarios, but missing common synonyms or variations keeps it below 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a highly specific niche (Twenty syncable-entity migration runner layer) with distinct triggers and minimal risk of firing for an unrelated skill.	5 / 5
	Total	18 / 20 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-runner-and-actions/SKILL.md
Commit: cbd58da

Reviewed: 3 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.