How do I install the Did Auth Agent skill?

Run npx skillmds@latest add tomevault-io/did-auth-agent in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Did Auth Agent safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Did Auth Agent?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Did Auth Agent free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Did Auth Agent?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Did Auth Agent by tomevault-io — Agent Skill

Name: Did Auth Agent
Author: tomevault-io

Did Auth Agent

Use `nuwa-id` (from identity-kit) to run a DIDAuth flow on `id.nuwa.dev`. The agent generates a key locally, sends a deep link to the user, asks user to return DID text, verifies key binding, then sends authenticated HTTP requests. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

DID Auth Agent Skill (CLI-first)

This skill is for agent environments where user and agent are on different devices and callback-to-localhost is not possible.

Prerequisites

Node.js >= 18
nuwa-id CLI available
Rooch mainnet + CADOP main domain (id.nuwa.dev)

Install `nuwa-id`

npm i -g @nuwa-ai/identity-kit
nuwa-id help

Commands

1) Initialize local key and config

nuwa-id init --key-fragment support-agent-main

This creates local state under:

~/.config/nuwa-did/config.json
~/.config/nuwa-did/keys/default.json

Optional: create additional profiles and switch active profile:

nuwa-id profile create --name support-b --key-fragment support-agent-b
nuwa-id profile use --name support-b
nuwa-id profile list

If --key-fragment is not provided, nuwa-id generates a timestamp-based fragment. Use an explicit, human-readable fragment for easier debugging and operations.

2) Create deep link and send it to user

nuwa-id link

Send the printed URL to the user.
The user opens it in browser and approves adding your key to their DID authentication set.

3) Ask user to return DID text

User sends DID back, for example:

did:rooch:rooch1...

4) Persist DID into local config

Save DID into ~/.config/nuwa-did/config.json:

nuwa-id set-did --did did:rooch:rooch1...

5) Verify key binding on DID document

nuwa-id verify

Only continue if verification succeeds.

6) Send DID-authenticated request

Option A: generate header only

nuwa-id auth-header \
  --method GET \
  --url https://did-check.nuwa.dev/whoami

Option B: send request directly

nuwa-id curl \
  --method GET \
  --url https://did-check.nuwa.dev/whoami

Notes

Default network is main.
Default CADOP domain is https://id.nuwa.dev.
Key fragment comes from active profile config after nuwa-id init.
Private key never leaves ~/.config/nuwa-did/keys.

Source: nuwa-protocol/nuwa — distributed by TomeVault.

---name: did-auth-agentdescription: Use `nuwa-id` (from identity-kit) to run a DIDAuth flow on `id.nuwa.dev`. The agent generates a key locally, sends a deep link to the user, asks user to return DID text, verifies key binding, then sends authenticated HTTP requests. Use when this capability is needed.---# DID Auth Agent Skill (CLI-first)This skill is for agent environments where user and agent are on different devices and callback-to-localhost is not possible.## Prerequisites- Node.js >= 18- `nuwa-id` CLI available- Rooch mainnet + CADOP main domain (`id.nuwa.dev`)## Install `nuwa-id````bashnpm i -g @nuwa-ai/identity-kitnuwa-id help```## Commands### 1) Initialize local key and config```bashnuwa-id init --key-fragment support-agent-main```This creates local state under:- `~/.config/nuwa-did/config.json`- `~/.config/nuwa-did/keys/default.json`Optional: create additional profiles and switch active profile:```bashnuwa-id profile create --name support-b --key-fragment support-agent-bnuwa-id profile use --name support-bnuwa-id profile list```If `--key-fragment` is not provided, `nuwa-id` generates a timestamp-based fragment.Use an explicit, human-readable fragment for easier debugging and operations.### 2) Create deep link and send it to user```bashnuwa-id link```Send the printed URL to the user. The user opens it in browser and approves adding your key to their DID authentication set.### 3) Ask user to return DID textUser sends DID back, for example:```textdid:rooch:rooch1...```### 4) Persist DID into local configSave DID into `~/.config/nuwa-did/config.json`:```bashnuwa-id set-did --did did:rooch:rooch1...```### 5) Verify key binding on DID document```bashnuwa-id verify```Only continue if verification succeeds.### 6) Send DID-authenticated requestOption A: generate header only```bashnuwa-id auth-header \ --method GET \ --url https://did-check.nuwa.dev/whoami```Option B: send request directly```bashnuwa-id curl \ --method GET \ --url https://did-check.nuwa.dev/whoami```## Notes- Default network is `main`.- Default CADOP domain is `https://id.nuwa.dev`.- Key fragment comes from active profile config after `nuwa-id init`.- Private key never leaves `~/.config/nuwa-did/keys`.---> Source: [nuwa-protocol/nuwa](https://github.com/nuwa-protocol/nuwa) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions