mcpField
B
biz-health-check

biz-health-check

github.com/nomadamasOther8.2k5.4k installsUpdated 2d ago
Repository

About biz-health-check

biz-health-check is a coding-agent skill that provides instructions for business health checks. It uses a CLI to select instructions for the current runtime and sets boundaries for sensitive actions and credentials.

Key features

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

Use cases

  1. 01Preparing a business health check
  2. 02Reviewing permitted actions before acting

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill biz-health-check

After installing, type/biz-health-checkin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
biz_health_check.py

Details

From the project README

biz-health-check

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 biz-health-check

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 biz-health-check

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/biz-health-check/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