菜单
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.
用 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 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.
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 | curate-vocabularies |
| description | 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. |
| license | Apache-2.0 |
The backlog of SKOS schemes lives in
third_party/skos/CANDIDATES.md. This
skill keeps it accurate and decides what may be onboarded.
| class | examples | container | static (demo/Pages) |
|---|---|---|---|
public-domain | CC0, US-gov works | ✅ | ✅ |
open | CC BY, ODC-By, OGL, Apache/MIT | ✅ | ✅ |
copyleft | CC BY-SA | ✅ container-only | ❌ |
noncommercial | CC BY-NC, BY-NC-ND | ✅ container-only | ❌ |
proprietary / unknown | all rights reserved; ODbL (not granted) | ❌ | ❌ |
| Container-only (policy v2, 2026-06-10): license explicit in meta.ttl + | |||
| manifest.json; no semantic changes (N-Quads formatting only); never in | |||
| static artifacts — the demo builder filters these schemes automatically. | |||
| When in doubt, treat as not bundleable and mark "To investigate". |
CANDIDATES.md with publisher,
license, class, formats, and a working source URL. Note the review date.third_party/skos/<slug>/meta.ttl via the
add-skos-scheme skill. For large dumps, start with skosdex:bundle false.n3 cannot
parse RDF/XML, so RDF/XML-only sources need conversion (riot, rapper) or a
per-scheme helper in the scheme's tools/ folder.CANDIDATES.md current when you touch it.