librarian

Audits documentation to enforce SSO T and sync with codebase changes.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/ResearchMonkey/Foundation_template --skill librarian-researchmonkey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: librarian
Source: https://github.com/ResearchMonkey/Foundation_template/tree/main/.agent/skills/librarian
Command: npx skills add https://github.com/ResearchMonkey/Foundation_template --skill librarian-researchmonkey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation and knowledge management often drift from the codebase, creating silos and conflicting assumptions. The Librarian helps enforce a single source of truth, manage the lifecycle of memory and artifacts, and keep docs in sync with code.

Core Features & Use Cases

  • SSOT enforcement across domains to ensure a single authoritative source per topic.
  • Doc-code synchronization that keeps API docs, architecture decisions, and anti-patterns aligned with the codebase.
  • Memory health monitoring and artifact lifecycle management (Draft → Active → Historic) to prevent stale information.
  • Audit-ready reporting and drift detection to resolve conflicts and maintain documentation integrity.
  • Use Case: When code changes introduce new APIs or decisions, run audits to update docs and resolve discrepancies.

Quick Start

Audit current docs to enforce SSOT and refresh memory health.

Frequently Asked Questions about librarian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain a single source of truth for project documentation?

To maintain a single source of truth for documentation, you need to align code, decisions, and artifacts across domains. This Skill enforces SSOT by applying structured gates that prevent conflicting assumptions and documentation silos from forming.

How do I keep API docs and architecture decisions synchronized with the codebase?

Keeping API docs synchronized with the codebase requires continuous doc-code alignment. This Skill audits documentation when code changes introduce new APIs or decisions, automatically detecting drift to resolve discrepancies and update artifacts.

What is the best way to audit documentation for staleness and conflicts?

Auditing documentation for staleness involves monitoring memory health and artifact lifecycles. This Skill generates audit-ready reports that detect drift, resolve conflicts, and manage the lifecycle from Draft to Active to Historic to prevent stale information.

How do I manage artifact lifecycles to prevent stale documentation?

Managing artifact lifecycles to prevent stale documentation requires tracking state transitions from Draft to Active to Historic. This Skill governs artifact lifecycles and monitors memory health to ensure outdated information is automatically identified and transitioned.

When should I run a documentation audit for memory health monitoring?

You should run a documentation audit for memory health monitoring whenever code changes introduce new APIs or architectural decisions. This detects discrepancies early, resolves drift, and ensures documentation integrity is maintained across all project domains.