CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable and well-sequenced with executable code, running commands, and verification checklists. Its main weakness is conciseness and progressive disclosure: large inline code templates that would benefit from being split into reference files.

Suggestions

Move the full query-factory and wrapper TypeScript templates into files under references/ (e.g. references/create-my-entity-query-factory.template.ts) and summarize the pattern in the body, reducing inline token weight.

Trim the repeated checklists (Test Utilities, Failing Tests Coverage, Successful Tests Coverage, Snapshot Tests) into a single consolidated checklist to cut redundancy.

Add a clear 'Advanced patterns' section that links one level deep to reference files for JSONB validation, update/delete specs, and snapshot management, instead of describing them inline.

DimensionReasoningScore

Conciseness

Content is actionable rather than explanatory, but ~490 lines inline several full TypeScript test files and redundant checklists that could be tightened or externalized; it is mostly efficient but padded with length.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript code and concrete commands such as 'npx jest test/integration/metadata/suites/my-entity --config=packages/twenty-server/jest.config.mjs', with no pseudocode.

3 / 3

Workflow Clarity

Multi-step process is clearly sequenced (Step 1 utilities, Step 2 failing tests, Step 3 successful tests, Step 4 update/delete) with checklists, a Running Tests verification section, and explicit Success Criteria checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist in references/scripts/assets, and all content sits inline in one ~490-line file; only a single external 'see @creating-syncable-entity rule' reference is signaled, so content that should be split is inline.

2 / 3

Total

10

/

12

Passed

Description

100%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 strong, specific description that clearly states both capability and an explicit 'Use when' trigger in third-person voice, with low conflict risk. It is concise and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Create comprehensive integration tests ... covering validator exceptions, input transpilation errors, and CRUD operations', matching the score-3 anchor of naming several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (create integration tests covering the listed scenarios) and when via an explicit 'Use when writing integration tests for metadata entities' clause, in third-person voice, so it is not capped at 2.

3 / 3

Trigger Term Quality

Includes natural domain terms a Twenty developer would actually say — 'integration tests', 'syncable entities', 'metadata entities', 'CRUD operations' — giving good coverage rather than only jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche ('syncable entities in Twenty', 'metadata entities') with distinct triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.