docs: enscli and ensskills docs

docs/ensnode.io/config/integrations/starlight/sidebar-topics/integrate.ts

@@ -61,6 +61,14 @@ export const integrateSidebarTopic = {
           label: "ENSDb (PostgreSQL)",
           link: "/docs/integrate/integration-options/ensdb",
         },
+        {
+          label: "enscli",
+          link: "/docs/integrate/integration-options/enscli",
+        },
+        {
+          label: "ensskills",
+          link: "/docs/integrate/integration-options/ensskills",
+        },
       ],
     },
     {

docs/ensnode.io/src/content/docs/docs/integrate/integration-options/enscli.mdx

@@ -0,0 +1,44 @@
+---
+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 and no commands ship yet.
+</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`.
+
+<Aside type="note" title="Looking for `ensdb-cli`?">
+`ensdb-cli` is a separate planned tool — an operator-focused CLI for managing [ENSDb](/docs/services/ensdb) instances, snapshots, and schemas. `enscli` is for *querying* ENS; `ensdb-cli` is for *operating* the database that ENS is indexed into. See [ENSDb snapshots & CLI](/docs/integrate/ensdb-snapshots-and-cli).
+</Aside>
+
+## Related
+
+<LinkCard
+  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"
+/>

docs/ensnode.io/src/content/docs/docs/integrate/integration-options/ensskills.mdx

@@ -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 and no skills ship yet.
+</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"
+/>