mcpField
N
naming-house

naming-house

github.com/nomadamasCreative & media8.2k4.9k installsUpdated 1d ago
Repository

About naming-house

A creative naming skill whose README directs users to a CLI for its full, current instructions. It also sets safeguards for credentials and actions such as payments or public posting.

Key features

  1. 01CLI-provided current instructions
  2. 02Runtime-specific instruction selection
  3. 03Helper-file listing
  4. 04Approval required for sensitive actions
  5. 05Credential and verification safeguards

Use cases

  1. 01Checking applicable naming instructions
  2. 02Following skill-specific guidance
  3. 03Avoiding unapproved payments or public posts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill naming-house

After installing, type/naming-housein Claude Code to confirm it loaded.

Bundled filesinstruction.mdskill.json

Details

From the project README

naming-house

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 naming-house

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 naming-house

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/naming-house/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