How do I install the Explanation skill?

Run npx skillmds@latest add seokhoonj/explanation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Explanation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Explanation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Explanation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Explanation?

seokhoonj (@seokhoonj) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Explanation by seokhoonj — Agent Skill

Name: Explanation
Author: seokhoonj

Explanation

Read the survey documentation behind a KOSIS table -- its purpose, legal basis, cycle, and key terms. Holds no logic of its own -- it calls the pykosis package's CLI (`kosis explanation`) and shows the result to the user. Trigger phrases: 통계조사 설명, 통계 작성목적, 통계 용어 설명, 법적근거 주기, KOSIS survey documentation, why is this survey conducted, KOSIS statistic definitions.

seokhoonj 76b11d3 2.6 KB Updated Sep 17, 2026

File contents

kosis -- survey documentation

Explain the survey behind a KOSIS table rather than its structure or numbers: its purpose, legal basis, cycle, and key terms. The documentation and parsing live in the pykosis package (on PyPI); this skill is a thin wrapper that calls its CLI and relays the result. For a table's structural metadata (items, units, source), use the meta skill.

Prerequisite

This plugin calls the kosis CLI, so the package must be installed and an API key set:

pipx install pykosis          # or: pip install pykosis
export KOSIS_API_KEY=...       # a free key from https://kosis.kr/openapi/

The key can also be stored in ~/.config/pykosis/credentials.json as {"KOSIS_API_KEY": "..."}. Without a key the CLI exits with kosis: no KOSIS API key ...; relay that and point the user at the KOSIS site.

Never print, log, quote, or echo the KOSIS_API_KEY value itself -- confirm only that a key is set.

Running

kosis explanation [--org ORG_ID --tbl TBL_ID | --stat-id STAT_ID] [--meta-item ITEM] [--json]

Identify the survey by --org+--tbl, or directly by --stat-id.
--meta-item narrows to one field (default ALL).
--json emits the full records; the text view shows field: value blocks.

Procedure

Get the codes. You need an org_id + tbl_id, or a stat_id. If the user gave a concept but no codes, use the search (or list) skill first.
Run. Ask for the whole documentation, or narrow with --meta-item.
```
kosis explanation --org 101 --tbl DT_1B42
```
Relay the result. Show the CLI's stdout. If the user asked about one field, point out that block.
Error handling. Relay the one-line kosis: <message> from stderr as-is -- the same key and install errors as the other kosis skills apply.

What this skill does not do

It does not re-implement fetching or parsing (the package does); it always calls the CLI.
It reads the survey documentation only -- for a table's items/units/source, use the meta skill; to fetch its observations, use data; to discover org and table codes, use search or list.

---name: explanationdescription: Read the survey documentation behind a KOSIS table -- its purpose, legal basis, cycle, and key terms. Holds no logic of its own -- it calls the pykosis package's CLI (`kosis explanation`) and shows the result to the user. Trigger phrases: 통계조사 설명, 통계 작성목적, 통계 용어 설명, 법적근거 주기, KOSIS survey documentation, why is this survey conducted, KOSIS statistic definitions.---# kosis -- survey documentationExplain the survey behind a KOSIS table rather than its structure or numbers: its purpose,legal basis, cycle, and key terms. The documentation and parsing live in the pykosis package(on PyPI); this skill is a thin wrapper that calls its CLI and relays the result. For atable's structural metadata (items, units, source), use the **meta** skill.## PrerequisiteThis plugin calls the `kosis` CLI, so the package must be installed and an API key set:```pipx install pykosis # or: pip install pykosisexport KOSIS_API_KEY=... # a free key from https://kosis.kr/openapi/```The key can also be stored in `~/.config/pykosis/credentials.json` as`{"KOSIS_API_KEY": "..."}`. Without a key the CLI exits with`kosis: no KOSIS API key ...`; relay that and point the user at the KOSIS site.**Never print, log, quote, or echo the `KOSIS_API_KEY` value itself** -- confirm only that a key is set.## Running```kosis explanation [--org ORG_ID --tbl TBL_ID | --stat-id STAT_ID] [--meta-item ITEM] [--json]```- Identify the survey by `--org`+`--tbl`, or directly by `--stat-id`.- `--meta-item` narrows to one field (default `ALL`).- `--json` emits the full records; the text view shows `field: value` blocks.## Procedure1. **Get the codes.** You need an `org_id` + `tbl_id`, or a `stat_id`. If the user gave a concept but no codes, use the **search** (or **list**) skill first.2. **Run.** Ask for the whole documentation, or narrow with `--meta-item`. ```bash kosis explanation --org 101 --tbl DT_1B42 ```3. **Relay the result.** Show the CLI's stdout. If the user asked about one field, point out that block.4. **Error handling.** Relay the one-line `kosis: <message>` from stderr as-is -- the same key and install errors as the other kosis skills apply.## What this skill does not do- It does not re-implement fetching or parsing (the package does); it always calls the CLI.- It reads the survey documentation only -- for a table's items/units/source, use the **meta** skill; to fetch its observations, use **data**; to discover org and table codes, use **search** or **list**.

Frequently asked questions