BC juso-address-cli
Search and resolve Korean road addresses (도로명주소) via the official juso.go.kr OpenAPI. Keyword search with zip codes, English address lookup, and address-to-coordinate conversion. Use when a task needs a form-ready Korean address with 우편번호, 영문주소, or lat/lng for a specific address string — e.g. checkout forms, shipping, invoicing, 사업자 등록 forms, real-estate intake. Prefer this over Kakao/Naver geocoders when the requirement is a government-validated road address rather than a map pin.
Search and resolve Korean road addresses (도로명주소) via the official juso.go.kr OpenAPI. Keyword search with zip codes, English address lookup, and…
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
net-credential-usescripts/eng.sh:30Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded): "${JUSO_CONFM_KEY:?JUSO_CONFM_KEY is not set — get a key at https://business.juso.go.kr/addrlink/openApi/apiExprn.do}"vendor-hostquoted -
low Exfiltration
net-credential-usescripts/search.sh:34Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded): "${JUSO_CONFM_KEY:?JUSO_CONFM_KEY is not set — get a key at https://business.juso.go.kr/addrlink/openApi/apiExprn.do}"vendor-hostquoted
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 71): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 890 tokens
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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 486: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (3 code blocks)
- +3All 4 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.