mcpField
B
bok-ecos-stats

bok-ecos-stats

github.com/nomadamasData & databases8.2k4.5k installsUpdated 1d ago
Repository

About bok-ecos-stats

bok-ecos-stats is a coding-agent skill whose full, runtime-specific instructions are retrieved through the k-skill CLI. It is intended for BOK ECOS statistics tasks and includes safeguards for consequential actions, credentials, and restricted procedures.

Key features

  1. 01Runtime-specific skill instructions
  2. 02CLI access to helper-file listings
  3. 03CLI update command
  4. 04Approval required for consequential actions
  5. 05Credential and boundary safeguards

Use cases

  1. 01Working with BOK ECOS statistics
  2. 02Checking applicable instructions for a runtime
  3. 03Keeping installed skill instructions current

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill bok-ecos-stats

After installing, type/bok-ecos-statsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
bok_ecos.py
tests/
test_bok_ecos.py

Details

From the project README

bok-ecos-stats

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 bok-ecos-stats

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 bok-ecos-stats

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/bok-ecos-stats/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