seoul-subway-arrival
Look up Seoul real-time subway arrival information with the official Seoul Open Data API. Use when the user asks when a train arrives, which trains are approaching a station, or how crowded Seoul subway timing looks right now.
Savant verdict: Review advised
SkillSpector or the source hub flagged patterns to review before use.
Live evaluation
Not evaluated yet. Workspaces can request a live evaluation.
Safety (NVIDIA SkillSpector)
Scan pending.
Structure
- 1 referenced file isn't in the packagescripts/generate-skill-stubs.js. They may be binary, too large to catalog, or missing upstream.
- The source hub's security checks flagged this skillSnyk: warn (Risk: MEDIUM · 2 issues)
SKILL.md
--- name: seoul-subway-arrival description: Look up Seoul real-time subway arrival information with the official Seoul Open Data API. Use when the user asks when a train arrives, which trains are approaching a station, or how crowded Seoul subway timing looks right now. license: MIT metadata: category: transit locale: ko-KR phase: v1 --- # seoul-subway-arrival <!-- k-skill:cli-stub — generated by scripts/generate-skill-stubs.js; edit skill.json / instruction.md instead --> ## Get the full instructions (required first step) Run this and follow its output as the primary instructions for this skill: ```bash npx -y @nomadamas/k-skill@0 instruct seoul-subway-arrival ``` 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: ```bash npx -y @nomadamas/k-skill@0 files seoul-subway-arrival ``` Keep the CLI and every coding-agent skill install current (including Vercel Agent Skills) with: ```bash 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-subway-arrival/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.