mcpField
K
komsa-ferry-info

komsa-ferry-info

github.com/nomadamasOther8.2k3.3k installsUpdated 2d ago
Repository

About komsa-ferry-info

komsa-ferry-info is a skill whose CLI provides runtime-specific instructions for ferry information lookup. Its README also states rules for consequential actions, credentials, and avoiding legal or verification safeguards.

Key features

  1. 01Runtime-specific instructions
  2. 02CLI access to helper files
  3. 03Approval required for consequential actions
  4. 04Credential and safeguard restrictions

Use cases

  1. 01Looking up ferry information
  2. 02Checking which skill instructions apply to a runtime

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill komsa-ferry-info

After installing, type/komsa-ferry-infoin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
komsa_ferry_info.py

Details

From the project README

komsa-ferry-info

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 komsa-ferry-info

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 komsa-ferry-info

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/komsa-ferry-info/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