mcpField
S
seoul-bike

seoul-bike

github.com/nomadamasOther8.2k5.6k installsUpdated 2d ago
Repository

About seoul-bike

seoul-bike is a skill that directs an agent to retrieve current, runtime-specific instructions through the k-skill CLI. It also sets boundaries for sensitive actions, credentials, and legal or identity checks.

Key features

  1. 01Runtime-specific instructions via CLI
  2. 02Lists bundled helper files
  3. 03Updates the CLI and installed skills
  4. 04Requires approval for sensitive actions
  5. 05Protects credentials and verification boundaries

Use cases

  1. 01Loading current Seoul Bike skill instructions
  2. 02Checking which helper files are available
  3. 03Updating the CLI and installed skills
  4. 04Reviewing safeguards before sensitive actions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill seoul-bike

After installing, type/seoul-bikein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
seoul_bike.py

Details

From the project README

seoul-bike

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 seoul-bike

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 seoul-bike

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/seoul-bike/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