kglisted

Load relevant entities from the bstack knowledge graph (research/entities/) for a given topic. Two-tier scoring: tier-1 (catalog-only, ~5ms — slug + tags + claim + links + sources match against docs/knowledge-index.md) is the fast first pass and the only stage for high-confidence exact-slug/tag queries; tier-2 (body-grep fallback, ~300ms — auto-fires when tier-1 returns < N matches OR its best hit is below the confidence floor, default 18) recovers topics whose vocabulary appears in entity prose but not the dense catalog (hit rate jumps from 70% → 100% on representative queries; this is hit rate ≥1, not true recall@N). Surfaces top-N entity bodies as a single context block the agent reasons over. This is a LOAD skill, not a query DSL — querying is what the agent does once loaded. Implements the LLM-as-index architecture (BRO-1223): substrate canonical, one projection (catalog) routes, agent IS the query engine. Empirical: peak per-query context drops from 29% → 4.6% of 1M (6.3× reduction); cumulative session
broomva/skills · ★ 3 · AI & Automation · score 75

Install: claude install-skill broomva/skills

# kg — knowledge graph loader Load relevant entities for: **$ARGUMENTS** ## Purpose The bstack knowledge graph lives at `research/entities/**/*.md` (~250 entities, ~1.1 MB, ~280k tokens). It fits in any 1M-context model with 3.5× headroom — meaning the LLM **is** the index. This skill performs the routing step: reads the dense catalog at `docs/knowledge-index.md`, ranks entities by topical relevance, and surfaces the top-N bodies as a single context block. The agent does the rest: traversal, inference, contradiction detection, semantic comparison — all by reading. There is no SQL layer, no embeddings, no typed-edge schema. The substrate is canonical; the catalog routes; the agent reasons. ## Usage ``` /kg load <topic> # default: top 10 (two-tier; tier-2 auto-fires on few OR weak tier-1 hits) /kg load <topic> --n 20 # widen the load /kg load <topic> --type tool # restrict by entity type /kg load <topic> --terms "recall,persistence" # query expansion: score synonyms/variants too /kg load <topic> --expand 1 # also load 1-hop related: neighbours of the top hits /kg load <topic> --explain # show the per-signal score trace for each loaded entity /kg load <topic> --body-search # force tier-2 body grep unconditionally /kg load <topic> --tier2-floor 0 # disable the confidence gate (tier-2 only on count<--n) /kg load <topic> --json # machine-readable output (for piping) /kg # catalog-only mode: print summary stats + top