wiki_enrichlisted

# LLM Wiki — Enrich Skill (wiki_enrich) > **Resolving script paths (read first):** Commands below invoke scripts as `<BIN>/X.py` (and a few as `<SKILLS>/...`). Resolve these to **absolute paths once** before running anything: > > - `<SKILL_DIR>` = the directory this `SKILL.md` lives in. > - `<SKILLS>` = the `skills/` folder containing this skill = `<SKILL_DIR>/..` > - `<BIN>` = the `bin/` folder beside it = `<SKILL_DIR>/../../bin` > > Do **not** hardcode a fixed prefix like `.agents/bin` or `../bin`: shell relative paths resolve against the current working directory (usually the topic root), not this skill's location. Once resolved, `<BIN>` is typically `.agents/bin` when invoked from the hub root, or `.claude/bin` from inside a topic directory. This skill handles "gap-filling" for concept extraction. Due to token limits, initial compilations might miss secondary theorems, lemmas, or physics corollaries. This skill ensures high concept density. > **Tooling (framework-agnostic):** This skill is written tool-agnostic. Map each capability to your own agent's tool — *read-file* (`Read` in Claude Code, `view_file` in Antigravity), *sub-agent / parallel task* (`Task`/`Agent` in Claude Code, `invoke_subagent` in Antigravity), *shell* (`Bash`/`PowerShell`). Use the closest equivalent your framework provides; if a parallel sub-agent tool is unavailable, mine the chunks sequentially yourself. When the user asks to enrich, deep-dive, or查漏补缺 (fill gaps) on a paper: 0. **Pre-enrichme