base

Define foundational conventions for ENS skills using Omnigraph and enssdk.

41|19|Updated Dec 23, 2024
One-click install
npx skills add https://github.com/namehash/ensnode --skill base-namehash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: base
Source: https://github.com/namehash/ensnode/tree/main/packages/ensskills/skills/base
Command: npx skills add https://github.com/namehash/ensnode --skill base-namehash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ENS skill ecosystem benefits from a shared foundation; this skill defines the core conventions that govern how skills interact with Omnigraph, enssdk, and the Terminology Reference, ensuring consistent, safe flows.

Core Features & Use Cases

  • Establishes default data reading through Omnigraph and discourages raw contract calls.
  • Recommends using enssdk for name handling, normalization, and hashing to avoid common errors.
  • Aligns user-facing language with the ENSNode Terminology Reference to avoid ambiguity.
  • Serves as a first-load baseline that other skills depend on.

Quick Start

Load this skill first to establish the foundational conventions for all ENS skills.

Frequently Asked Questions about base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are ENS conventions for standardizing skill reads and naming?

ENS conventions standardize skill reads and naming by defining default data reading through Omnigraph, using enssdk for name handling, and aligning language with the ENSNode Terminology Reference to ensure consistent user-facing interactions.

Do I need to load foundational ENS conventions before using other ENS skills?

Yes, you should load foundational ENS conventions first to establish a baseline. Other ENS skills depend on these conventions to interact safely with Omnigraph, enssdk, and the Terminology Reference without encountering common errors.

How do I structure an ENS skill using the enssdk and Omnigraph conventions?

Structure an ENS skill by creating a SKILL.md entry point with a YAML frontmatter containing name and description. You can then add optional scripts, references, and assets for extended guidance while following the enssdk and Omnigraph conventions.

Why does my ENS skill encounter normalization errors when using raw contract calls?

ENS skills encounter normalization errors with raw contract calls because the conventions discourage them. The foundational guidelines recommend using enssdk for name handling, normalization, and hashing to avoid these common errors.

What is the ENSNode Terminology Reference used for in ENS skills?

The ENSNode Terminology Reference is used to align user-facing language in ENS skills. It defines Node terminology and ensures consistent communication across the Omnigraph usage and enssdk primitives, avoiding ambiguity.

Can I use enssdk primitives directly without following the ENS skill conventions?

While you can use enssdk primitives directly, following ENS skill conventions is recommended. The conventions establish enssdk as the standard for name handling and hashing, ensuring safe flows and avoiding common implementation errors.