mcpField
K
korean-heritage-search

korean-heritage-search

github.com/nomadamasOther8.2k4.4k installsUpdated 2d ago
Repository

About korean-heritage-search

A coding-agent skill for searching Korean cultural heritage information. It uses the k-skill CLI to provide instructions for the current runtime and sets safeguards for consequential actions and credentials.

Key features

  1. 01Runtime-specific instructions via CLI
  2. 02Bundled helper-file listing
  3. 03Explicit approval for consequential actions
  4. 04Credential and verification safeguards

Use cases

  1. 01Guiding an agent through Korean heritage searches
  2. 02Preventing unapproved submissions or payments
  3. 03Avoiding credential exposure and verification bypasses

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill korean-heritage-search

After installing, type/korean-heritage-searchin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
korean_heritage_search.py

Details

From the project README

korean-heritage-search

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-heritage-search

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-heritage-search

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-heritage-search/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