Agent skill

Twenty Syncable Entity Wiring

by twentyhq in twentyhq/twenty

Registers a new syncable entity in three NestJS modules and adds its service and GraphQL resolver layers when contributing to the Twenty server.

Custom licenceAuto-check passedBackend & APIs

Install Twenty Syncable Entity Wiring

skills CLI
$ npx skills add twentyhq/twenty --skill syncable-entity-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install twentyhq/twenty syncable-entity-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/twentyhq/twenty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/syncable-entity-integration .claude/skills/syncable-entity-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
syncable-entity-integration
GitHub stars
58k
Token cost
~2.9k tokens
SKILL.md length
366 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
Custom licence

At a glance

Registers a new syncable entity in three NestJS modules and adds its service and GraphQL resolver layers when contributing to the Twenty server.

  • Works in 6 steps: Register in Builder Module → Register in Validators Module → Register Action Handlers → …
  • Registering builders, validators and action handlers for a new Twenty entity
  • SKILL.md covers Quick Start, Step 1: Register in Builder…, Step 2: Register in Validators… and Step 3: Register Action Handlers, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This is step five of six in a sequence for adding a syncable entity to the Twenty server, done after the earlier four steps and before testing. The agent registers the entity's workspace migration builder in its module, adds the validator service to the validators module, and registers create, update and delete action handlers, noting that builders must be both provided and exported while handlers are normally only provided.

It then builds the service layer, which returns flat entities, and the resolver layer, which converts those flat entities to DTOs, with an exception interceptor handling errors for GraphQL. The skill applies only to work on Twenty's own server internals, not to apps built on top of Twenty.

When your agent uses it

  • Registering builders, validators and action handlers for a new Twenty entity
  • Adding a business service and resolver for an entity exposed through GraphQL
  • Finishing the integration step before testing a syncable entity

Example prompts

  • “Wire a new syncable entity called Bookmark into the Twenty builder, validator and action handler modules.”
  • “Create the service and resolver for the Bookmark entity, with the service returning flat entities.”
  • “Add the exception interceptor so Bookmark errors surface properly in GraphQL.”

Requirements

  • A checkout of the twentyhq/twenty repository with the first four steps already done

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Register in Builder Module
  2. Register in Validators Module
  3. Register Action Handlers
  4. Create Service Layer
  5. Create Resolver Layer
  6. Flat-to-DTO Conversion

What it can do on your machine

Read from SKILL.md and the folder at commit 0d66dd1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Twenty Syncable Entity Wiring loads about 2.9k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 366 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 366 words (~2,870 tokens).

“Purpose: Wire everything together, register in modules, create services and resolvers.”

— opening of SKILL.md by twentyhq, Custom licence
name
syncable-entity-integration

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/syncable-entity-integration of twentyhq/twenty.

Open the folder on GitHubat commit 0d66dd1

Compare with similar skills

Twenty Syncable Entity Wiring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Twenty Syncable Entity Wiring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Twenty Syncable Entity Wiring this skilltwentyhq/twenty58k—~2.9kAutomated safety check: PassCustom licence
Implementing API Patternsancoleman/ai-design-components5261 repos~3kAutomated safety check: PassMIT
API Designericrisco/rsc-harness156—~3.1kAutomated safety check: PassMIT
Nestjsgiuseppe-trisciuoglio/developer-kit355—~1.4kAutomated safety check: NotesMIT
Node Backend Development Guidelinesdiet103/claude-code-infrastructure-showcase10k2 repos~2kAutomated safety check: PassMIT
API DesignerJeffallan/claude-skills12k2 repos~2kAutomated safety check: PassMIT

Similar skills

  • Implementing API Patterns

    ancoleman/ai-design-components

    API design and implementation across REST, GraphQL, gRPC, and tRPC patterns.

    526 GitHub starsUsed in 1 repo~3k tokens
    Backend & APIsAuto-check passed
  • API Design

    ericrisco/rsc-harness

    A skill your agent uses when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency —…

    156 GitHub stars~3.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Nestjs

    giuseppe-trisciuoglio/developer-kit

    Provides comprehensive NestJS framework patterns with Drizzle ORM integration for building scalable server-side applications.

    355 GitHub stars~1.4k tokensUpdated 27 days ago
    Backend & APIsAuto-check: notes
  • Node Backend Development Guidelines

    diet103/claude-code-infrastructure-showcase

    Sets layered architecture and coding rules for Node.js, Express and TypeScript microservices, covering routes, controllers, services, repositories, Prisma, Sentry and Zod.

    10k GitHub starsUsed in 2 repos~2k tokens
    Backend & APIsAuto-check passed
  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 2 repos~2k tokens
    Backend & APIsAuto-check passed
  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    158 GitHub starsUsed in 17 repos~4k tokens
    Backend & APIsAuto-check passed

