hippocampus

Manage persistent knowledge bases with tiered markdown and binary asset storage.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MariusWilsch/clarity-workflow-plugin --skill hippocampus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hippocampus
Source: https://github.com/MariusWilsch/clarity-workflow-plugin/tree/main/skills
Command: npx skills add https://github.com/MariusWilsch/clarity-workflow-plugin --skill hippocampus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a centralized, organized knowledge base for your AI, ensuring that all markdown files and binary assets are stored and managed consistently, preventing scattered information and enabling efficient retrieval.

Core Features & Use Cases

  • Centralized Markdown Storage: Enforces a strict rule that all markdown files must be stored in the hippocampus, preventing clutter in project directories.
  • Tiered Storage: Supports both global (cross-project) and project-specific storage tiers.
  • Binary Asset Management: Organizes non-markdown files (images, PDFs, audio, etc.) into structured folders with index files.
  • Use Case: When creating documentation, tutorials, or storing reference materials, this Skill ensures they are saved in a discoverable and organized manner within the designated hippocampus directories.

Quick Start

Use the hippocampus skill to search for documentation on prompt engineering patterns.

Frequently Asked Questions about hippocampus

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

FAQPage Schema
How do I organize a persistent markdown knowledge base for AI?

To organize a persistent markdown knowledge base for AI, use a centralized storage convention that enforces strict directory rules. This prevents file clutter by ensuring all markdown documentation is systematically stored and easily discoverable.

What is the best way to manage binary assets in a knowledge base?

The best way to manage binary assets in a knowledge base is using automated file organization with indexed structures. This routes non-markdown files like images and PDFs into specific folders, generating index files to facilitate efficient asset retrieval.

Can I use tiered storage for project-specific and global documentation?

Yes, you can use tiered storage for project-specific and global documentation. This mechanism supports both cross-project and project-level storage tiers, allowing you to scope markdown files and binary assets appropriately across different contexts.

How do I prevent scattered markdown files in my project directories?

To prevent scattered markdown files in project directories, enforce a centralized storage convention. By mandating that all markdown documentation is saved within a designated knowledge base, you eliminate clutter and ensure consistent file organization.

Does this knowledge base convention support automated file discovery?

Yes, this knowledge base convention supports automated file discovery. It facilitates the discovery, creation, and editing of documentation by maintaining a strict storage structure and using index files for binary asset management.