ens-manager

Automate ENS name registration, subdomain creation, and IPFS website publishing.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Zeugh-eth/ens-manager --skill ens-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ens-manager
Source: https://github.com/Zeugh-eth/ens-manager/tree/main
Command: npx skills add https://github.com/Zeugh-eth/ens-manager --skill ens-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires viem, content-hash, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complete ENS workflow from registration to publishing, reducing manual steps and coordination across tools.

Core Features & Use Cases

  • Registers new .eth names using a three-phase process (commitment → 60s wait → register) to prevent frontrunning.
  • Creates subdomains for owned ENS names, handling both wrapped and unwrapped types, and optionally attaches IPFS content hashes.
  • Publishes static websites by binding IPFS content to subdomains and serving via gateways like eth.limo and eth.link.
  • Use case: A project owner wants to register a name, create api and docs subdomains, and publish a site to IPFS with a single workflow.

Quick Start

Run the three core commands to register a name, create a subdomain, and publish IPFS content.

Frequently Asked Questions about ens-manager

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

FAQPage Schema
How do I automate ENS registration and IPFS publishing in a single workflow?

You can automate the complete ENS workflow from registration to IPFS publishing by running a script that handles the three-phase commitment process, subdomain creation, and IPFS content hash binding without manual intervention.

Why does ENS registration require a commitment and wait period?

ENS registration uses a three-phase process—commitment, a 60-second wait, and final registration—to prevent frontrunning. This delay ensures your name registration request is secure before executing the transaction on-chain.

Do I need Node.js and specific libraries to manage ENS subdomains?

Yes, you need Node.js 18+ and the viem library. Optional content-hash library support is required if you want to attach IPFS content hashes to your subdomains for decentralized website publishing.

Can I publish a static website to IPFS and serve it via ENS subdomains?

Yes, you can bind IPFS content hashes to ENS subdomains to publish static websites. The published content is then accessible through decentralized gateways like eth.limo and eth.link.

Does ENS subdomain automation work with both wrapped and unwrapped names?

Yes, the automation supports creating subdomains for both wrapped and unwrapped ENS name types. You can optionally attach IPFS content hashes during the subdomain creation process.

What are the prerequisites for running an automated ENS workflow?

You need a keystore or wallet access for transaction signing and ETH for gas fees. The environment requires Node.js 18+, viem, and optionally content-hash for IPFS features.