PluginBench
Skill
Pass
Audit score 90

hwp

nomadamas/k-skill

Parse, extract, and convert HWP/HWPX documents to JSON and Markdown using kordoc.

What is hwp?

Agent-native skill for reading and analyzing Korean HWP/HWPX documents. Use it to parse document structure, extract text and form fields, compare versions, and convert to Markdown or back to HWPX format. Read-only for binary editing; use rhwp-edit for modifications.

  • Parse HWP/HWPX documents into structured JSON format
  • Extract text content and metadata from documents
  • Identify and extract form field data
  • Perform document diffing to compare versions
  • Convert Markdown back to HWPX format
  • Support agent-native document processing workflows

How to install hwp

npx skills add https://github.com/nomadamas/k-skill --skill hwp
Prerequisites
  • Node.js 18 or later
  • npx available in environment
  • kordoc library (bundled with skill)
Claude Code
Cursor
Windsurf
Cline

How to use hwp

  1. 1.Run `npx -y @nomadamas/k-skill@0 instruct hwp` to get runtime-specific instructions
  2. 2.Use `npx -y @nomadamas/k-skill@0 files hwp` to list available helper files
  3. 3.Parse HWP/HWPX files using the kordoc agent-native API
  4. 4.Extract JSON, form fields, or text as needed
  5. 5.Convert Markdown to HWPX or compare document versions
  6. 6.Keep the skill updated with `npx -y @nomadamas/k-skill@0 update`

Use cases

Good for
  • Extract structured data from Korean government or business forms in HWP format
  • Compare versions of HWP documents to identify changes
  • Convert HWP documents to Markdown for further processing or analysis
  • Populate HWP form templates programmatically via Markdown conversion
  • Analyze document structure and metadata for compliance or audit purposes
Who it's for
  • Agents processing Korean documents
  • Document automation workflows
  • Form data extraction tasks
  • Content conversion pipelines
  • Document analysis and comparison tasks

hwp FAQ

Can I edit HWP files directly with this skill?

No, this skill is read-only for parsing and conversion. For binary editing, use the rhwp-edit skill instead.

What document formats are supported?

HWP (Hangul Word Processor) and HWPX (compressed HWP) formats are supported.

How do I convert Markdown back to HWPX?

Use the Markdown→HWPX reverse conversion capability included in kordoc after parsing or preparing your Markdown content.

Do I need to provide credentials or API keys?

No, this skill works locally with kordoc and does not require external credentials or API keys.

What should I do before making changes to documents?

Always get explicit user approval before executing final submissions, cancellations, or public posting of document changes.

Full instructions (SKILL.md)

Source of truth, from nomadamas/k-skill.


name: hwp description: Use kordoc for agent-native HWP/HWPX document parsing, JSON extraction, diffing, form-field extraction, and Markdown→HWPX reverse conversion (read/convert only — for binary editing use rhwp-edit). license: MIT metadata: category: documents locale: ko-KR phase: v1

hwp

<!-- 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:

npx -y @nomadamas/k-skill@0 instruct hwp

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 hwp

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/hwp/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.