Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,14 @@ export const integrateSidebarTopic = {
label: "ENSDb (PostgreSQL)",
link: "/docs/integrate/integration-options/ensdb",
},
{
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Goader Great work shipping these two new pages!

CleanShot 2026-05-14 at 12 35 33

Could you please also update the text here on the "AI / LLM Tooling" page?

The general message we should communicate here is:

  1. AI / LLM tooling is a key priority that ENSNode is building infrastructure for.
  2. Next steps on our roadmap for this include enscli and ensskills. (link to each of the pages you created for these)
  3. Check back soon for even more detail on our roadmap for AI / LLM tooling for building on ENS.

label: "enscli (CLI)",
link: "/docs/integrate/integration-options/enscli",
},
{
label: "ensskills (AI agents)",
link: "/docs/integrate/integration-options/ensskills",
},
],
},
{
Expand Down
20 changes: 19 additions & 1 deletion docs/ensnode.io/src/content/docs/docs/integrate/ai-llm.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,26 @@ title: AI / LLM Tooling
description: AI and LLM tooling for building on ENSv2.
---

import { LinkCard } from "@astrojs/starlight/components";

:::caution[Coming Soon]
We're actively working on this page right now. Check back by May 18th for full content!
:::

This page will cover AI and LLM tooling for building on ENS — including llms.txt integration, Cursor skills, and Claude Code skills for ENS development.
AI and LLM tooling is a key priority for ENSNode, and we're building the infrastructure to make ENS a first-class citizen in the world of AI coding assistants and chat-based interfaces.

Next on the roadmap for this space are [`enscli`](/docs/integrate/integration-options/enscli) and [`ensskills`](/docs/integrate/integration-options/ensskills) — the foundation for how developers and their AI agents will reach for ENS.

<LinkCard
title="enscli"
description="An agent- and human-friendly CLI for the ENS Omnigraph API."
href="/docs/integrate/integration-options/enscli"
/>

<LinkCard
title="ensskills"
description="Skill bundles that give AI agents an opinionated contract for ENS."
href="/docs/integrate/integration-options/ensskills"
/>

Check back soon for more detail on our AI / LLM tooling roadmap.
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
title: enscli
description: Coming soon — an agent- and human-friendly CLI for the ENS Omnigraph API, wrapping enssdk.
---

import { Aside, LinkCard } from "@astrojs/starlight/components";

<Aside type="caution" title="Coming soon">
**`enscli`** is a planned ENS CLI that wraps [`enssdk`](/docs/integrate/integration-options/enssdk) to bring the ENS Omnigraph to the terminal. The npm name is reserved; we're still shaping the design. `enscli` will ship soon.
</Aside>

`enscli` will be the terminal-shaped entry point to the [ENS Omnigraph](/docs/integrate/omnigraph) — a single CLI for resolving names, looking up records, searching domains, and running ad-hoc queries against any ENSNode instance.

Designed to feel natural whether you're driving it yourself or letting an AI agent drive. From a terminal it's one `npx` away with sensible defaults against the public Omnigraph; for agents it's predictable arguments, structured output, and machine-readable help.

## Built for

- Developers exploring or validating an ENS integration from a terminal, without writing a script first.
- Operators wiring ENS lookups into shell pipelines, cron, or CI.
- AI coding agents driving [`ensskills`](/docs/integrate/integration-options/ensskills), which reach into the protocol through `enscli`.

## Related

<LinkCard
Comment thread
Goader marked this conversation as resolved.
title="enssdk"
description="The TypeScript SDK that enscli wraps."
href="/docs/integrate/integration-options/enssdk"
/>

<LinkCard
title="ensskills"
description="The agent-skill bundles that drive enscli on a developer's behalf."
href="/docs/integrate/integration-options/ensskills"
/>

<LinkCard
title="ENS Omnigraph API"
description="The underlying GraphQL API enscli speaks to."
href="/docs/integrate/omnigraph"
/>
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
title: ensskills
description: Coming soon — skill bundles that give AI agents an opinionated contract for ENS.
---

import { Aside, LinkCard } from "@astrojs/starlight/components";

<Aside type="caution" title="Coming soon">
**`ensskills`** is a planned collection of agent skills for ENS development and ENS lookups. The npm name is reserved; we're still shaping the design. `ensskills` will ship soon.
</Aside>

`ensskills` will be a small, curated set of skills that give AI coding agents — Claude Code, Cursor, Codex, and the rest — a well-defined contract for working with ENS. We want to support users who want a conversational interaction with ENS through their AI assistant, handled by skills that drive [`enscli`](/docs/integrate/integration-options/enscli) behind the scenes, and to streamline the developer experience writing integration code with [`enssdk`](/docs/integrate/integration-options/enssdk), [`enskit`](/docs/integrate/integration-options/enskit), or the raw [Omnigraph API](/docs/integrate/omnigraph).

Left to their own devices, agents love to reinvent the wheel from scratch every prompt — burning through your token budget rediscovering what ENS even is before they get around to the actual task. `ensskills` will be blueprints: focused, versioned bundles that hand the agent the right context for ENS work — no more, no less. The result is agents that produce ENS code that actually works, without the developer having to brief them from scratch every time.

## Built for

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

## Related

<LinkCard
title="enscli"
description="The CLI ensskills drives at runtime for ENS state lookups."
href="/docs/integrate/integration-options/enscli"
/>

<LinkCard
title="enssdk"
description="The TypeScript SDK ensskills teaches agents to author code against."
href="/docs/integrate/integration-options/enssdk"
/>

<LinkCard
title="enskit"
description="The React toolkit ensskills steers agents toward for UI work."
href="/docs/integrate/integration-options/enskit"
/>

<LinkCard
title="ENS Omnigraph API"
description="The GraphQL API behind all of the above."
href="/docs/integrate/omnigraph"
/>
Loading