mcpField
L
library-book-search

library-book-search

github.com/nomadamasProductivity8.2k6.8k installsUpdated 2d ago
Repository

About library-book-search

library-book-search is a skill whose current, runtime-specific instructions are fetched through the k-skill CLI. The README describes safety rules for sensitive actions, credentials, and verification boundaries.

Key features

  1. 01Fetches current skill instructions
  2. 02Adapts instructions to runtime
  3. 03Lists bundled helper files
  4. 04Defines action and credential safeguards

Use cases

  1. 01Load search skill instructions for the current runtime
  2. 02Review safeguards before sensitive actions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill library-book-search

After installing, type/library-book-searchin Claude Code to confirm it loaded.

Bundled filesinstruction.mdskill.json

Details

From the project README

library-book-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 library-book-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 library-book-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/library-book-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