mcpField
K
korean-character-count

korean-character-count

github.com/nomadamasProductivity8.2k7.3k installsUpdated 2d ago
Repository

About korean-character-count

A coding-agent skill for Korean character counting. It directs users to retrieve the current instructions and helper-file list through the k-skill CLI.

Key features

  1. 01CLI-delivered skill instructions
  2. 02CLI listing of helper files
  3. 03Usage and safety safeguards

Use cases

  1. 01Counting Korean characters with the skill's instructions
  2. 02Checking available helper files before use

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill korean-character-count

After installing, type/korean-character-countin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
korean_character_count.js

Details

From the project README

korean-character-count

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-character-count

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-character-count

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-character-count/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