mcpField
A
assembly-bill-vote-search

assembly-bill-vote-search

github.com/nomadamasOther8.2k4.7k installsUpdated 2d ago
Repository

About assembly-bill-vote-search

A coding-agent skill for searching assembly bill votes. Its README directs users to retrieve runtime-specific instructions through the k-skill CLI and sets boundaries around sensitive actions and credentials.

Key features

  1. 01Runtime-specific instructions via CLI
  2. 02Lists bundled helper files
  3. 03Safety rules for sensitive actions

Use cases

  1. 01Look up assembly bill votes with the skill
  2. 02Check applicable instructions for the current runtime

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill assembly-bill-vote-search

After installing, type/assembly-bill-vote-searchin Claude Code to confirm it loaded.

Bundled filesinstruction.mdskill.json

Details

From the project README

assembly-bill-vote-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 assembly-bill-vote-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 assembly-bill-vote-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/assembly-bill-vote-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