Skip to content

ensskills (AI agents)

ensskills is a curated set of agent skills that give AI coding agents — Claude Code, Cursor, Codex, and the rest — a well-defined contract for working with ENS. Left to their own devices, agents reinvent ENS from scratch every prompt, burning context rediscovering the protocol. ensskills hands them the right context—no more, no less—so they produce ENS code that works correctly, the first time.

The skills drive enscli for live ENS lookups and steer agents toward enssdk / enskit when writing integration code.

ensskills is a normal, version-locked npm package: it ships the skills, and skills-npm symlinks them into whichever agent directories you have (.claude/skills, .cursor/skills, …). Because the skills are pinned like any dependency, the version you install is exactly the version that lands — and it stays in lockstep with the rest of your ENSNode suite.

Add both to your project and wire a prepare script:

package.json
{
"devDependencies": {
"ensskills": "1.15.1",
"skills-npm": "^1"
},
"scripts": {
// re-syncs the pinned skills into your agent dirs on every install
"prepare": "skills-npm"
}
}
Terminal window
pnpm install # symlinks the skills for your detected agents
  • ens-protocol — how the ENS protocol works at a conceptual level: the nametree, normalization, namehash/labelhash, registry/resolver/registrar, forward & reverse resolution, primary names, records, and ENS across chains. Vendor-neutral, intentionally stable, with pull-as-needed reference pages. The mental model the other skills build on.
  • omnigraph — the monolithic ENS skill. Teaches the unified ENSv1 + ENSv2 datamodel, resolution via Domain.resolve / Account.resolve, Relay pagination, a condensed schema reference, vetted example queries, and how to execute and explore queries with enscli.
  • enscli — running ENS lookups from the shell: the output contract, namespace/URL resolution, input hardening, and every command (Omnigraph queries, offline schema exploration, namehash/labelhash, ENSRainbow healing, indexing status).

The following are reserved and ship as stubs today, fleshed out in upcoming releases:

  • enssdk — TypeScript integration with the typed Omnigraph client.
  • enskit — React integration (useOmnigraphQuery, cache directives, infinite pagination).
  • migrate-to-omnigraph — migrating from the legacy ENS Subgraph.
  • unigraph-sql — SQL over ENSDb for query shapes the Omnigraph doesn’t express.
  • Developers building ENS apps with AI agents in the loop.
  • End-users asking AI assistants ENS-shaped questions and expecting answers grounded in the protocol.
  • Teams moving from the legacy ENS Subgraph onto the Omnigraph.