[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73HE82S7QG14XGSQ4AR1GA4":3,"skill-same:01M73HE82S7QG14XGSQ4AR1GA4":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":61,"updatedAt":62,"install":63,"resources":75},"01M73HE82S7QG14XGSQ4AR1GA4","k-opendata",null,"Queries Korea's Public Data Portal (`공공데이터포털`, data.go.kr) Open API — a shared gateway hosting Open APIs from dozens of Korean government agencies under one account\u002Fservice-key system. Documents the portal's common activation flow (활용신청 → 개발\u002F운영계정 → 인증키) and the verified Korea Customs Service (`관세청`) trade-statistics endpoints (HS-code-level import\u002Fexport by country, national\u002Fregional totals) as the primary reference API set. Requires DATA_GO_KR_API_KEY environment variable.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002Fskills\u002Fk-opendata\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: k-opendata\nscope: common\ndescription: >\n  Queries Korea's Public Data Portal (`공공데이터포털`, data.go.kr) Open API —\n  a shared gateway hosting Open APIs from dozens of Korean government agencies\n  under one account\u002Fservice-key system. Documents the portal's common\n  activation flow (활용신청 → 개발\u002F운영계정 → 인증키) and the verified Korea\n  Customs Service (`관세청`) trade-statistics endpoints (HS-code-level\n  import\u002Fexport by country, national\u002Fregional totals) as the primary\n  reference API set. Requires DATA_GO_KR_API_KEY environment variable.\nversion: 1.2.3\nlast_reviewed: 2026-09-03\nstatus: active\nowner: public-data-analyst\nprerequisites: DATA_GO_KR_API_KEY environment variable\nrelates_to:\n  - skill: k-ecos\n    type: composes_with\n  - skill: k-kosis\n    type: relates_to\nl2_propagate: true\nmetadata:\n  type: domain\n  source: https:\u002F\u002Fwww.data.go.kr\u002F\n  license: KOGL (`공공누리`)\n  category: trade-statistics\n  locale: ko-KR\n  triggers:\n    - k-opendata\n    - \u002Fk-opendata\n    - 공공데이터포털\n    - data.go.kr\n    - '`관세청`'\n    - '`수출입무역통계`'\n    - '`품목별 국가별 수출입실적`'\n    - Korea Customs Service trade statistics\n    - HS code trade data\nlang: ko\nlang_reason: proper-noun\n---\n\n> **Composition note**: the Korea-Customs analysis workflows that compose with this\n> skill (`hs-classification-workflow`, `market-entry-strategy`, `landed-cost-calculation`)\n> live in the co-export variant (`templates\u002Fco-export\u002Fskills\u002F`) and are linked there.\n\n## Context\n\nUnified skill for Korea's Public Data Portal (`공공데이터포털`, data.go.kr) — the shared Open API\ngateway for Korean government agencies. One portal account and one issued `serviceKey` work\nacross *every* dataset hosted there, but each individual dataset (agency + API) still requires\nits own separate `활용신청` (usage request) before that specific endpoint will accept the key.\nThis skill documents the shared activation mechanics plus the Korea Customs Service (`관세청`)\ntrade-statistics family of APIs, which give **HS-code-level** import\u002Fexport figures — the exact\ngap that `k-kosis` cannot fill (KOSIS has no public per-HS-code trade table; see `k-kosis`\nNotes). Use this whenever HS-code-specific 수출입 실적\u002F동향 (trade performance\u002Ftrend) data is\nneeded for classification, market-entry, or landed-cost work.\n\n## When to Use\n\n- HS-code-level import\u002Fexport value, weight, or trade-balance lookup (national total, by\n  country, or by 시도) — e.g. \"HS 841440 수출입 동향 조회\"\n- Cross-checking a UN Comtrade or KOSIS-proxy trade figure against the authoritative Korean\n  customs-clearance source\n- Any other data.go.kr-hosted government dataset the user names explicitly (this skill's\n  *activation flow* section applies portal-wide, even though the documented endpoints below\n  are customs-specific)\n\n## Execution Steps\n\n1. **Verify Prerequisites**: Confirm `DATA_GO_KR_API_KEY` environment variable is set. If not,\n   guide the user through **Portal Activation Flow** below — do not attempt to query without a\n   key (`SERVICE_KEY_IS_NULL`, error code 20).\n2. **Select the endpoint**: Match the user's need to one of the **Korea Customs Service Trade\n   Statistics APIs** below. For a single HS code across countries\u002Ftime, `품목별 국가별\n   수출입실적(GW)` (`nitemtrade`) is almost always correct.\n3. **Resolve required parameters**: `strtYymm`\u002F`endYymm` (YYYYMM, must span ≤ 1 year per\n   request — loop year-by-year for longer ranges, matching the loop pattern used against UN\n   Comtrade earlier in this kind of task) and `cntyCd` (2-letter country code) are required for\n   `nitemtrade`; only `hsSgn` (the HS code, up to 10 digits) is optional-but-essential for this\n   use case — always pass it.\n4. **Query**: Call the endpoint over HTTPS with `serviceKey` URL-encoded (the key contains `+`,\n   `\u002F`, `=` — use `--data-urlencode`, never raw string interpolation, or the key will be\n   silently mangled).\n5. **Parse Response**: Default response is **XML** (unlike KOSIS's JSON). Check the\n   `\u003CresultCode>`\u002F`\u003CresultMsg>` envelope first — `00` is success; anything else is a documented\n   error (see Failure Modes). Some data.go.kr APIs accept `&type=json` for a JSON response —\n   ⚠️ **unverified for this specific API**; try it, and fall back to XML parsing if unsupported.\n   **Watch for a trailing aggregate row**: live testing (2026-09-03) confirmed that a\n   `strtYymm`–`endYymm` range query returns an extra `\u003Citem>` with `year` (or `priodTitle`) set to\n   `총계` (total) summing the whole range, with dimension fields (`hsCode`\u002F`hsCd`, `statCd`,\n   `statKor`, etc.) set to `-`. Filter this row out before per-period analysis, or double-counting\n   results; keep it only when a range total is explicitly wanted.\n6. **Aggregate if needed**: `cntyCd` is required per call on `nitemtrade` — there is no\n   \"world total\" pseudo-code for that endpoint. For a national total across all countries, use\n   `수출입총괄(GW)` (`getNewtradeList`) directly — confirmed below to take no country or HS\n   parameter, i.e. it *is* the pre-aggregated national total, no loop-and-sum needed. It has no\n   HS-code split, though; if both a national total *and* an HS-code breakdown are needed, still\n   loop `nitemtrade` per country and sum.\n7. **Format Output**: Present figures with unit (USD amount, kg weight) and period, sorted\n   chronologically; append disclaimer \"`공공데이터포털(data.go.kr) 관세청 Open API 자료 기준`\".\n8. **Save to Deliverables**: Store research findings in `deliverables\u002Fresearch\u002F` per project\n   conventions.\n\n## Output Format\n\n- Trade data: HS code \u002F product name \u002F country \u002F period (YYYYMM) \u002F export amount (USD) \u002F\n  export weight (kg) \u002F import amount (USD) \u002F import weight (kg) \u002F trade balance, sorted by\n  period\n- Always cite: \"`공공데이터포털(data.go.kr) 관세청 Open API 자료 기준`\"\n\n## Reference Material\n\n- `references\u002Fterms-ko.json`: Korean-original customs terminology mapping (endpoint names ↔ operations,\n  field aliases incl. the `hsCd`\u002F`hsCode` inconsistency, portal terms, error messages). Non-Markdown\n  reference asset, exempt from the workspace English-only doc policy. A confirmed JSON response shape\n  (`&type=json` support) discovered in recurring lookups goes there.\n\n## Related Skills\n\n- k-ecos (BOK macro-financial series — complements customs trade figures for balance-of-payments context)\n- k-kosis (macro\u002Faggregate statistics — not HS-code-level; use this skill instead for\n  per-HS-code trade figures)\n- hs-classification-workflow (HS code must be confirmed before trade-trend lookup is meaningful)\n- market-entry-strategy\n- landed-cost-calculation\n\n## 공공데이터포털 (data.go.kr) Open API Specification\n\n### Portal Activation Flow\n\n⚠️ **Not independently live-tested this session** — derived from `data.go.kr` help documentation\nand general-purpose search (fetched 2026-09-03). Confirm exact UI copy\u002Ftiming against the live\nportal, as public-sector portals occasionally reorganize.\n\n1. **회원가입\u002F로그인**: Create a data.go.kr account (separate system from KOSIS\u002FDART\u002FLaw Open\n   API accounts — each Korean government Open API portal has its own account).\n2. **데이터셋 검색**: Search `데이터셋 > 오픈API` for the target dataset (e.g. \"관세청 품목별\n   국가별 수출입실적\").\n3. **활용신청**: Open the dataset's `openapi.do` detail page and click `활용신청`. Required\n   fields: 인증유형, 활용용도, 활용목적, 상세기능 선택, 표준약관 동의.\n4. **개발계정 vs 운영계정**:\n   - **개발계정 (dev)**: Immediate\u002Ffast approval in most cases; traffic-capped (관세청 APIs:\n     10,000 calls\u002Fday). Sufficient for research\u002Flookup use.\n   - **운영계정 (production)**: Requires review — must register a usage case (활용사례) and\n     request a specific traffic quota. Only needed for a deployed, recurring-traffic service.\n5. **인증키 발급**: 마이페이지 → 인증키 확인. **One service key per account, shared across every\n   data.go.kr Open API** the account has been approved for — but each individual dataset must\n   still be separately `활용신청`-approved before that key will work against it.\n6. **Exception**: Some 관세청 datasets (e.g. `수출이행내역`) additionally require separate\n   **UNI-PASS** (unipass.customs.go.kr) membership — check the dataset's detail page for this\n   requirement before assuming the data.go.kr key alone is sufficient.\n\n### Korea Customs Service (`관세청`) Trade Statistics APIs\n\n| API (Korean name) | Granularity | Base URL | Status |\n|---|---|---|---|\n| 품목별 국가별 수출입실적(GW) | HS code × country × month | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnitemtrade\u002FgetNitemtradeList` | ✅ Live-tested — see below |\n| 품목별 수출입실적(GW) | HS code × month (no country split) | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002FItemtrade\u002FgetItemtradeList` | ✅ Live-tested — see below |\n| 국가별 수출입실적(GW) | Country × month (no HS split) | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnationtrade\u002FgetNationtradeList` | ✅ Live-tested — see below |\n| 수출입총괄(GW) | National monthly total | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002FNewtrade\u002FgetNewtradeList` | ✅ Live-tested — see below |\n| 시도별 수출입실적(GW) | Korean 시\u002F도 × month | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fsidotrade\u002FgetSidotradeList` | ❌ 403 — key not `활용신청`-approved for this dataset yet, see below |\n| 수출이행내역 | Export fulfillment records | resolve via [openapi.do](https:\u002F\u002Fwww.data.go.kr\u002Fdata\u002F15126269\u002Fopenapi.do) | ⚠️ Requires separate UNI-PASS membership |\n\n#### 1. 품목별 국가별 수출입실적 (`getNitemtradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnitemtrade\u002FgetNitemtradeList\n```\n\n| Parameter | Required | Description |\n|---|---|---|\n| `serviceKey` | Y | Issued authentication key (≤100 chars; URL-encode — contains reserved chars) |\n| `strtYymm` | Y | Start period, `YYYYMM` (e.g. `202401`) — window must be ≤ 1 year |\n| `endYymm` | Y | End period, `YYYYMM` |\n| `cntyCd` | Y | Country code, 2 characters (e.g. `CN`, `US`, `JP`) |\n| `hsSgn` | N | HS code, up to 10 digits — omit for all HS codes to that country (large response) |\n\nResponse format: **XML**. Fields (`body.items.item`): `year`, `hsCd` (⚠️ **not** `hsCode` — differs\nfrom `getItemtradeList`'s field name for the same concept), `statCd` (country code),\n`statCdCntnKor1` (country name), `statKor` (product name), `expDlr`, `expWgt`, `impDlr`, `impWgt`,\n`balPayments`. The trailing `총계` row (see Execution Step 5) sets `hsCd`\u002F`statCd`\u002F`statKor`\u002Fetc.\nto `-`.\n\n✅ **Live-tested** 2026-09-03 with a real `DATA_GO_KR_API_KEY` (`strtYymm=202401`,\n`endYymm=202403`, `cntyCd=CN`, `hsSgn=841440`) — `resultCode` `00`, response matched the fields\nabove exactly.\n\n#### Example Request (live-tested 2026-09-03)\n\n```bash\ncurl -sS --get 'https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnitemtrade\u002FgetNitemtradeList' \\\n  --data-urlencode \"serviceKey=$DATA_GO_KR_API_KEY\" \\\n  --data-urlencode 'strtYymm=202401' \\\n  --data-urlencode 'endYymm=202412' \\\n  --data-urlencode 'cntyCd=CN' \\\n  --data-urlencode 'hsSgn=841440'\n```\n\n⚠️ If `DATA_GO_KR_API_KEY` in `.env`\u002Fenvironment is already percent-encoded (contains literal\n`%2F`, `%3D` sequences), interpolate it raw into the URL instead of `--data-urlencode` — double-\nencoding it (`%2F` → `%252F`) breaks the key. Check the raw value before choosing which form to\nuse.\n\n#### 2. 품목별 수출입실적 (`getItemtradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002FItemtrade\u002FgetItemtradeList\n```\n\n| Parameter | Required | Type | Description |\n|---|---|---|---|\n| `serviceKey` | Y | string | Issued authentication key |\n| `strtYymm` | Y | number | Start period, `YYYYMM` |\n| `endYymm` | Y | number | End period, `YYYYMM` |\n| `hsSgn` | N | number | HS code — omit for all HS codes (large response) |\n\nResponse format: **XML**. Fields (`body.items.item`): `year`, `hsCode` (⚠️ note: this endpoint\nuses `hsCode`, while `nitemtrade` uses `hsCd` for the same concept — do not assume field names\nare consistent across sibling endpoints), `statKor` (product name), `expDlr`, `expWgt`, `impDlr`,\n`impWgt`, `balPayments` (trade balance). No country split — use `nitemtrade` instead when a\ncountry breakdown is also needed. Trailing `총계` row sets `hsCode`\u002F`statKor` to `-`.\n\n✅ **Live-tested** 2026-09-03 with a real key (`strtYymm=202401`, `endYymm=202403`,\n`hsSgn=841440`) — `resultCode` `00`, fields matched exactly.\n\n#### 3. 국가별 수출입실적 (`getNationtradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnationtrade\u002FgetNationtradeList\n```\n\n| Parameter | Required | Type | Description |\n|---|---|---|---|\n| `serviceKey` | Y | string | Issued authentication key |\n| `strtYymm` | Y | string | Start period, `YYYYMM` |\n| `endYymm` | Y | string | End period, `YYYYMM` |\n| `cntyCd` | N | string | Country code — omit for all countries (large response) |\n\nResponse format: **XML**. Fields (`body.items.item`): `year`, `statCd` (country code),\n`statCdCntnKor1` (country name), `expDlr`, `expCnt`, `impDlr`, `impCnt`, `balPayments`. No HS-code\nsplit — use `nitemtrade` instead when an HS breakdown is also needed. Note the field naming\ninconsistency vs. `nitemtrade`\u002F`Itemtrade`: weight here is `expCnt`\u002F`impCnt`, not `expWgt`\u002F`impWgt`\n— confirm the unit (documented portal-wide as net weight, kg) before treating it as a count.\n\n✅ **Live-tested** 2026-09-03 with a real key (`strtYymm=202401`, `endYymm=202403`,\n`cntyCd=CN`) — `resultCode` `00`, fields matched exactly. No `총계` row appeared when `cntyCd`\nwas passed for a single country; unconfirmed whether one appears when `cntyCd` is omitted.\n\n#### 4. 수출입총괄 (`getNewtradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002FNewtrade\u002FgetNewtradeList\n```\n\n| Parameter | Required | Type | Description |\n|---|---|---|---|\n| `serviceKey` | Y | string | Issued authentication key |\n| `strtYymm` | Y | string | Start period, `YYYYMM` |\n| `endYymm` | Y | string | End period, `YYYYMM` |\n\nResponse format: **XML**. Fields (`body.items.item`): `year`, `expDlr`, `expCnt`, `impDlr`,\n`impCnt`, `balPayments`. **No country or HS-code parameter at all** — this confirms it as the\npre-aggregated national monthly total referenced in Execution Step 6 above; no loop-and-sum\nneeded for a world-total figure.\n\n✅ **Live-tested** 2026-09-03 with a real key (`strtYymm=202401`, `endYymm=202403`) —\n`resultCode` `00`, one `\u003Citem>` per month plus a trailing `year=\"총계\"` row summing the range.\n\n#### 5. 시도별 수출입실적 (`getSidotradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fsidotrade\u002FgetSidotradeList\n```\n\n| Parameter | Required | Type | Description |\n|---|---|---|---|\n| `serviceKey` | Y | string | Issued authentication key |\n| `strtYymm` | Y | number | Start period, `YYYYMM` |\n| `endYymm` | Y | number | End period, `YYYYMM` |\n| `sidoCd` | N | string | 시도 code — omit for all 시도 |\n\nResponse format: **XML**. Fields (`body.items.item`): `priodTitle` (period), `sidoNm` (시도 name),\n`expUsdAmt`, `expCnt`, `impUsdAmt`, `impCnt`, `cmtrBlncAmt` (trade balance).\n\n⚠️ **Administrative code change (2026-07-01)**: 전남광주통합 (Jeonnam-Gwangju merger) and Incheon\n지방행정체계 개편 changed `sidoCd` values. Per the dataset's own notice: queries for periods\n**on or after 2026-07-01** use code `12` (전남광주통합특별시); queries for periods **before\n2026-07-01** must use the pre-merger codes `29` (광주광역시) \u002F `46` (전라남도) separately. A\n`strtYymm`\u002F`endYymm` range spanning the merger date will need two calls with different codes if\nscoped to that region — do not assume one `sidoCd` covers the full range.\n\n✅ Spec confirmed via Swagger explorer, 2026-09-03. ❌ **Live-tested 2026-09-03 — failed**: the\nsame key that works for `nitemtrade`\u002F`Itemtrade`\u002F`nationtrade`\u002F`Newtrade` returned HTTP 403 with\n`\u003CerrMsg>SERVICE_KEY_IS_NOT_REGISTERED_ERROR\u003C\u002FerrMsg>` \u002F `returnReasonCode` `30` for\n`sidotrade`. This is the per-dataset `활용신청` requirement from the Portal Activation Flow\nsection made concrete: a portal-wide `serviceKey` does **not** automatically work against every\ndataset — this specific dataset needs its own separate usage-request approval even though the\nsibling 관세청 endpoints above worked immediately. Before using this endpoint, apply for\n`관세청_시도별 수출입실적(GW)` specifically at its `openapi.do` page and wait for approval.\nRetried once a few minutes later with the identical request — same error — so this is a genuine\nmissing per-dataset approval, not a propagation delay.\n\n### Failure Modes\n\n- `DATA_GO_KR_API_KEY` not set → guide through Portal Activation Flow, then stop\n- Error code `20` (`SERVICE_KEY_IS_NULL`) → key missing\u002Fnot passed correctly — check\n  URL-encoding of the key value\n- Error code `22` (traffic quota exceeded) → dev account daily cap (10,000\u002Fday for 관세청 APIs)\n  hit; wait for reset or request 운영계정 quota increase\n- Error code `30` (`SERVICE_KEY_IS_NOT_REGISTERED_ERROR`, HTTP 403, `등록되지 않은 서비스키`) →\n  the key is valid portal-wide but not yet `활용신청`-approved for *this specific* dataset —\n  confirmed live 2026-09-03 against `sidotrade`; apply separately on that dataset's `openapi.do`\n  page, do not assume approval on one 관세청 endpoint covers its siblings\n- `strtYymm`\u002F`endYymm` span > 1 year → split into multiple calls, one per ≤1-year window (loop\n  by year, same pattern as querying UN Comtrade year-by-year)\n- World-total figure needed → use `수출입총괄(GW)` (`getNewtradeList`) directly (confirmed\n  live 2026-09-03, no `cntyCd`\u002F`hsSgn` parameter exists on it); do not loop-and-sum `nitemtrade`\n  per country unless an HS-code split is also required\n- Range query returns an unexpected extra row → check for the `총계` (total) aggregate row\n  (see Execution Step 5) before treating item count as \"one row per period\"\n\n### Notes\n\n- Data source: [공공데이터포털 (data.go.kr)](https:\u002F\u002Fwww.data.go.kr\u002F)\n- This skill is read-only query only.\n- License: `공공누리`(KOGL) — cite source when reproducing trade figures in deliverables.\n- Created 2026-09-03 in `co-export` after establishing that neither KOSIS nor UN Comtrade give\n  an exact, HS-code-level, 관세청-sourced figure as directly as data.go.kr's customs APIs do;\n  follows the `k-kosis`\u002F`k-dart`\u002F`k-law` sibling pattern. Not yet promoted to\n  `templates\u002Fcommon\u002Fskills\u002F` at the workspace root — this project checkout has no\n  `templates\u002Fcommon\u002F` directory to propagate into.\n- 2026-09-03 (continued): all five documented base URLs\u002Foperations (`nitemtrade`, `Itemtrade`,\n  `nationtrade`, `Newtrade`, `sidotrade`) confirmed via the portal's own Swagger explorer\n  (`활용정보 → 상세기능 → Explore` tab on each dataset's `openapi.do` page — a plain page-text\n  fetch does not surface this tab's content; browser interaction was required).\n- 2026-09-03 (live test): a real `DATA_GO_KR_API_KEY` became available and 4 of 5 endpoints\n  (`nitemtrade`, `Itemtrade`, `nationtrade`, `Newtrade`) were exercised live with `resultCode`\n  `00` — confirmed exact field names (including the `hsCd` vs. `hsCode` inconsistency between\n  `nitemtrade` and `Itemtrade`) and the trailing `총계` aggregate-row behavior on range queries.\n  `sidotrade` failed with error `30` (key not yet approved for that specific dataset) — see\n  Failure Modes. This is the strongest real-world confirmation of the per-dataset `활용신청`\n  requirement described in Portal Activation Flow step 5.\n","> **Composition note**: the Korea-Customs analysis workflows that compose with this\n> skill (`hs-classification-workflow`, `market-entry-strategy`, `landed-cost-calculation`)\n> live in the co-export variant (`templates\u002Fco-export\u002Fskills\u002F`) and are linked there.\n\n## Context\n\nUnified skill for Korea's Public Data Portal (`공공데이터포털`, data.go.kr) — the shared Open API\ngateway for Korean government agencies. One portal account and one issued `serviceKey` work\nacross *every* dataset hosted there, but each individual dataset (agency + API) still requires\nits own separate `활용신청` (usage request) before that specific endpoint will accept the key.\nThis skill documents the shared activation mechanics plus the Korea Customs Service (`관세청`)\ntrade-statistics family of APIs, which give **HS-code-level** import\u002Fexport figures — the exact\ngap that `k-kosis` cannot fill (KOSIS has no public per-HS-code trade table; see `k-kosis`\nNotes). Use this whenever HS-code-specific 수출입 실적\u002F동향 (trade performance\u002Ftrend) data is\nneeded for classification, market-entry, or landed-cost work.\n\n## When to Use\n\n- HS-code-level import\u002Fexport value, weight, or trade-balance lookup (national total, by\n  country, or by 시도) — e.g. \"HS 841440 수출입 동향 조회\"\n- Cross-checking a UN Comtrade or KOSIS-proxy trade figure against the authoritative Korean\n  customs-clearance source\n- Any other data.go.kr-hosted government dataset the user names explicitly (this skill's\n  *activation flow* section applies portal-wide, even though the documented endpoints below\n  are customs-specific)\n\n## Execution Steps\n\n1. **Verify Prerequisites**: Confirm `DATA_GO_KR_API_KEY` environment variable is set. If not,\n   guide the user through **Portal Activation Flow** below — do not attempt to query without a\n   key (`SERVICE_KEY_IS_NULL`, error code 20).\n2. **Select the endpoint**: Match the user's need to one of the **Korea Customs Service Trade\n   Statistics APIs** below. For a single HS code across countries\u002Ftime, `품목별 국가별\n   수출입실적(GW)` (`nitemtrade`) is almost always correct.\n3. **Resolve required parameters**: `strtYymm`\u002F`endYymm` (YYYYMM, must span ≤ 1 year per\n   request — loop year-by-year for longer ranges, matching the loop pattern used against UN\n   Comtrade earlier in this kind of task) and `cntyCd` (2-letter country code) are required for\n   `nitemtrade`; only `hsSgn` (the HS code, up to 10 digits) is optional-but-essential for this\n   use case — always pass it.\n4. **Query**: Call the endpoint over HTTPS with `serviceKey` URL-encoded (the key contains `+`,\n   `\u002F`, `=` — use `--data-urlencode`, never raw string interpolation, or the key will be\n   silently mangled).\n5. **Parse Response**: Default response is **XML** (unlike KOSIS's JSON). Check the\n   `\u003CresultCode>`\u002F`\u003CresultMsg>` envelope first — `00` is success; anything else is a documented\n   error (see Failure Modes). Some data.go.kr APIs accept `&type=json` for a JSON response —\n   ⚠️ **unverified for this specific API**; try it, and fall back to XML parsing if unsupported.\n   **Watch for a trailing aggregate row**: live testing (2026-09-03) confirmed that a\n   `strtYymm`–`endYymm` range query returns an extra `\u003Citem>` with `year` (or `priodTitle`) set to\n   `총계` (total) summing the whole range, with dimension fields (`hsCode`\u002F`hsCd`, `statCd`,\n   `statKor`, etc.) set to `-`. Filter this row out before per-period analysis, or double-counting\n   results; keep it only when a range total is explicitly wanted.\n6. **Aggregate if needed**: `cntyCd` is required per call on `nitemtrade` — there is no\n   \"world total\" pseudo-code for that endpoint. For a national total across all countries, use\n   `수출입총괄(GW)` (`getNewtradeList`) directly — confirmed below to take no country or HS\n   parameter, i.e. it *is* the pre-aggregated national total, no loop-and-sum needed. It has no\n   HS-code split, though; if both a national total *and* an HS-code breakdown are needed, still\n   loop `nitemtrade` per country and sum.\n7. **Format Output**: Present figures with unit (USD amount, kg weight) and period, sorted\n   chronologically; append disclaimer \"`공공데이터포털(data.go.kr) 관세청 Open API 자료 기준`\".\n8. **Save to Deliverables**: Store research findings in `deliverables\u002Fresearch\u002F` per project\n   conventions.\n\n## Output Format\n\n- Trade data: HS code \u002F product name \u002F country \u002F period (YYYYMM) \u002F export amount (USD) \u002F\n  export weight (kg) \u002F import amount (USD) \u002F import weight (kg) \u002F trade balance, sorted by\n  period\n- Always cite: \"`공공데이터포털(data.go.kr) 관세청 Open API 자료 기준`\"\n\n## Reference Material\n\n- `references\u002Fterms-ko.json`: Korean-original customs terminology mapping (endpoint names ↔ operations,\n  field aliases incl. the `hsCd`\u002F`hsCode` inconsistency, portal terms, error messages). Non-Markdown\n  reference asset, exempt from the workspace English-only doc policy. A confirmed JSON response shape\n  (`&type=json` support) discovered in recurring lookups goes there.\n\n## Related Skills\n\n- k-ecos (BOK macro-financial series — complements customs trade figures for balance-of-payments context)\n- k-kosis (macro\u002Faggregate statistics — not HS-code-level; use this skill instead for\n  per-HS-code trade figures)\n- hs-classification-workflow (HS code must be confirmed before trade-trend lookup is meaningful)\n- market-entry-strategy\n- landed-cost-calculation\n\n## 공공데이터포털 (data.go.kr) Open API Specification\n\n### Portal Activation Flow\n\n⚠️ **Not independently live-tested this session** — derived from `data.go.kr` help documentation\nand general-purpose search (fetched 2026-09-03). Confirm exact UI copy\u002Ftiming against the live\nportal, as public-sector portals occasionally reorganize.\n\n1. **회원가입\u002F로그인**: Create a data.go.kr account (separate system from KOSIS\u002FDART\u002FLaw Open\n   API accounts — each Korean government Open API portal has its own account).\n2. **데이터셋 검색**: Search `데이터셋 > 오픈API` for the target dataset (e.g. \"관세청 품목별\n   국가별 수출입실적\").\n3. **활용신청**: Open the dataset's `openapi.do` detail page and click `활용신청`. Required\n   fields: 인증유형, 활용용도, 활용목적, 상세기능 선택, 표준약관 동의.\n4. **개발계정 vs 운영계정**:\n   - **개발계정 (dev)**: Immediate\u002Ffast approval in most cases; traffic-capped (관세청 APIs:\n     10,000 calls\u002Fday). Sufficient for research\u002Flookup use.\n   - **운영계정 (production)**: Requires review — must register a usage case (활용사례) and\n     request a specific traffic quota. Only needed for a deployed, recurring-traffic service.\n5. **인증키 발급**: 마이페이지 → 인증키 확인. **One service key per account, shared across every\n   data.go.kr Open API** the account has been approved for — but each individual dataset must\n   still be separately `활용신청`-approved before that key will work against it.\n6. **Exception**: Some 관세청 datasets (e.g. `수출이행내역`) additionally require separate\n   **UNI-PASS** (unipass.customs.go.kr) membership — check the dataset's detail page for this\n   requirement before assuming the data.go.kr key alone is sufficient.\n\n### Korea Customs Service (`관세청`) Trade Statistics APIs\n\n| API (Korean name) | Granularity | Base URL | Status |\n|---|---|---|---|\n| 품목별 국가별 수출입실적(GW) | HS code × country × month | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnitemtrade\u002FgetNitemtradeList` | ✅ Live-tested — see below |\n| 품목별 수출입실적(GW) | HS code × month (no country split) | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002FItemtrade\u002FgetItemtradeList` | ✅ Live-tested — see below |\n| 국가별 수출입실적(GW) | Country × month (no HS split) | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnationtrade\u002FgetNationtradeList` | ✅ Live-tested — see below |\n| 수출입총괄(GW) | National monthly total | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002FNewtrade\u002FgetNewtradeList` | ✅ Live-tested — see below |\n| 시도별 수출입실적(GW) | Korean 시\u002F도 × month | `https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fsidotrade\u002FgetSidotradeList` | ❌ 403 — key not `활용신청`-approved for this dataset yet, see below |\n| 수출이행내역 | Export fulfillment records | resolve via [openapi.do](https:\u002F\u002Fwww.data.go.kr\u002Fdata\u002F15126269\u002Fopenapi.do) | ⚠️ Requires separate UNI-PASS membership |\n\n#### 1. 품목별 국가별 수출입실적 (`getNitemtradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnitemtrade\u002FgetNitemtradeList\n```\n\n| Parameter | Required | Description |\n|---|---|---|\n| `serviceKey` | Y | Issued authentication key (≤100 chars; URL-encode — contains reserved chars) |\n| `strtYymm` | Y | Start period, `YYYYMM` (e.g. `202401`) — window must be ≤ 1 year |\n| `endYymm` | Y | End period, `YYYYMM` |\n| `cntyCd` | Y | Country code, 2 characters (e.g. `CN`, `US`, `JP`) |\n| `hsSgn` | N | HS code, up to 10 digits — omit for all HS codes to that country (large response) |\n\nResponse format: **XML**. Fields (`body.items.item`): `year`, `hsCd` (⚠️ **not** `hsCode` — differs\nfrom `getItemtradeList`'s field name for the same concept), `statCd` (country code),\n`statCdCntnKor1` (country name), `statKor` (product name), `expDlr`, `expWgt`, `impDlr`, `impWgt`,\n`balPayments`. The trailing `총계` row (see Execution Step 5) sets `hsCd`\u002F`statCd`\u002F`statKor`\u002Fetc.\nto `-`.\n\n✅ **Live-tested** 2026-09-03 with a real `DATA_GO_KR_API_KEY` (`strtYymm=202401`,\n`endYymm=202403`, `cntyCd=CN`, `hsSgn=841440`) — `resultCode` `00`, response matched the fields\nabove exactly.\n\n#### Example Request (live-tested 2026-09-03)\n\n```bash\ncurl -sS --get 'https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnitemtrade\u002FgetNitemtradeList' \\\n  --data-urlencode \"serviceKey=$DATA_GO_KR_API_KEY\" \\\n  --data-urlencode 'strtYymm=202401' \\\n  --data-urlencode 'endYymm=202412' \\\n  --data-urlencode 'cntyCd=CN' \\\n  --data-urlencode 'hsSgn=841440'\n```\n\n⚠️ If `DATA_GO_KR_API_KEY` in `.env`\u002Fenvironment is already percent-encoded (contains literal\n`%2F`, `%3D` sequences), interpolate it raw into the URL instead of `--data-urlencode` — double-\nencoding it (`%2F` → `%252F`) breaks the key. Check the raw value before choosing which form to\nuse.\n\n#### 2. 품목별 수출입실적 (`getItemtradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002FItemtrade\u002FgetItemtradeList\n```\n\n| Parameter | Required | Type | Description |\n|---|---|---|---|\n| `serviceKey` | Y | string | Issued authentication key |\n| `strtYymm` | Y | number | Start period, `YYYYMM` |\n| `endYymm` | Y | number | End period, `YYYYMM` |\n| `hsSgn` | N | number | HS code — omit for all HS codes (large response) |\n\nResponse format: **XML**. Fields (`body.items.item`): `year`, `hsCode` (⚠️ note: this endpoint\nuses `hsCode`, while `nitemtrade` uses `hsCd` for the same concept — do not assume field names\nare consistent across sibling endpoints), `statKor` (product name), `expDlr`, `expWgt`, `impDlr`,\n`impWgt`, `balPayments` (trade balance). No country split — use `nitemtrade` instead when a\ncountry breakdown is also needed. Trailing `총계` row sets `hsCode`\u002F`statKor` to `-`.\n\n✅ **Live-tested** 2026-09-03 with a real key (`strtYymm=202401`, `endYymm=202403`,\n`hsSgn=841440`) — `resultCode` `00`, fields matched exactly.\n\n#### 3. 국가별 수출입실적 (`getNationtradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fnationtrade\u002FgetNationtradeList\n```\n\n| Parameter | Required | Type | Description |\n|---|---|---|---|\n| `serviceKey` | Y | string | Issued authentication key |\n| `strtYymm` | Y | string | Start period, `YYYYMM` |\n| `endYymm` | Y | string | End period, `YYYYMM` |\n| `cntyCd` | N | string | Country code — omit for all countries (large response) |\n\nResponse format: **XML**. Fields (`body.items.item`): `year`, `statCd` (country code),\n`statCdCntnKor1` (country name), `expDlr`, `expCnt`, `impDlr`, `impCnt`, `balPayments`. No HS-code\nsplit — use `nitemtrade` instead when an HS breakdown is also needed. Note the field naming\ninconsistency vs. `nitemtrade`\u002F`Itemtrade`: weight here is `expCnt`\u002F`impCnt`, not `expWgt`\u002F`impWgt`\n— confirm the unit (documented portal-wide as net weight, kg) before treating it as a count.\n\n✅ **Live-tested** 2026-09-03 with a real key (`strtYymm=202401`, `endYymm=202403`,\n`cntyCd=CN`) — `resultCode` `00`, fields matched exactly. No `총계` row appeared when `cntyCd`\nwas passed for a single country; unconfirmed whether one appears when `cntyCd` is omitted.\n\n#### 4. 수출입총괄 (`getNewtradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002FNewtrade\u002FgetNewtradeList\n```\n\n| Parameter | Required | Type | Description |\n|---|---|---|---|\n| `serviceKey` | Y | string | Issued authentication key |\n| `strtYymm` | Y | string | Start period, `YYYYMM` |\n| `endYymm` | Y | string | End period, `YYYYMM` |\n\nResponse format: **XML**. Fields (`body.items.item`): `year`, `expDlr`, `expCnt`, `impDlr`,\n`impCnt`, `balPayments`. **No country or HS-code parameter at all** — this confirms it as the\npre-aggregated national monthly total referenced in Execution Step 6 above; no loop-and-sum\nneeded for a world-total figure.\n\n✅ **Live-tested** 2026-09-03 with a real key (`strtYymm=202401`, `endYymm=202403`) —\n`resultCode` `00`, one `\u003Citem>` per month plus a trailing `year=\"총계\"` row summing the range.\n\n#### 5. 시도별 수출입실적 (`getSidotradeList`)\n\n```\nGET https:\u002F\u002Fapis.data.go.kr\u002F1220000\u002Fsidotrade\u002FgetSidotradeList\n```\n\n| Parameter | Required | Type | Description |\n|---|---|---|---|\n| `serviceKey` | Y | string | Issued authentication key |\n| `strtYymm` | Y | number | Start period, `YYYYMM` |\n| `endYymm` | Y | number | End period, `YYYYMM` |\n| `sidoCd` | N | string | 시도 code — omit for all 시도 |\n\nResponse format: **XML**. Fields (`body.items.item`): `priodTitle` (period), `sidoNm` (시도 name),\n`expUsdAmt`, `expCnt`, `impUsdAmt`, `impCnt`, `cmtrBlncAmt` (trade balance).\n\n⚠️ **Administrative code change (2026-07-01)**: 전남광주통합 (Jeonnam-Gwangju merger) and Incheon\n지방행정체계 개편 changed `sidoCd` values. Per the dataset's own notice: queries for periods\n**on or after 2026-07-01** use code `12` (전남광주통합특별시); queries for periods **before\n2026-07-01** must use the pre-merger codes `29` (광주광역시) \u002F `46` (전라남도) separately. A\n`strtYymm`\u002F`endYymm` range spanning the merger date will need two calls with different codes if\nscoped to that region — do not assume one `sidoCd` covers the full range.\n\n✅ Spec confirmed via Swagger explorer, 2026-09-03. ❌ **Live-tested 2026-09-03 — failed**: the\nsame key that works for `nitemtrade`\u002F`Itemtrade`\u002F`nationtrade`\u002F`Newtrade` returned HTTP 403 with\n`\u003CerrMsg>SERVICE_KEY_IS_NOT_REGISTERED_ERROR\u003C\u002FerrMsg>` \u002F `returnReasonCode` `30` for\n`sidotrade`. This is the per-dataset `활용신청` requirement from the Portal Activation Flow\nsection made concrete: a portal-wide `serviceKey` does **not** automatically work against every\ndataset — this specific dataset needs its own separate usage-request approval even though the\nsibling 관세청 endpoints above worked immediately. Before using this endpoint, apply for\n`관세청_시도별 수출입실적(GW)` specifically at its `openapi.do` page and wait for approval.\nRetried once a few minutes later with the identical request — same error — so this is a genuine\nmissing per-dataset approval, not a propagation delay.\n\n### Failure Modes\n\n- `DATA_GO_KR_API_KEY` not set → guide through Portal Activation Flow, then stop\n- Error code `20` (`SERVICE_KEY_IS_NULL`) → key missing\u002Fnot passed correctly — check\n  URL-encoding of the key value\n- Error code `22` (traffic quota exceeded) → dev account daily cap (10,000\u002Fday for 관세청 APIs)\n  hit; wait for reset or request 운영계정 quota increase\n- Error code `30` (`SERVICE_KEY_IS_NOT_REGISTERED_ERROR`, HTTP 403, `등록되지 않은 서비스키`) →\n  the key is valid portal-wide but not yet `활용신청`-approved for *this specific* dataset —\n  confirmed live 2026-09-03 against `sidotrade`; apply separately on that dataset's `openapi.do`\n  page, do not assume approval on one 관세청 endpoint covers its siblings\n- `strtYymm`\u002F`endYymm` span > 1 year → split into multiple calls, one per ≤1-year window (loop\n  by year, same pattern as querying UN Comtrade year-by-year)\n- World-total figure needed → use `수출입총괄(GW)` (`getNewtradeList`) directly (confirmed\n  live 2026-09-03, no `cntyCd`\u002F`hsSgn` parameter exists on it); do not loop-and-sum `nitemtrade`\n  per country unless an HS-code split is also required\n- Range query returns an unexpected extra row → check for the `총계` (total) aggregate row\n  (see Execution Step 5) before treating item count as \"one row per period\"\n\n### Notes\n\n- Data source: [공공데이터포털 (data.go.kr)](https:\u002F\u002Fwww.data.go.kr\u002F)\n- This skill is read-only query only.\n- License: `공공누리`(KOGL) — cite source when reproducing trade figures in deliverables.\n- Created 2026-09-03 in `co-export` after establishing that neither KOSIS nor UN Comtrade give\n  an exact, HS-code-level, 관세청-sourced figure as directly as data.go.kr's customs APIs do;\n  follows the `k-kosis`\u002F`k-dart`\u002F`k-law` sibling pattern. Not yet promoted to\n  `templates\u002Fcommon\u002Fskills\u002F` at the workspace root — this project checkout has no\n  `templates\u002Fcommon\u002F` directory to propagate into.\n- 2026-09-03 (continued): all five documented base URLs\u002Foperations (`nitemtrade`, `Itemtrade`,\n  `nationtrade`, `Newtrade`, `sidotrade`) confirmed via the portal's own Swagger explorer\n  (`활용정보 → 상세기능 → Explore` tab on each dataset's `openapi.do` page — a plain page-text\n  fetch does not surface this tab's content; browser interaction was required).\n- 2026-09-03 (live test): a real `DATA_GO_KR_API_KEY` became available and 4 of 5 endpoints\n  (`nitemtrade`, `Itemtrade`, `nationtrade`, `Newtrade`) were exercised live with `resultCode`\n  `00` — confirmed exact field names (including the `hsCd` vs. `hsCode` inconsistency between\n  `nitemtrade` and `Itemtrade`) and the trailing `총계` aggregate-row behavior on range queries.\n  `sidotrade` failed with error `30` (key not yet approved for that specific dataset) — see\n  Failure Modes. This is the strongest real-world confirmation of the per-dataset `활용신청`\n  requirement described in Portal Activation Flow step 5.\n",{"lang":23,"name":5,"owner":24,"scope":25,"status":26,"version":27,"metadata":28,"relates_to":43,"description":50,"lang_reason":51,"l2_propagate":52,"last_reviewed":53,"prerequisites":54},"ko","public-data-analyst","common","active","1.2.3",{"type":29,"locale":30,"source":31,"license":32,"category":33,"triggers":34},"domain","ko-KR","https:\u002F\u002Fwww.data.go.kr\u002F","KOGL (`공공누리`)","trade-statistics",[5,35,36,37,38,39,40,41,42],"\u002Fk-opendata","공공데이터포털","data.go.kr","`관세청`","`수출입무역통계`","`품목별 국가별 수출입실적`","Korea Customs Service trade statistics","HS code trade data",[44,47],{"type":45,"skill":46},"composes_with","k-ecos",{"type":48,"skill":49},"relates_to","k-kosis","Queries Korea's Public Data Portal (`공공데이터포털`, data.go.kr) Open API — a shared gateway hosting Open APIs from dozens of Korean government agencies under one account\u002Fservice-key system. Documents the portal's common activation flow (활용신청 → 개발\u002F운영계정 → 인증키) and the verified Korea Customs Service (`관세청`) trade-statistics endpoints (HS-code-level import\u002Fexport by country, national\u002Fregional totals) as the primary reference API set. Requires DATA_GO_KR_API_KEY environment variable.\n","proper-noun",true,1788393600000,"DATA_GO_KR_API_KEY environment variable","main","b57e612781a79b0e3e60878294ce59c86cc68e5d","templates\u002Fcommon\u002Fskills\u002Fk-opendata",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":52},[65,68,71],{"tool":66,"command":67},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill k-opendata",{"tool":69,"command":70},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill k-opendata",{"tool":72,"command":73},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill k-opendata","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002Fskills\u002Fk-opendata\u002FSKILL.md",[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fterms-ko.json","REFERENCE","参考文档",2978,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002Fskills\u002Fk-opendata\u002Freferences\u002Fterms-ko.json",[83,91,96,101,106,111],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":90},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":92,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":90},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":97,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":90},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":102,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":90},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":107,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":90},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":112,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":90},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]