- Home
- Skills
- Vectorize Io
- Hindsight
- Hindsight Self Hosted
hindsight-self-hosted_skill
- Python
1.2k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill vectorize-io/hindsight --skill hindsight-self-hosted- SKILL.md4.7 KB
Overview
This skill connects your agent to a self-hosted Hindsight server so team knowledge, project conventions, and task learnings are stored and shared. Use it to retain discoveries, surface relevant context before work, and keep a searchable team memory that improves decision-making. It emphasizes immediate, specific entries and team-first organization.
How this skill works
The skill uses the Hindsight CLI to retain, recall, and reflect on memories in a named bank on your self-hosted server. It checks that the CLI is configured with api_url and api_key in ~/.hindsight/config and then issues commands like memory retain, memory recall, and memory reflect against the provided bank ID. Stored memories can include contexts (procedures, learnings, preferences) to make recall more precise.
When to use it
- Before starting any non-trivial task or new work area
- When making implementation or tooling decisions
- When answering questions about the codebase or onboarding someone
- After discovering a workaround, bug fix, or configuration detail
- To capture individual preferences that affect collaboration
Best practices
- Store discoveries immediately with concrete commands and outcomes
- Be specific: include exact flags, versions, and error symptoms
- Attribute personal preferences to the named individual
- Include both what worked and what did not work
- Recall relevant memories before proposing solutions or writing code
Example use cases
- Record that the project requires Node 20 and tests need NODE_ENV=test
- Recall coding standards (ESLint + Airbnb, Prettier) before refactoring a module
- Store a successful deployment workaround and the exact commands used
- Save an individual’s PR or commit message preference for future collaboration
- Reflect on past incidents to synthesize a recommended approach for a current task
FAQ
Install the hindsight CLI if missing, then create ~/.hindsight/config with api_url and api_key and set file permissions to 600. Ask your admin for the bank ID to use.
What should I store versus keep private?
Store team-relevant knowledge: conventions, procedures, workarounds, and architecture rationale. For personal preferences, include the person’s name so others can respect them; avoid storing sensitive credentials or private data.