mcpField
K
k-skill-setup

k-skill-setup

github.com/nomadamasAgent workflows8.2k8.7k installsUpdated 1d ago
Repository

About k-skill-setup

A skill that directs coding agents to load current setup instructions through the k-skill CLI. It also sets safety rules for sensitive actions, credentials, and verification boundaries.

Key features

  1. 01Fetch runtime-specific instructions
  2. 02List bundled helper files
  3. 03Update the CLI and installed skills
  4. 04Require approval for consequential actions
  5. 05Protect credentials and verification boundaries

Use cases

  1. 01Set up a coding-agent skill for the current runtime
  2. 02Refresh skill and CLI instructions
  3. 03Check safety limits before acting on external services

Install

Copy the command and run it in a terminal.

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

After installing, type/k-skill-setupin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
check-setup.sh

Details

From the project README

k-skill-setup

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 k-skill-setup

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 k-skill-setup

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/k-skill-setup/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