Skip to content

AI / LLM Tooling

We’re building the infrastructure to make ENS a first-class citizen for AI agents.

The foundation for how developers and their AI agents reach for ENS is ensskills, that teach your AI assistant about ENS, ENSNode, the ENS Omnigraph, and how to drive enscli — an agent- and human-friendly CLI — on your behalf.

Add ensskills and skills-npm to your project and wire a prepare script so the pinned skills re-sync into your agent directories (.claude/skills, .cursor/skills, …) on every install:

package.json
{
"devDependencies": {
"ensskills": "0.0.0-next-20260603190454",
"skills-npm": "^1"
},
"scripts": {
"prepare": "skills-npm"
}
}
Terminal window
npm install # symlinks the skills for your detected agents

Not in a Node project? skills installs every ENS skill straight from the repo. It normally pins to the matching v… release tag; during the current prerelease window it pins to the immutable main commit the prerelease snapshot was built from, until enscli/ensskills ship in their first official release:

Terminal window
npx skills add https://github.com/namehash/ensnode/tree/0eec193/packages/ensskills/skills --skill '*'

That’s it — your AI agent now has all of ensskills at its disposal.

prompt.md
Which address currently owns vitalik.eth
and how many other domains do they own?

If you aren’t using ensskills, the entire documentation site is also published in the llms.txt format so any agent or LLM can load it directly as context:

  • /llms.txt — a structured index of the documentation with links to every page.
  • /llms-full.txt — the entire documentation concatenated into a single file, ready to drop into a model’s context window.

Paste this at the top of a prompt to point your agent at the full documentation before asking your question:

prompt.md
Load the ENSNode documentation from https://ensnode.io/llms-full.txt to answer the following question: