BC korean-invoice
한국형 견적서/세금계산서 자동 생성 (사업자등록번호, 부가세 자동 계산)
한국형 견적서/세금계산서 자동 생성 (사업자등록번호, 부가세 자동 계산)
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:56High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…bKX+KS9G…yMA/NhKJ…RGz/Q==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:139High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Nsx+IAh7…8CA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:332High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:454High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…TIe+vXnW…DL0+idd5…ssn/eusA…vCn/9RBg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:553High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CpK+FtMRQVdIMN6/Df5j…tIC+7KYK…qaA==",
detector
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 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
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 838 tokens
- 100Running it twice. No mutating operations
- low 13 top-level sections: this looks like several domains in one skill
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)
- +3Description length 40: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 19 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.