mcpField
E
ev-charger-nearby

ev-charger-nearby

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

About ev-charger-nearby

ev-charger-nearby is a skill whose instructions are supplied through the k-skill CLI. The README provides setup commands and safeguards, but does not describe its search capabilities or data sources.

Key features

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

Use cases

  1. 01Loading the skill's current instructions
  2. 02Reviewing safety limits before use

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill ev-charger-nearby

After installing, type/ev-charger-nearbyin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
ev_charger.py
tests/
test_ev_charger.py

Details

From the project README

ev-charger-nearby

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 ev-charger-nearby

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 ev-charger-nearby

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/ev-charger-nearby/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