メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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 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 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.
SOC 職業分類に基づく
| name | build-data-bundle |
| description | 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. |
| license | Apache-2.0 |
The bundle is the deployable dataset that the SPARQL + Solr container ships.
node scripts/skosdex bundle # merge eligible canonical.nq.gz -> dist/bundle.nq.gz (+ manifest.json)
node scripts/skosdex solr-docs # derive dist/solr-docs.json from the bundle
node scripts/skosdex demo # bake dist/demo.html (standalone browser)
node scripts/skosdex site # bundle + solr-docs + demo, publish into docs/ (GitHub Pages)
node scripts/skosdex build # full pipeline incl. fetch/normalize/canonicalize
Prereq: the committed canonical.nq.gz files are Git LFS objects — run
git lfs pull after a fresh clone or bundle reads empty pointer files.
bundle doeslicenseClass is open/public-domain and
skosdex:bundle is not false. Everything else is excluded with a reason.canonical.nq.gz, places its triples in a
named graph equal to its conceptSchemeURI, and prefixes blank node
labels per-scheme, so multiple schemes merge without collisions.dist/bundle.nq.gz plus dist/manifest.json listing
included/excluded schemes, licenses, and quad counts — check the manifest to
confirm no copyleft/NC data slipped in.| File | Committed? | Consumed by |
|---|---|---|
dist/bundle.nq.gz | no (gitignored) | Oxigraph (gunzipped + baked into the skosdex/sparql image) |
dist/solr-docs.json | no | Solr (posted by the solr-init container) |
dist/manifest.json | no | provenance / license audit |
dist/demo.html | no | standalone browser; copied to docs/index.html |
docs/ (index.html, bundle.nq.gz, solr-docs.json, manifest.json) | yes | GitHub Pages site |
Note: everything in dist/ is a gitignored build output. docs/ IS committed
(it's the published site) and holds plain (non-LFS) small files, because
GitHub Pages serves LFS pointers, not content.
Run bundle/build before docker compose build (see the run-endpoints
skill), and site to refresh the Pages demo.