SKILLEMALL.ai

BC oma-hwp

Convert Hangul HWP, HWPX, or HWPML documents to Markdown with kordoc. Use for text, table, and image extraction from these formats.

first-fluke/oh-my-agent Agent Skills author: first-fluke 9 files · 3 scripts body ≈ 2 182 tokens Open the sourcegithub.com↗ analyzed 14 h ago

Convert Hangul HWP, HWPX, or HWPML documents to Markdown with kordoc.

As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting

GeneratorWordExcelPDFAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
99
Quality 40%
87
Run on models
none yet
Process rating
C
61/100
Has gaps
Progress reporting w 2
0
Inputs and preconditions w 11
30
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: oh-my-agent, oh-my-agent

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Dangerous commands cmd-pipe-to-shell-known-host resources/execution-protocol.md:112
      Pipe-to-shell installer from a well-known host (still executes remote code) (documentation table row)
      | `bunx` / `bun` not found | Ask user to install Bun: `curl -fsSL https://bun.sh/install \| bash` |
      table

    Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 61/100

    • 0Progress reporting. Says nothing while it works
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 3 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 66 steps, 2 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2182 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +3Description length 131: enough signal without eating the budget
    • +4Structure: 26 headings
    • +3Step-by-step instructions: 66 items
    • +3Output format is stated explicitly
    • +4Has examples (2 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.