Name: syncable-entity-testing
Rating: 66.4 (1 reviews)
Author: twentyhq

syncable-entity-testing

Contributing to the Twenty codebase itself (twentyhq/twenty server internals), not for building apps on top of Twenty. Create comprehensive integration tests for syncable entities in Twenty. Use when writing integration tests for metadata entities, covering validator exceptions, input transpilation errors, and CRUD operations. Tests are MANDATORY for all syncable entities.

Quality

79%

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

The canonical home for this skill is syncable-entity-testing in twentyhq/twenty

Quality

Content

71%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 templates and a clear step sequence, but it is verbose due to repeated checklists and monolithic — it would benefit from consolidating duplicated coverage lists and splitting large code templates into reference files.

Suggestions

Consolidate the repeated coverage lists: keep one canonical checklist (e.g. the 'Complete Test Checklist') and reference it from Quick Start and Success Criteria instead of restating the items.

Move the full query-factory and wrapper boilerplate templates into a references/ file (e.g. references/test-templates.ts) and keep only a condensed example plus a link in SKILL.md to reduce the inline wall of code.

Add an explicit feedback loop in the Running Tests section (e.g. 'if a snapshot fails, review the diff, fix the test/entity, then re-run with --updateSnapshot only when the new output is correct') to strengthen workflow_clarity.

Dimension	Reasoning	Score
Conciseness	Code examples are lean and executable, but coverage requirements are restated four times (Quick Start, per-step 'Test coverage requirements', 'Complete Test Checklist', and 'Success Criteria'), adding noticeable padding that could be consolidated.	3 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript for query factories, wrappers, and failing/successful test specs with concrete file paths, covering the common cases directly.	5 / 5
Workflow Clarity	Clear sequenced steps (utilities → failing creation → successful creation → update/delete) with checklists and a Running Tests verification section, but error-recovery feedback loops (what to do when a test fails) are implicit rather than explicit.	4 / 5
Progressive Disclosure	Well-organized into labeled sections but monolithic — all ~490 lines and full code templates are inlined with no references to detail files (only a trailing @creating-syncable-entity pointer); content that could live in reference files is inline.	3 / 5
	Total	15 / 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, trigger-rich, and explicitly disambiguated, clearly answering both what the skill does and when to use it. Minor gaps in keyword synonym coverage keep specificity and trigger_term_quality just short of perfect.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'covering validator exceptions, input transpilation errors, and CRUD operations' — giving specific scope rather than generic language, though coverage is not exhaustive.	4 / 5
Completeness	Explicitly answers both 'what' (create comprehensive integration tests for syncable entities covering validators, transpilation errors, CRUD) and 'when' via a concrete 'Use when writing integration tests for metadata entities...' trigger phrase.	5 / 5
Trigger Term Quality	Includes natural terms a Twenty contributor would say ('integration tests', 'syncable entities', 'metadata entities', 'CRUD operations') with good coverage, but lacks synonyms or file-extension variants that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche ('Contributing to the Twenty codebase itself ... not for building apps on top of Twenty') with distinct triggers and an explicit disambiguation, minimizing conflict with adjacent skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: twentyhq/twenty
Path: .claude/skills/syncable-entity-testing/SKILL.md
Commit: 710f163

Reviewed: 1 day 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.