gramaton-ai
OrganizationVersioned, epistemic memory for AI agents.
Categories
Indexed Skills (6)
benchmark-extract
Use to ingest a LongMemEval-style benchmark dataset into the isolated benchmark gramaton store via Claude Code sub-agents. Each unique haystack session becomes one Gramaton session via the production `session_prepare` → `session_commit` path. User-triggered by "run benchmark extraction", "ingest LongMemEval-S", "load benchmark data". Requires the `gramaton-bench` MCP server live on port 7338; see docs/benchmarks.md for setup.
migrate-to-api
Use when moving an existing inline HTTP/MCP handler (server/handler_X.go, server/mcp_X.go) into the api/ canonical surface. One-time-per-cluster work; mirrors PR
new-operation
Use when adding a new operation to the api/ package (new capture/search/branch/backup/etc method, new MCP tool, new HTTP endpoint). Scaffolds the typed Request/Response, XxxDescription constant, wires HTTP + MCP stdio + CLI MCP proxy transports, and stubs tests. Triggers include "add a new MCP tool for X", "new api operation", "add an endpoint for Y", "scaffold Z under api/". Do NOT use for migrating an existing inline handler — that's migrate-to-api.
pre-merge-check
Use before opening a PR, committing a substantive change, or declaring a feature done. Runs the mechanical Pre-merge Checklist from CONTRIBUTING.md — build, test, race, vet, changelog presence, description constant consistency. Triggers include "ready to commit", "about to open a PR", "ship this", "is this done", "final check". Always run this before telling the user a task is complete.
store-health
Use to diagnose the health of a Gramaton knowledge store. Aggregates the standard health probes into a single report — pending classification, orphans, duplicates, stale-temporal, refuted, expiring, ephemeral survivors. Identifies when piggyback curation should run and when dedup is worth attempting. Triggers include "check store health", "is my store healthy", "audit the knowledge store", "what does the store look like", "store status". Works against any Gramaton instance (the dev's dogfood store or a user's production store).
gramaton
Persistent memory for this user via Gramaton MCP tools. Use when the user references past decisions, prior sessions, project context, or preferences; mentions a ticket (a ULID or project ticket codename); says remember, save, or store; asks about plans, status, or architecture; or works with tasks, TODOs, and backlogs (collections). Covers search, save, session extraction, and collection workflows.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.