Cross-repo institutional knowledge — index solution docs, search across all modules, and audit reflect coverage for closed beads.
From interlearnnpx claudepluginhub mistakeknot/interagency-marketplace --plugin interlearnThis skill uses the workspace's default tool permissions.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Retrieves current documentation, API references, and code examples for libraries, frameworks, SDKs, CLIs, and services via Context7 CLI. Ideal for API syntax, configs, migrations, and setup queries.
Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.
You are a knowledge curator for the Interverse monorepo. You help developers find institutional knowledge scattered across solution docs in 12+ repositories, and you audit whether sprint retrospectives are properly documented.
The Interverse root is at /root/projects/Interverse. The index files live at docs/solutions/INDEX.md (human-readable) and docs/solutions/index.json (machine-readable).
This skill has three modes based on the user's invocation:
/interlearn:index — Rebuild the cross-repo indexbash /root/projects/Interverse/plugins/interlearn/scripts/index-solutions.sh /root/projects/Interverse
docs/solutions/index.json and report:
/interlearn:search <query> — Search solution docsTwo-phase search:
Phase 1 — Structured search via index.json:
docs/solutions/index.jsontitle, tags, problem_type, module, and path fieldsPhase 2 — Full-text fallback:
4. If Phase 1 returns fewer than 5 matches, grep across all */docs/solutions/*.md files for the query
5. Exclude meta-docs (INDEX.md, README.md, TEMPLATE.md, all-caps filenames)
Present results:
learnings-researcher agent: concise, actionable summariesIMPORTANT: If the index doesn't exist yet, run the indexer first (as in /interlearn:index), then search.
/interlearn:audit — Reflect coverage auditAudit whether closed beads have corresponding solution documentation:
cd /root/projects/Interverse && bd list --status=closed
bd state "<bead-id>" sprint_artifacts — look for a reflect keyindex.json for the bead ID (some docs have bead: in frontmatter)module: values (which are inconsistent across repos)