knowledge-layer
FeaturedHigh-level deployment wrapper over RepoBrain core with graph-first knowledge injection and all-file support. Exposes `refresh_filesystem` and `ask_filesystem` for building and querying the knowledge graph.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- study8677
- Repository
- study8677/repobrain
- Created
- 9 months ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
project-knowledge
Build and maintain a durable, project-local knowledge base with provenance-tracked sources, injection-linted pages, and a generated index, using the bundled deterministic knowledge_tool.py CLI. Use when the user says "build a project knowledge base", "set up a knowledge layer", "register this source", "draft a knowledge page", "lint the knowledge pages", "regenerate the knowledge index", "export a knowledge bundle", or "/agent-collab:project-knowledge." Also offer this proactively when agent memory limits truncate project context across sessions, or when the same sources keep being re-read and re-synthesized because no durable, citable project-local record exists.
knowledge
Manage the LifeOS Knowledge Archive — a curated, typed graph of People, Companies, Ideas, and Research notes with typed related: links; search, add, harvest, develop, ingest, and graph-navigate. USE WHEN knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, ingest, contradictions, knowledge graph, retrieve, mine conversations. NOT FOR session/ISA context recovery (use ContextSearch), published content semantic search across blog/newsletter/X/LinkedIn (use _CONTENTSEARCH), or one-shot URL/YouTube ingestion via the Arbol harvester pipeline (use _HARVEST).
build-codebase-knowledge
Build and maintain a compact, deterministic repository-intelligence layer and task resolver to minimize broad repository scans, unnecessary file reads, context-window usage, and stale architectural assumptions. Use when navigating a complex codebase, starting a new task, resolving relevant files, or updating repository knowledge after code changes.