More from twentyhq/twenty

All 13 skills in this repo
  • Guides changes to an existing Twenty app: adding or editing objects, layouts, logic functions and front components, with a plan stated before multi-entity edits.

    58k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Twenty App Operations

    twentyhq/twenty

    Operates an existing Twenty app: managing remotes, syncing, building, deploying, reading logs, running tests and setting up CI/CD, with confirmation for production.

    58k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Contributor guide for step three of adding a syncable entity to the Twenty server: write the validator, the migration action builder and the orchestrator wiring.

    58k GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Walks through step 2 of adding a syncable entity to the Twenty server: a cache service for flat entity maps and utilities that transform entities and DTOs into universal flat entities.

    58k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Step four of adding a syncable entity in the Twenty server: write create, update and delete action handlers that run workspace migrations against the database.

    58k GitHub stars~3.1k tokensUpdated today
    Auto-check passed
  • Step-by-step guide to writing the mandatory integration tests for syncable metadata entities in Twenty's server, covering failures and CRUD success cases.

    58k GitHub stars~3.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Twenty Syncable Entity Wiring

What does Twenty Syncable Entity Wiring do?

Registers a new syncable entity in three NestJS modules and adds its service and GraphQL resolver layers when contributing to the Twenty server. This is step five of six in a sequence for adding a syncable entity to the Twenty server, done after the earlier four steps and before testing. The agent registers the entity's workspace migration builder in its module, adds the validator service to the validators module, and registers create, update and delete action handlers, noting that builders must be both provided and exported while handlers are normally only provided.

When should I use Twenty Syncable Entity Wiring?

Twenty Syncable Entity Wiring fits situations like: registering builders, validators and action handlers for a new Twenty entity; adding a business service and resolver for an entity exposed through GraphQL; finishing the integration step before testing a syncable entity.

How do I install Twenty Syncable Entity Wiring in Claude Code?

Run `npx skills add twentyhq/twenty --skill syncable-entity-integration -a claude-code`. Or copy the skill folder (.claude/skills/syncable-entity-integration in twentyhq/twenty) into .claude/skills/syncable-entity-integration in your project. Claude Code loads it when a task matches its description.

How do I install Twenty Syncable Entity Wiring in Codex?

Run `npx skills add twentyhq/twenty --skill syncable-entity-integration -a codex`. Or copy the skill folder (.claude/skills/syncable-entity-integration in twentyhq/twenty) into .agents/skills/syncable-entity-integration in your project. Codex loads it when a task matches its description.

Can I use Twenty Syncable Entity Wiring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add twentyhq/twenty --skill syncable-entity-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/syncable-entity-integration, .gemini/skills/syncable-entity-integration, .github/skills/syncable-entity-integration and .opencode/skills/syncable-entity-integration in your project.

What does Twenty Syncable Entity Wiring need to run?

SKILL.md names no scripts, command-line tools or credentials: Twenty Syncable Entity Wiring is instructions for the agent only. Our summary lists: A checkout of the twentyhq/twenty repository with the first four steps already done.

Does Twenty Syncable Entity Wiring access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Twenty Syncable Entity Wiring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Twenty Syncable Entity Wiring use?

Twenty Syncable Entity Wiring has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Twenty Syncable Entity Wiring use?

About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Twenty Syncable Entity Wiring?

Skills that share tags, products or a category with Twenty Syncable Entity Wiring: Implementing API Patterns (ancoleman/ai-design-components, 526 stars), API Design (ericrisco/rsc-harness, 156 stars), Nestjs (giuseppe-trisciuoglio/developer-kit, 355 stars) and Node Backend Development Guidelines (diet103/claude-code-infrastructure-showcase, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Twenty Syncable Entity Wiring?

twentyhq (a GitHub organization) maintains it in twentyhq/twenty, which has 57,999 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

Source: twentyhq/twenty on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.