qmd-knowledge
FeaturedManage project knowledge with qmd — captures learnings, decisions, and conventions
Install
Quality Score: 89/100
Skill Content
Details
- Author
- jellydn
- Repository
- jellydn/my-ai-tools
- Created
- 7 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
qmd-search
Answers user questions by searching a local Markdown repository using the `qmd` (Quick Markdown Search) CLI toolkit. Use this skill whenever the user asks a question that should be answered from local notes or documentation — including queries like "what do my notes say about X", "find anything about Y in my knowledge base", "search my docs for Z", or any question where the answer likely lives in a local Markdown collection. Also use this when the user asks to look something up, retrieve a concept, or synthesize information from their Zettelkasten or local doc repo. Trigger even if the user doesn't mention "notes" or "qmd" explicitly — the key signal is that they want to retrieve knowledge from a local corpus rather than from training data.
scribe-kb
Read, write, and search a scribe-managed knowledge base (markdown vault with frontmatter conventions, wikilinks, and qmd hybrid search). Use when the user's project has a scribe.yaml (KB root) or a .claude/<kb_name>/ drop-file directory (consumer side), or when they mention scribe, scriptorium, qmd, drop files, or "my KB". Covers frontmatter schema, wikilink syntax, drop-file pattern, search via qmd, and directory taxonomy.
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.