mcpField
G
g2b-order-plan-search

g2b-order-plan-search

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

About g2b-order-plan-search

A coding-agent skill for searching G2B order plans. Its README points to a CLI for current instructions and sets boundaries around sensitive actions and credentials.

Key features

  1. 01CLI-provided current instructions
  2. 02Runtime-specific instruction selection
  3. 03Helper-file listing
  4. 04Approval required for sensitive actions
  5. 05Credential and verification safeguards

Use cases

  1. 01Finding G2B order plans
  2. 02Checking applicable skill instructions
  3. 03Avoiding unapproved submissions or payments

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill g2b-order-plan-search

After installing, type/g2b-order-plan-searchin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
g2b_order_plan.py

Details

From the project README

g2b-order-plan-search

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 g2b-order-plan-search

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 g2b-order-plan-search

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/g2b-order-plan-search/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