Loading the registry…
Safely read, edit, and convert HWPX (Hangul / 한글 .hwpx) word-processor files with Python + lxml without corrupting them. Use this whenever a task involves a .hwpx file, a 한글 / Hangul / 한컴 (Hancom Office) document, HWPML, or a Korean government / academic / 논문 / 보고서 document — including reading or extracting text and tables (e.g. exporting complex merged tables to Excel / .xlsx), editing paragraphs, tables, images, equations, footnotes/endnotes, or memos, adding or positioning captions, fixing layout (orphaned headings, blank pages, columns), building a table of contents, or repackaging the zip. Also trigger when a 한글 file "won't open" / "is corrupted" (파일이 깨졌다 / 한글에서 안 열린다), or when the user hands you a legacy .hwp (this skill detects it and tells them to convert to .hwpx first). Trigger even if the user only says "edit this 한글 file" or ".hwpx" and doesn't mention the internals — naive edits (re-zipping, stale line caches, cloned ids) make 한글 refuse to open the file.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'kangdacool/hwpx-editing-skill (hwpx-editing)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'kangdacool/hwpx-editing-skill (hwpx-editing)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
2 findings · 2.1s
v2.0.11
11 findings · 14.6s
v0.3.74
1 finding · 5.2s
v0.1.0
0 findings · 7.4s
v0.1.0
1 finding · 7.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.2s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 18, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 15 findings above stand exactly as their scanners reported them, at full severity.