context-graph
Use when storing decision traces, querying past precedents, or implementing learning loops. Load in COMPLETE state or when needing to learn from history. Covers semantic search with Voyage AI embeddings, ChromaDB for cross-platform vector storage, and pattern extraction from history.
What this skill does
# Context Graph
Living records of decision traces with semantic search. Find similar past decisions by meaning, not keywords.
## Setup
**MCP Server (recommended):**
The context-graph MCP server provides the same functionality via tools:
- `context_store_trace` - Store decisions with embeddings
- `context_query_traces` - Semantic search
- `context_get_trace` - Get by ID
- `context_update_outcome` - Mark success/failure
- `context_list_traces` - List with pagination
- `context_list_categories` - Category breakdown
Configure in `.claude/mcp.json`:
```json
{
"mcpServers": {
"context-graph": {
"command": "uv",
"args": ["--directory", "context-graph-mcp", "run", "python", "server.py"],
"env": {"VOYAGE_API_KEY": "your_key_here"}
}
}
}
```
**CLI Scripts (alternative):**
```bash
# 1. Install dependencies
pip install voyageai chromadb
# 2. Set Voyage AI key
export VOYAGE_API_KEY="your_key_here"
# 3. Store/query traces
python scripts/store-trace.py "DECISION"
python scripts/query-traces.py "similar situation"
```
## Instructions
1. **Store trace** after decisions with category + outcome
2. **Query precedents** when facing similar situations
3. **Update outcome** to success/failure after validation
## Quick Commands (MCP)
```
context_store_trace(decision="Chose FastAPI for async", category="framework")
context_query_traces(query="web framework choice", limit=5)
context_update_outcome(trace_id="trace_abc...", outcome="success")
```
## Quick Commands (CLI)
```bash
# Store a decision trace
python scripts/store-trace.py "Chose FastAPI over Flask for async support" --category framework
# Find similar past decisions
python scripts/query-traces.py "web framework selection"
# Query by category
python scripts/query-traces.py "database choice" --category architecture --limit 3
# Output JSON for parsing
python scripts/query-traces.py "error handling" --json
```
## Trace Schema
| Field | Description |
|-------|-------------|
| `id` | Unique trace identifier |
| `timestamp` | When stored |
| `category` | Grouping (framework, api, error, etc.) |
| `decision` | What was decided (text) |
| `outcome` | pending / success / failure |
| `state` | State machine state when decided |
| `feature_id` | Related feature (if any) |
| `embedding` | 1024-dim vector (Voyage AI) |
## Categories
- `framework` - Tech stack choices
- `architecture` - Design patterns, structure
- `api` - Endpoint design, contracts
- `error` - Failure modes, fixes
- `testing` - Test strategies
- `deployment` - Infra decisions
## When to Use
| Situation | Action |
|-----------|--------|
| Made a technical decision | Store trace with category |
| Facing similar problem | Query traces before deciding |
| Session complete | Query category → extract patterns |
| Repeating error | Query traces for that error |
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.