メニュー
Use when bringing up, configuring, or troubleshooting the skosdex services — the Oxigraph SPARQL endpoint, the Solr index, and the web frontend via docker compose (or swapping Oxigraph for Apache Jena Fuseki).
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 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.
| name | run-endpoints |
| description | Use when bringing up, configuring, or troubleshooting the skosdex services — the Oxigraph SPARQL endpoint, the Solr index, and the web frontend via docker compose (or swapping Oxigraph for Apache Jena Fuseki). |
| license | Apache-2.0 |
The dataset is served by a small docker compose stack.
npm run build # produce dist/bundle.nq + dist/solr-docs.json first
docker compose up --build
| Service | URL | Notes |
|---|---|---|
| web | http://localhost:8080 | static frontend, same-origin proxy to the others |
| sparql (Oxigraph) | http://localhost:7878/query | dist/bundle.nq baked into the image |
| solr | http://localhost:8983/solr | core skos, loaded by the one-shot solr-init |
The web frontend talks to sparql and solr through nginx proxies
(/sparql/, /solr/) so the browser hits a single origin (no CORS).
npm run build, then docker compose up --build
(the SPARQL image bakes in dist/bundle.nq; solr-init re-posts the docs).serve-read-only. For a writable
endpoint, change the CMD in docker/sparql/Dockerfile to serve.sparql service for
image: stain/jena-fuseki (or secoresearch/fuseki), mount dist/bundle.nq,
and load it via Fuseki's --file/TDB loader. The rest of the stack and the
/sparql/ proxy target are unchanged.OXIGRAPH_TAG build arg in
docker/sparql/Dockerfile; bump it there.