Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

hindsight-docs — Claude Code skill: what it does, how to install

This skill gives AI agents Hindsight documentation for architecture, APIs, configuration, and SDKs. Use it when adding Hindsight memory to an agent.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add vectorize-io/hindsight --skill hindsight-docs -a claude-code
Open on GitHub

What hindsight-docs does

hindsight-docs gives an agent the Hindsight documentation, covering its biomimetic memory system and core operations: retain, recall, and reflect. It explains memory banks, dispositions, mental models, API configuration, deployment, and SDK integrations for Python, Node.js, Rust, and the CLI.

The material is organized under references/, with best practices, an FAQ, an OpenAPI specification, API guides, SDK pages, and integration notes. The agent can locate files with Glob, search documentation with Grep, and read the relevant pages. Retrieval is documented across semantic, BM25, graph, and temporal strategies.

There is one operational detail to check before using it: queries across multiple memory banks require client-side orchestration. Conversation updates use the same document_id, while configuration is handled through HINDSIGHT_API_* environment variables.

What it helps with

  • understand Hindsight architecture
  • find parameters for retain, recall, and reflect
  • configure memory banks and dispositions
  • choose an SDK for Python, Node.js, or Rust
  • inspect API endpoints and configuration

Example prompts for the agent

  • Read `references/best-practices.md` and explain how to set up missions, tags, and observation scopes for my agent.
  • Find the Hindsight API Server deployment instructions for Docker and list the relevant `HINDSIGHT_API_*` settings.
  • Compare semantic, BM25, graph, and temporal retrieval for a recall request, then point to the related API endpoints.

How to install hindsight-docs

1Skills CLI (Vercel)

npx skills add vectorize-io/hindsight --skill hindsight-docs -a claude-code

2Manually: put the files in place

~/.claude/skills/hindsight-docs/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/hindsight-docs/

Similar

watch bradautomates Analyzes a video from a URL or local path, collects frames and a transcript, then lets the agent answer questions about the footage. Useful for video review inside an IDE. Claude Code CX Codex Cursor +1 17,100installs anysearch anysearch-ai This skill gives an agent web search, domain-specific queries, parallel batch search, and page extraction. Use it when a task needs current information or a claim needs checking. Claude Code CX Codex Cursor +1 38,500installs gemini-api-dev official google-gemini Guides coding agents to write Gemini API code in Python and TypeScript using current SDKs, interaction endpoints, and active models. Claude Code CX Codex Cursor +1 25,100installs opencli-autofix jackwener Repairs broken OpenCLI adapters when websites alter their DOM or APIs. The agent inspects trace logs, explores live pages, and applies targeted patches. Claude Code CX Codex Cursor +1 17,600installs book-to-skill virgiliojr94 Turns books and documents into structured agent skills with frameworks, principles, and techniques. Useful when an agent should apply an author's methods while working. Claude Code CX Codex Cursor +1 8,400installs security-best-practices github.com/openai/skills A skill that reviews code against security best practices for Python, JavaScript/TypeScript and Go, then suggests fixes. Claude Code CX Codex Cursor +1 357installs setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. Claude Code 1,052,851installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. Claude Code 711,230installs

Questions about hindsight-docs

How do I install hindsight-docs in Claude Code?

Run npx skills add vectorize-io/hindsight --skill hindsight-docs -a claude-code, run npx skills add vectorize-io/hindsight --skill hindsight-docs -a claude-code again, then check ~/.claude/skills/hindsight-docs/SKILL.md.

What does hindsight-docs do?

The skill gives an agent Hindsight documentation covering architecture, APIs, memory bank configuration, retrieval strategies, and SDKs. It helps the agent locate the right material in references/.

What should I know about queries across multiple memory banks?

Queries across multiple memory banks require client-side orchestration. Use the same document_id when a conversation is updated over time.

Source text

SKILL.md · MIT
---
name: hindsight-docs
description: Complete Hindsight documentation for AI agents. Use this to learn about Hindsight architecture, APIs, configuration, and best practices.
---

# Hindsight Documentation Skill

Complete technical documentation for Hindsight - a biomimetic memory system for AI agents.

## When to Use This Skill

Use this skill when you need to:
- Understand Hindsight architecture and core concepts
- Learn about retain/recall/reflect operations
- Configure memory banks and dispositions
- Set up the Hindsight API server (Docker, Kubernetes, pip)
- Integrate with Python/Node.js/Rust SDKs
- Understand retrieval strategies (semantic, BM25, graph, temporal)
- Debug issues or optimize performance
- Review API endpoints and parameters

## Documentation Structure

All documentation is in `references/` organized by category:

```
references/
├── best-practices.md # START HERE — missions, tags, formats, anti-patterns
├── faq.md            # Common questions and decisions
├── changelog/        # Release history and version changes (index.md + integrations/)
├── openapi.json      # Full OpenAPI spec — endpoint schemas, request/response models
├── developer/
│   ├── api/          # Core operations: retain, recall, reflect, memory banks
│   └── *.md          # Architecture, configuration, deployment, performance
└── sdks/
    ├── *.md          # Python, Node.js, CLI, embedded
    └── integrations/ # Framework and tool integrations
```

## How to Find Documentation

### 1. Find Files by Pattern (use Glob tool)

```bash
# Core API operations
references/developer/api/*.md

# SDK documentation
references/sdks/*.md
references/sdks/integrations/*.md

# Find specific topics
references/**/configuration.md
references/**/*python*.md
references/**/*deployment*.md
```

### 2. Search Content (use Grep tool)

```bash
# Search for concepts
pattern: "disposition"        # Memory bank configuration
pattern: "graph retrieval"    # Graph-based search
pattern: "helm install"       # Kubernetes deployment
pattern: "document_id"        # Document management
pattern: "HINDSIGHT_API_"     # Environment variables

# Search in specific areas
path: references/developer/api/
pattern: "POST /v1"           # Find API endpoints

path: references/sdks/
pattern: "def |async def "    # Find Python examples
```

### 3. Read Full Documentation (use Read tool)

```
references/developer/api/retain.md
references/sdks/python.md
references/sdks/integrations/litellm.md
```

## Start Here: Best Practices

Before reading API docs, read the best practices guide. It covers practical rules for missions, tags, content format, observation scopes, and anti-patterns — the fastest way to integrate correctly.

```
references/best-practices.md
```

## Key Concepts

- **Memory Banks**: Isolated memory stores (one per user/agent)
- **Retain**: Store memories (auto-extracts facts/entities/relationships)
- **Recall**: Retrieve memories (4 parallel strategies: semantic, BM25, graph, temporal)
- **Reflect**: Disposition-aware reasoning using memories
- **document_id**: Groups messages in a conversation (upsert on same ID)
- **Dispositions**: Skepticism, literalism, empathy traits (1-5) affecting reflect
- **Mental Models**: Consolidated knowledge synthesized from facts

## Notes

- Code examples are inlined from working examples
- Configuration uses `HINDSIGHT_API_*` environment variables
- Database migrations run automatically on startup
- Multi-bank queries require client-side orchestration
- Use `document_id` for conversation evolution (same ID = upsert)

---

**Auto-generated** from `hindsight-docs/docs/` and `hindsight-docs/docs-integrations/`. Run `./scripts/generate-docs-skill.sh` to update.

© vectorize-io · MIT · vectorize-io/hindsight

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor