CtrlK
BlogDocsLog inGet started
Tessl Logo

syncable-entity-integration

Wire syncable entity services into NestJS modules, create service layer and resolvers for Twenty entities. Use when registering builders, validators, and action handlers in modules, creating business services, or exposing entities via GraphQL API with proper exception handling.

68

Quality

83%

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

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

A highly actionable, well-sequenced integration guide with concrete code and exact file paths, supported by a checklist and mandatory handoff to testing. Minor redundancy and the absence of an explicit build/verify checkpoint keep it just short of top marks.

Suggestions

Add an explicit build/compile verification step (e.g., 'Run the workspace build and confirm no DI errors') before the checklist to strengthen the validation checkpoint.

Show the `update` and `delete` service methods (or note they mirror `create`) so the resolver calls are not referencing unimplemented code.

Collapse the duplicated layer-responsibility content (Quick Start principle, table, and bullet list) into a single section to tighten token efficiency.

DimensionReasoningScore

Conciseness

Largely efficient executable code with no over-explanation of known concepts, but layer responsibilities are restated three times (Quick Start principle, the table, and the bullet sections), which could be trimmed.

4 / 5

Actionability

Concrete copy-paste TypeScript with exact file paths for modules, service, resolver, and conversion util, but the service only implements `create` while the resolver calls `update`/`delete`, leaving a minor gap.

4 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced with a closing checklist and a mandatory next-step link to testing, but there is no in-workflow build/compile verification checkpoint before moving on.

4 / 5

Progressive Disclosure

Well-organized into clearly signaled sections (Quick Start, Steps 1–6, Layer Responsibilities, Checklist, Next Step) with one-level-deep references to the sibling testing skill and parent rule, though all code is inline in a ~320-line file.

4 / 5

Total

16

/

20

Passed

Description

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

A specific, well-triggered description that clearly states both capability and invocation conditions with concrete, domain-anchored language. Slightly jargon-heavy on trigger terms but highly distinguishable and complete.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Wire syncable entity services into NestJS modules', 'create service layer and resolvers', 'registering builders, validators, and action handlers', 'exposing entities via GraphQL API' — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('Wire... create service layer and resolvers') and when ('Use when registering builders, validators, and action handlers... creating business services, or exposing entities via GraphQL API') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with natural developer terms ('NestJS modules', 'builders, validators, action handlers', 'GraphQL API'), but jargon-heavy and missing common synonyms or variations that would warrant a 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Twenty syncable entities in NestJS) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

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.