메뉴
Use when adding a new SKOS concept scheme / vocabulary / thesaurus to the skosdex repository (creating its third_party/skos/<slug>/ folder and meta.ttl), or when deciding whether a scheme's data may be committed and bundled given its license.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when (re)building skosdex concept embeddings for many or all schemes at once — a one-off GPU batch box to embed the whole corpus ASAP, or a parallel CI matrix for incremental per-scheme additions. Covers the embed pipeline, where to run it (and why not the prod box), model parity, committing + deploying the vectors with no blackout, and — critically — tearing the GPU box down afterwards so it stops billing.
Use when working with skosdex concept embeddings — the per-scheme and combined vectors, their JSON formats, the in-browser "similar by meaning" / viz consumers, or the server-side similarity REST API (tools/embed_api.mjs). Covers how to build, combine, query, and extend them.
Use when redeploying the live skosdex stack (skosdex.fly.dev — Oxigraph + Solr + web) on Fly.io, choosing between a direct deploy and the zero-downtime cutover, forcing/monitoring a deploy, or recovering a broken one. The deploy is CI-driven from claude/main.
Use when discovering, researching, triaging, or maintaining the list of candidate SKOS vocabularies for skosdex — i.e. updating third_party/skos/CANDIDATES.md, verifying a scheme's license, or deciding whether a vocabulary can be bundled or must stay metadata-only.
Use when producing the shippable skosdex dataset — merging openly-licensed canonical N-Quads into dist/bundle.nq.gz, generating dist/solr-docs.json, building the docs/ site, or understanding which schemes are included/excluded and why.
Use when fetching, parsing, normalizing, or canonicalizing a SKOS scheme into N-Quads in skosdex — i.e. running the scripts/skosdex fetch/normalize/canonicalize pipeline or debugging its normalized.nq.gz / canonical.nq.gz output, including the gzip + Git LFS storage and zip/gz source decompression.
| name | add-skos-scheme |
| description | Use when adding a new SKOS concept scheme / vocabulary / thesaurus to the skosdex repository (creating its third_party/skos/<slug>/ folder and meta.ttl), or when deciding whether a scheme's data may be committed and bundled given its license. |
| license | Apache-2.0 |
Each scheme lives in third_party/skos/<slug>/ and is described by a single
meta.ttl. The common tooling (scripts/skosdex) reads meta.ttl and needs no
per-scheme code for the normal case.
<slug> and create third_party/skos/<slug>/.templates/meta.ttl (next to this skill) into that folder and fill it
in. See the skosdex: vocabulary in ns/skosdex.ttl for term definitions.public-domain — CC0 / public domain → bundle OK.open — permissive, commercial use allowed, no share-alike (e.g. CC BY,
Apache, MIT, OGL) → bundle OK.copyleft — share-alike (e.g. CC BY-SA) → container-only: bundled
into the SPARQL/Solr image with explicit licensing, no semantic changes;
never in static artifacts. (ODbL is NOT granted — metadata only.)noncommercial — CC BY-NC / BY-NC-ND → container-only, as above.proprietary / unknown → metadata only.public-domain/open, you may set
skosdex:sourceFile to a committed copy under the scheme folder. Otherwise
set skosdex:sourceURL (the tooling fetches into the gitignored cache/).
If the download is a zip/gzip, add skosdex:compression "zip" (or "gzip"),
and skosdex:sourceEntry for a specific member of a multi-file zip.node scripts/skosdex list should show the scheme with the expected
license class and inclusion status.node scripts/skosdex build (see the normalize-skos skill). The
committed output is a gzipped, Git LFS-tracked canonical.nq.gz — ensure
git lfs is installed (the SessionStart hook handles this; see CLAUDE.md).The repository only carries openly-licensed data. Anything with a viral
(copyleft / share-alike) or anti-commercial (NC) license must stay
metadata-only: a meta.ttl record that lets others fetch it themselves
under its own terms. The bundler enforces this regardless of the bundle flag —
non-open data never reaches dist/. See third_party/skos/README.md.