SKILLEMALL.ai
GitHub ↗ RU Sign in

CD gongmunseo

내용을 받아 한국 행정 공문서(기안문·시행문·보고서·계획서·통지·회의록) 표준 서식의 HWPX로 뽑아주는 오케스트레이터 스킬. 행정안전부 「행정업무운영편람」·시행규칙에 근거한 항목부호 8단계(1. 가. 1) 가) (1) (가) ① ㉮), 둘째 줄 내어쓰기 정렬, 공식 여백(위20·아래10·좌우20mm), 명조 15pt, 줄간격, 날짜·붙임·끝·금액 표기법을 적용해 kordoc의 공문서 모드로 변환한다. 트리거 — "보고서 작성해줘", "기안문 만들어", "공문서로 뽑아줘", "계획서 써줘", "회의록 정리해서 hwpx", "공문 양식으로", "통지문 만들어", "공문서 hwpx", "행정 문서 작성". 단순 md→hwpx 변환(서식 불문)은 kordoc generate 직접 사용. 기존 hwp/hwpx 양식의 빈칸 채우기는 kordoc fill. 견본 문서를 주며 "이 서식대로·똑같이 써줘"(서식 베끼기)는 이 스킬이 아니라 kordoc patch 경로(견본을 읽어 내용만 새로 쓴 뒤 patch).

chrisryugj/kordoc Claude Code author: chrisryugj 11 files body ≈ 1 784 tokens Open the sourcegithub.com↗ analyzed 3 d ago

내용을 받아 한국 행정 공문서(기안문·시행문·보고서·계획서·통지·회의록) 표준 서식의 HWPX로 뽑아주는 오케스트레이터 스킬.

As a process D 35/100 · Unfinished process — References files that are not bundled: templates/<종류>.md

GeneratorAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
75
Run on models
none yet
Process rating
D
35/100
Unfinished process
References files that are not bundled: templates/<종류>.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Edit Bash AskUserQuestion

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: templates/<종류>.md

Process rating: all ten parameters 35/100

Will not run. References files that are not bundled: templates/<종류>.md
  • 0Tools and files. 1 referenced file(s) missing: templates/<종류>.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Steps. 40 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1784 tokens
  • 100Running it twice. No mutating operations

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 10 example trigger phrases
  • +3Description length 509: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (3 of 4)

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