syncable-entity-testing

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

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-testing/SKILL.md

Quality

Content

61%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, executable code and precise run commands, but it is verbose — repeating coverage requirements and embedding several large full-file examples that pad the context. Workflow sequencing is present yet missing explicit validation checkpoints for destructive test operations.

Suggestions

Trim repetition: the 'Test coverage requirements' lists under Steps 2-3 duplicate the test cases already shown in the code and reappear in the 'Complete Test Checklist' — keep one consolidated checklist and reference it.

Replace full-file copy-paste blocks (e.g., the entire failing-creation spec) with one representative example plus a concise pattern description, since Claude can extrapolate the remaining CRUD variants from it.

Add an explicit validation/verification checkpoint into the test-authoring workflow (e.g., 'run the new spec and confirm both failing and successful cases pass before marking the entity complete') to satisfy the destructive/batch feedback-loop requirement.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose, embedding multiple large copy-paste code blocks (query factory, wrapper, full failing and successful spec files) and re-listing coverage requirements as both prose and checklists, much of which Claude could derive from one representative example plus a pattern description.	2 / 5
Actionability	Guidance is fully executable: concrete file paths, complete TypeScript code for query factories/wrappers, runnable jest commands with exact --config flags, and copy-paste-ready test cases covering common scenarios.	5 / 5
Workflow Clarity	Steps are sequenced (utilities → failing tests → successful tests → update/delete → run) and a checklist exists, but destructive batch operations (create/update/delete entity tests) lack explicit validation checkpoints or feedback loops, which caps workflow clarity per the rubric.	3 / 5
Progressive Disclosure	Good section structure with well-organized headers, a quick start, and a checklist; the body relies on inline examples rather than external references (no bundle files exist), which is appropriate for a single-step process, though the large code blocks could be slimmed.	4 / 5
	Total	14 / 20 Passed

Description

83%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 states concrete actions and an explicit 'Use when' trigger clause with natural, domain-specific keywords. It is narrowly scoped to syncable-entity integration testing, giving it good distinctiveness, though a few trigger-term synonyms could broaden coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several specific concrete actions — 'Create comprehensive integration tests', 'covering validator exceptions, input transpilation errors, and CRUD operations' — with only minor gaps in coverage rather than a fully comprehensive enumeration.	4 / 5
Completeness	Explicitly answers both what ('Create comprehensive integration tests for syncable entities...') and when ('Use when writing integration tests for metadata entities...') with concrete trigger phrases, satisfying both halves clearly.	5 / 5
Trigger Term Quality	Strong natural keywords such as 'integration tests', 'metadata entities', 'validator exceptions', 'input transpilation errors', and 'CRUD operations', with a few common variations (e.g., synonyms or test-suite phrasings) missing.	4 / 5
Distinctiveness Conflict Risk	The niche is fairly specific (syncable entities in Twenty, metadata test suites), making it mostly distinct with only minor overlap risk against general testing skills.	4 / 5
	Total	17 / 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: .cursor/skills/syncable-entity-testing/SKILL.md
Commit: cbd58da

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