feat: introduce enscli and ensskills

.changeset/datasources-identify-contracts.md

@@ -0,0 +1,5 @@
+---
+"@ensnode/datasources": patch
+---
+
+Add contract identification by address. `@ensnode/datasources` exports `identifyDatasourceContracts(namespaceId, query)`, which finds every well-known contract in a namespace's datasources whose address matches a given address, optionally scoped to a chain.

.changeset/enscli-datasources-identify.md

@@ -0,0 +1,5 @@
+---
+"enscli": patch
+---
+
+`enscli` gains `datasources identify <address>`: an offline command that reports which well-known ENS contract an address corresponds to. It accepts a bare address, a chain-scoped `chainId:address`, or full CAIP-10 `eip155:chainId:address`, and `--namespace` (default `mainnet`) selects which namespace to search. A miss returns `{ matches: [] }` with exit code `0`.

.changeset/enscli-initial.md

@@ -0,0 +1,5 @@
+---
+"enscli": patch
+---
+
+Introduce `enscli`, a new agent- and human-friendly CLI for ENS that wraps `enssdk` and the ENS Omnigraph. It supports raw Omnigraph queries (`enscli ensnode omnigraph "<query>" --variables …`), offline schema exploration (`enscli ensnode omnigraph schema [Type[.field]]`), indexing status, ENSRainbow healing, and `namehash`/`labelhash`. It defaults to NameHash-hosted instances per `--namespace` (mainnet, sepolia, sepolia-v2), resolves config from flags/env/`.env`, outputs JSON when piped and a pretty form in a TTY, and hardens inputs against agent hallucinations.

.changeset/ensnode-sdk-sepolia-v2-default.md

@@ -0,0 +1,5 @@
+---
+"@ensnode/ensnode-sdk": patch
+---
+
+`getDefaultEnsNodeUrl` now returns the hosted default for the `sepolia-v2` namespace (`https://api.v2-sepolia.ensnode.io`).

.changeset/ensskills-datasources-identify.md

@@ -0,0 +1,5 @@
+---
+"ensskills": patch
+---
+
+The `enscli` agent skill documents the new `datasources identify` command.

.changeset/ensskills-initial.md

@@ -0,0 +1,5 @@
+---
+"ensskills": patch
+---
+
+Introduce `ensskills`, a versioned, `skills-npm`-installable package of ENS agent skills. It ships the `ens-protocol` skill (a concise, stable, vendor-neutral conceptual model of the ENS protocol — nametree, normalization, hashing, registry/resolver/registrar, resolution, records, multichain — with pull-as-needed reference pages), the `omnigraph` skill (autogenerated schema reference + vetted example queries, plus prose on the unified ENSv1+ENSv2 datamodel and resolution), and the `enscli` skill (running Omnigraph queries and the other CLI commands, with the output contract, namespace/URL resolution, and input hardening), with stub skills reserved for `enssdk`, `enskit`, `migrate-to-omnigraph`, and `unigraph-sql`.

.changeset/ensskills-llms-txt-link.md

@@ -0,0 +1,5 @@
+---
+"ensskills": patch
+---
+
+Point the base skill at the published `llms.txt` / `llms-full.txt` docs endpoints so agents can load the full ENSNode documentation when a question reaches beyond the skills.

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 NameHash
+Copyright (c) 2026 NameHash Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

apps/ensadmin/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 NameHash
+Copyright (c) 2026 NameHash Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

apps/ensapi/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 NameHash
+Copyright (c) 2026 NameHash Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

apps/ensapi/src/omnigraph-api/schema/domain.ts

