mcpField
I
iros-registry-automation

iros-registry-automation

github.com/nomadamasDocuments8.2k6.5k installsUpdated 2d ago
Repository

About iros-registry-automation

iros-registry-automation is a skill for registry-related tasks, with instructions delivered by a CLI according to the runtime. It emphasizes approval for consequential actions and limits around credentials and legal or identity checks.

Key features

  1. 01Runtime-specific instructions via CLI
  2. 02Lists bundled helper files
  3. 03Requires approval for consequential actions
  4. 04Protects credentials and verification boundaries

Use cases

  1. 01Retrieve applicable registry task instructions
  2. 02Review helper files bundled with the skill

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill iros-registry-automation

After installing, type/iros-registry-automationin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
iros_pdf_summary.py
upstream.pin
tests/
test_iros_pdf_summary.py

Details

From the project README

iros-registry-automation

Get the full instructions (required first step)

Run this and follow its output as the primary instructions for this skill:

npx -y @nomadamas/k-skill@0 instruct iros-registry-automation

The CLI detects the current runtime (Dolshoi vault/CloakBrowser vs generic) and prints only the applicable instructions, always up to date. Helper files bundled with the CLI are listed by:

npx -y @nomadamas/k-skill@0 files iros-registry-automation

Keep the CLI and every coding-agent skill install current (including Vercel Agent Skills) with:

npx -y @nomadamas/k-skill@0 update

If npx is unavailable, install Node.js 18+ or follow https://github.com/NomaDamas/k-skill#readme, or read the source instructions at https://github.com/NomaDamas/k-skill/blob/main/iros-registry-automation/instruction.md.

Hard rules even without the CLI

  • Never execute payment, message/email delivery, final submission, cancellation, or public posting without the user's explicit approval immediately beforehand.
  • Never ask for, print, or store plaintext credentials in chat, files, or shell arguments.
  • Never bypass legal, physical-presence, CAPTCHA, identity-proofing, or electronic-signature boundaries.

Comments

Markdown supported