mcpField
H
heyyumi

heyyumi

github.com/nomadamasOther8.2k681 installsUpdated 2d ago
Repository

About heyyumi

heyyumi is a coding-agent skill whose required first step is to fetch runtime-specific instructions through its CLI. It also sets boundaries for sensitive actions, credentials, and legal or identity checks.

Key features

  1. 01Runtime-specific instructions via CLI
  2. 02CLI command to list helper files
  3. 03CLI update command
  4. 04Approval required for sensitive actions
  5. 05Credential and verification safeguards

Use cases

  1. 01Loading applicable instructions for a runtime
  2. 02Reviewing bundled skill helper files
  3. 03Updating installed skills and CLI
  4. 04Preventing 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 heyyumi

After installing, type/heyyumiin Claude Code to confirm it loaded.

Bundled filesinstruction.mdskill.json

Details

From the project README

heyyumi

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 heyyumi

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 heyyumi

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/heyyumi/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