Results for “knowledge-base-poisoning”

Build and query AI-powered knowledge bases from claude-mem observations, enabling focused conversational sessions on specific topics.

Manages a multi-layered knowledge system for ingesting, organizing, syncing, and retrieving knowledge across local files, MCP memory, vector stores, and Git repos.

Author, validate, and clean up company SOPs and internal runbooks with 5W2H completeness checks, cross-link validation, and KB hygiene reporting.

Build and maintain a persistent, interlinked markdown knowledge base that compiles knowledge once and keeps it current, with cross-references and contradiction flags.

Persists and recalls agent knowledge across sessions using four approaches: static KB, company wiki, persistent memory, and session brain.

Manage a multi-layered knowledge system for ingesting, organizing, syncing, and retrieving knowledge across local files, MCP memory, vector stores, and Git repos.

Turns a local folder into a searchable, maintainable knowledge base for AI agents, handling setup, navigation, content ingestion, querying, and health checks without external databases or RAG systems.

Builds a personal knowledge base for capturing and retrieving understanding, with structured namespaces for concepts, tools, patterns, and references.

Use to assign ownership, set review cadence, and deprecate support content without breaking self-service or AI grounding. Trigger for "who owns this article", "our KB is out of date", orphan articles, annual review calendar nobody follows, deprecating help content, knowledge governance, or preventing stale articles from quietly harming customers.

Capture conversations and decisions into structured Notion pages for easy reuse as wiki entries, how-tos, decisions, or FAQs with proper linking.

Knowledge-base steward in the spirit of Niklas Luhmann's Zettelkasten. Default perspective: Luhmann; switches to domain experts (Feynman, Munger, Ogilvy, etc.) by task. Enforces atomic notes, connectivity, and validation loops. Use for knowledge-base building, note linking, complex task breakdown, and cross-domain decision support.

Organizes persistent company memory using a PARA-structured knowledge base with daily notes, atomic facts, and entity tracking for cross-session agent recall.

Analyze a codebase and generate onboarding documentation for engineers, tech leads, and contractors, with fast fact-gathering and repeatable outputs.

Consolidates six standard operating procedures for the Knowledge department, covering web content extraction, documentation maintenance, and related workflows.

Structures company knowledge bases for business plan automation, defining a 7-category schema, completeness scoring, and storage layouts for Notion or local Markdown.