@@ -145,7 +145,7 @@ DomainInterfaceRef.implement({
     owner: t.field({
       type: AccountRef,
       description:
-        "If this is an ENSv1Domain, this is the effective owner of the Domain. If this is an ENSv2Domain, this is the on-chain owner address (the HCA account address if used).",
+        "If this is an ENSv1Domain, this is the effective owner of the Domain (derived from the Registry, the Registrar, or the NameWrapper, in that order). If this is an ENSv2Domain, this is the on-chain owner address (the HCA account address if used).",
       nullable: true,
       resolve: (parent) => parent.ownerId,
     }),
@@ -279,7 +279,7 @@ DomainInterfaceRef.implement({
     // Domain.subdomains
     /////////////////////
     subdomains: t.connection({
-      description: "All Domains that are direct descendents of this Domain in the namegraph.",
+      description: "All Domains that are direct descendants of this Domain in the namegraph.",
       type: DomainInterfaceRef,
       args: {
         where: t.arg({ type: SubdomainsWhereInput }),

apps/ensindexer/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 NameHash
+Copyright (c) 2026 NameHash Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

apps/ensrainbow/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 NameHash
+Copyright (c) 2026 NameHash Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

apps/fallback-ensapi/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 NameHash
+Copyright (c) 2026 NameHash Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

docs/ensnode.io/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 NameHash
+Copyright (c) 2026 NameHash Inc.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

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

@@ -26,6 +26,10 @@ export const integrateSidebarTopic = {
         },
       ],
     },
+    {
+      label: "AI/LLM Tooling 🤖",
+      link: "/docs/integrate/ai-llm",
+    },
     {
       label: "ENS Subgraph",
       collapsed: false,
@@ -236,9 +240,5 @@ export const integrateSidebarTopic = {
         },
       ],
     },
-    {
-      label: "AI / LLM Tooling",
-      link: "/docs/integrate/ai-llm",
-    },
   ],
 };

docs/ensnode.io/src/components/molecules/HostedInstanceVersionWarning.astro

@@ -0,0 +1,53 @@
+---
+import { Aside } from "@astrojs/starlight/components";
+
+import snapshot from "@data/omnigraph-examples/snapshot.json";
+// TEMP prerelease: enscli/ensskills aren't published at `snapshot.sdkVersion` yet — remove at the
+// first official release (see @data/enscli-ensskills-prerelease).
+import { ENSCLI_ENSSKILLS_NPM_SPEC } from "@data/enscli-ensskills-prerelease";
+
+// The ENSNode suite is version-locked to the production-deployed Omnigraph (see the vendored
+// `@data/omnigraph-examples/snapshot.json`). The SDK bundles the Omnigraph schema (consumed by the
+// `gql.tada` TypeScript plugin) and `ensskills` bundles the schema plus example queries, so pinning
+// the matching version keeps generated types / agent knowledge aligned with the deployed API.
+interface Props {
+  // "sdk" warns about pinning enssdk/enskit for gql.tada types; "skills" warns about pinning
+  // ensskills/enscli for agent knowledge.
+  variant: "sdk" | "skills";
+}
+
+const { variant } = Astro.props;
+const VERSION = snapshot.sdkVersion;
+---
+
+<Aside type="caution" title="Version compatibility with hosted instances">
+  <a href="/docs/hosted-instances">Our hosted ENSNode instances</a> currently run ENSNode <code
+    >{VERSION}</code
+  >.{" "}
+  {
+    variant === "sdk" ? (
+      <Fragment>
+        The Omnigraph GraphQL schema is bundled inside the SDK and consumed by the{" "}
+        <code>gql.tada</code> TypeScript plugin to type your queries, so pin an{" "}
+        <strong>exact</strong> version (no <code>^</code> or <code>~</code>) of{" "}
+        <code>enssdk@{VERSION}</code> (and <code>enskit@{VERSION}</code> when using React) to keep
+        your generated types matched to the deployed schema. Use these exact install commands:
+        <pre>{`npm install enssdk@${VERSION}
+# or, for React apps:
+npm install enskit@${VERSION} enssdk@${VERSION}`}</pre>
+      </Fragment>
+    ) : (
+      <Fragment>
+        <code>ensskills</code> is version-locked to the ENSNode suite—the Omnigraph schema and
+        example queries the skills teach are bundled at a specific version—so you pin{" "}
+        <code>ensskills</code> and the matching <code>enscli</code> to keep your agent's ENS
+        knowledge and queries matched to the deployed API.{" "}
+        {/* TEMP prerelease: revert to pinning both at <code>{VERSION}</code> at the first official release */}
+        These two packages are newer than the deployed <code>{VERSION}</code> release, so until
+        their first official release install them from the prerelease tag—
+        <code>ensskills@{ENSCLI_ENSSKILLS_NPM_SPEC}</code> and{" "}
+        <code>enscli@{ENSCLI_ENSSKILLS_NPM_SPEC}</code>.
+      </Fragment>
+    )
+  }
+</Aside>

docs/ensnode.io/src/components/molecules/IntegrateHostedEnsNodeTip.astro

@@ -1,11 +1,11 @@
 ---
 import { Aside, LinkCard } from "@astrojs/starlight/components";
-import HostedInstanceSdkVersionWarning from "./HostedInstanceSdkVersionWarning.astro";
+import HostedInstanceVersionWarning from "./HostedInstanceVersionWarning.astro";
 ---
 
 <Aside type="tip" title="No backend required">
   You don't need to run your own ENSNode to follow this guide — the steps below default to a
   NameHash-hosted instance. Browse the available deployments below.
 </Aside>
-<HostedInstanceSdkVersionWarning />
+<HostedInstanceVersionWarning variant="sdk" />
 <LinkCard title="Hosted ENSNode Instances" href="/docs/hosted-instances" />

docs/ensnode.io/src/content/docs/docs/hosted-instances.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { LinkCard } from "@astrojs/starlight/components";
 import HostedEnsNodeInstance from "@components/molecules/HostedEnsNodeInstance.astro";
-import HostedInstanceSdkVersionWarning from "@components/molecules/HostedInstanceSdkVersionWarning.astro";
+import HostedInstanceVersionWarning from "@components/molecules/HostedInstanceVersionWarning.astro";
 import EnsSubgraphCorrectnessPostEnsV2Launch from "@components/molecules/EnsSubgraphCorrectnessPostEnsV2Launch.astro";
 
 export const subgraphCompatibilityApiLevel = `<em>API-level Subgraph Compatibility.</em> This ENSNode instance has a fully backwards compatible ENS Subgraph GraphQL API. However, additional plugins have been activated which index a superset of data into the subgraph data model in ENSDb. This superset of indexed data means that the data returned for some ENS Subgraph API queries may be different.`;
@@ -24,7 +24,7 @@ NameHash Labs provides hosted instances of ENSNode for developers building on EN
 
 These instances are currently provided free of charge with no API key required, have no rate limiting, and are maintained and monitored by the NameHash Labs team.
 
-<HostedInstanceSdkVersionWarning />
+<HostedInstanceVersionWarning variant="sdk" />
 
 ### ENS Namespaces
 

docs/ensnode.io/src/content/docs/docs/integrate/ai-llm.mdx

@@ -3,11 +3,57 @@ title: AI / LLM Tooling
 description: AI and LLM tooling for building on ENSv2.
 ---
 
-import { LinkCard } from "@astrojs/starlight/components";
+import { Code, LinkCard } from "@astrojs/starlight/components";
+// TEMP prerelease: enscli/ensskills install pins — remove at first official release (see enscli-ensskills-prerelease.ts)
+import { ENSCLI_ENSSKILLS_NPM_SPEC, ENSCLI_ENSSKILLS_GIT_REF } from "@data/enscli-ensskills-prerelease";
+import HostedInstanceVersionWarning from "@components/molecules/HostedInstanceVersionWarning.astro";
 
-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.
+We're building the infrastructure to make ENS a first-class citizen for AI agents.
 
-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.
+The foundation for how developers and their AI agents reach for ENS is [`ensskills`](/docs/integrate/integration-options/ensskills), that teach your AI assistant about ENS, ENSNode, the ENS Omnigraph, and how to drive [`enscli`](/docs/integrate/integration-options/enscli) — an agent- and human-friendly CLI — on your behalf.
+
+<HostedInstanceVersionWarning variant="skills" />
+
+## Quickstart (`npm`/`pnpm`/`yarn`/`bun`)
+
+Add `ensskills` and [`skills-npm`](https://github.com/antfu/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:
+
+<Code
+  lang="jsonc"
+  code={`// package.json
+  {
+    "devDependencies": {
+      "ensskills": "${ENSCLI_ENSSKILLS_NPM_SPEC}",
+      "skills-npm": "^1"
+    },
+    "scripts": {
+      "prepare": "skills-npm"
+    }
+  }
+`}
+/>
+
+```bash
+npm install   # symlinks the skills for your detected agents
+```
+
+## Quickstart (`npx skills`)
+
+Not in a Node project? [`skills`](https://github.com/vercel-labs/skills) installs every ENS skill straight from the repo. It normally pins to the matching `v…` release tag; during the current prerelease window it tracks `main` until `enscli`/`ensskills` ship in their first official release:
+
+<Code
+  lang="bash"
+  code={`npx skills add https://github.com/namehash/ensnode/tree/${ENSCLI_ENSSKILLS_GIT_REF}/packages/ensskills/skills --skill '*'`}
+/>
+
+## Next Steps
+
+That's it — your AI agent now has all of [`ensskills`](/docs/integrate/integration-options/ensskills) at its disposal.
+
+```md title=prompt.md
+Which address currently owns vitalik.eth
+and how many other domains do they own?
+```
 
 <LinkCard
   title="enscli"
@@ -21,4 +67,15 @@ Next on the roadmap for this space are [`enscli`](/docs/integrate/integration-op
   href="/docs/integrate/integration-options/ensskills"
 />
 
-Check back soon for more detail on our AI / LLM tooling roadmap.
+## Documentation as `llms.txt`
+
+If you aren't using `ensskills`, the entire documentation site is also published in the [`llms.txt`](https://llmstxt.org/) format so any agent or LLM can load it directly as context:
+
+- [`/llms.txt`](https://ensnode.io/llms.txt) — a structured index of the documentation with links to every page.
+- [`/llms-full.txt`](https://ensnode.io/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:
+
+```md title="prompt.md"
+Load the ENSNode documentation from https://ensnode.io/llms-full.txt to answer the following question:
+```

docs/ensnode.io/src/content/docs/docs/integrate/ens-subgraph/key-limitations.mdx

@@ -128,7 +128,7 @@ The Subgraph schema spreads ownership across multiple fields — `owner`, `regis
 :::
 
 :::tip[One effective owner field]
-In the [Omnigraph API](/docs/integrate/omnigraph) `Domain.owner` is _always_ the effective owner's address—no weird edge-cases! For ENSv2 Domains, `Domain.owner` is Smart-Account-aware and represents the true owner of the Domain at a given time.
+In the [Omnigraph API](/docs/integrate/omnigraph) `Domain.owner` is _always_ the effective owner's address — no weird edge-cases! For ENSv2 Domains, `Domain.owner` is Smart-Account-aware and represents the true owner of the Domain at a given time.
 :::
 
 ## Missing all offchain ENS names