mcpField
K
korean-slang-writing

korean-slang-writing

github.com/nomadamasCreative & media8.2k6.7k installsUpdated 2d ago
Repository

About korean-slang-writing

A coding-agent skill for writing Korean slang. It delivers runtime-specific instructions through a CLI and includes safeguards for sensitive or consequential actions.

Key features

  1. 01Runtime-specific instructions via CLI
  2. 02Lists bundled helper files
  3. 03Requires approval for consequential actions
  4. 04Protects credentials and verification boundaries

Use cases

  1. 01Writing Korean slang with a coding agent
  2. 02Checking which helper files are available
  3. 03Applying safety rules during writing tasks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill korean-slang-writing

After installing, type/korean-slang-writingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
data/
seed-slang.json
scripts/
_slang_http.py
slang_lookup.py
slang_search.py

Details

From the project README

korean-slang-writing

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-slang-writing

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-slang-writing

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-slang-writing/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