mcpField
L
localdata-business-status

localdata-business-status

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

About localdata-business-status

A skill for business-status tasks that loads runtime-specific instructions through the k-skill CLI. It also sets safeguards for sensitive actions, credentials, and legal or verification boundaries.

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. 01Loading current instructions for business-status tasks
  2. 02Checking which helper files are available
  3. 03Reviewing safeguards before interacting with business services

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill localdata-business-status

After installing, type/localdata-business-statusin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
data/
localdata_industries.json
localdata_orgcodes.json
scripts/
localdata_business_status.py

Details

From the project README

localdata-business-status

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 localdata-business-status

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 localdata-business-status

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/localdata-business-status/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