mcpField
K
korean-marathon-schedule

korean-marathon-schedule

github.com/nomadamasProductivity8.2k6.0k installsUpdated 2d ago
Repository

About korean-marathon-schedule

korean-marathon-schedule is a productivity skill that provides task instructions through a CLI. It selects guidance for the current runtime; the README does not detail the schedule data or operations it supports.

Key features

  1. 01Runtime-specific instructions
  2. 02CLI access to helper-file listings
  3. 03CLI and skill update command
  4. 04Explicit approval and credential safeguards

Use cases

  1. 01Getting current-runtime task guidance
  2. 02Listing bundled helper files
  3. 03Updating the CLI and installed skills

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill korean-marathon-schedule

After installing, type/korean-marathon-schedulein Claude Code to confirm it loaded.

Bundled filesinstruction.mdskill.json

Details

From the project README

korean-marathon-schedule

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 korean-marathon-schedule

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 korean-marathon-schedule

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/korean-marathon-schedule/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