mcpField
K
k-schoollunch-menu

k-schoollunch-menu

github.com/nomadamasOther8.2k7.1k installsUpdated 2d ago
Repository

About k-schoollunch-menu

k-schoollunch-menu is a coding-agent skill whose current instructions are retrieved through the k-skill CLI. Its README provides safety rules, but does not describe the school-lunch menu task itself.

Key features

  1. 01Runtime-specific instructions via CLI
  2. 02Lists bundled helper files
  3. 03Updates the CLI and skill installs
  4. 04Approval required for consequential actions
  5. 05Protects credentials and verification boundaries

Use cases

  1. 01Loading current instructions for k-schoollunch-menu
  2. 02Checking available helper files
  3. 03Updating installed skills and CLI

Install

Copy the command and run it in a terminal.

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

After installing, type/k-schoollunch-menuin Claude Code to confirm it loaded.

Bundled filesinstruction.mdskill.json

Details

From the project README

k-schoollunch-menu

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-schoollunch-menu

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-schoollunch-menu

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-schoollunch-menu/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