mcpField
H
highway-traffic-status

highway-traffic-status

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

About highway-traffic-status

A coding-agent skill named for highway traffic status. Its README explains how to load up-to-date instructions and states general safety boundaries, without detailing traffic-status functions.

Key features

  1. 01CLI-delivered instructions
  2. 02Runtime-specific guidance
  3. 03Helper-file listing
  4. 04Explicit approval for sensitive actions

Use cases

  1. 01Loading current skill instructions
  2. 02Checking helper files available to the skill

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill highway-traffic-status

After installing, type/highway-traffic-statusin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
highway_traffic.py
tests/
test_highway_traffic.py

Details

From the project README

highway-traffic-status

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 highway-traffic-status

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 highway-traffic-status

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/highway-traffic-status/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