mcpField
S
seoul-weather-risk

seoul-weather-risk

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

About seoul-weather-risk

seoul-weather-risk is a skill whose current instructions are provided by the k-skill CLI for the detected runtime. The available README specifies safety rules, but does not describe its weather-risk capabilities.

Key features

  1. 01Loads runtime-specific instructions
  2. 02Lists bundled helper files
  3. 03Provides an update command
  4. 04Requires approval for consequential actions
  5. 05Prohibits credential exposure and boundary bypasses

Use cases

  1. 01Loading current instructions for the active runtime
  2. 02Checking which helper files are available
  3. 03Applying safety rules before consequential actions

Install

Copy the command and run it in a terminal.

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

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

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
references/
admin-dong-place-map.json
scripts/
seoul_weather_risk.py
tests/
test_seoul_weather_risk.py

Details

From the project README

seoul-weather-risk

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-weather-risk

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-weather-risk

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-weather-risk/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