cortex-setup-project
/cortex-setup-project
Bootstrap Cortex for a new project or import existing session history. Use when the user says 'set up Cortex', 'seed this project', 'import my history', 'backfill memories', 'bootstrap memory', 'initialize Cortex for this project', or when starting to use Cortex on an existing codebase that already has Claude Code conversation history.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Bootstrap Cortex for a new project or import existing session history. Use when the user says 'set up Cortex', 'seed this project', 'import my history', 'backfill memories', 'bootstrap memory', 'initialize Cortex for this project', or when starting to use Cortex on an existing codebase that already has Claude Code conversation history.
Triggers from the description
Original author description
Bootstrap Cortex for a new project or import existing session history. Use when the user says 'set up Cortex', 'seed this project', 'import my history', 'backfill memories', 'bootstrap memory', 'initialize Cortex for this project', or when starting to use Cortex on an existing codebase that already has Claude Code conversation history.
How it works
- Phase 1: Infrastructure Verification
- Phase 2: Build Methodology Profiles
- Phase 3: Codebase Seeding
- Phase 4: History Import
- Phase 5: Consolidation and Verification
- Final Summary
SKILL.md preview
---
name: cortex-setup-project
description: "Bootstrap Cortex for a new project or import existing session history. Use when the user says 'set up Cortex', 'seed this project', 'import my history', 'backfill memories', 'bootstrap memory', 'initialize Cortex for this project', or when starting to use Cortex on an existing codebase that already has Claude Code conversation history."
---
# Setup Project — Fully Autonomous Bootstrap
Execute all four phases sequentially without asking the user any questions. If a phase fails, attempt automatic recovery before reporting the error. Never ask the user to run commands manually or choose between options.
## Phase 1: Infrastructure Verification
1. Call `cortex:memory_stats({})` to verify store connectivity. If it succeeds, the store is healthy — this covers **both** backends (the zero-config SQLite default needs no PostgreSQL, so do NOT run `pg_isready` or any PostgreSQL setup when this passes). Proceed to Phase 2.
2. Only if `memory_stats` fails: call `cortex:check_setup({})` (backend-aware diagnostics) to identify the failure.
- SQLite backend reported: fix per the check output (usually `~/.claude/methodology` permissions or a corrupt `memory.db`); do NOT install PostgreSQL.
- PostgreSQL backend reported: run `pg_isready` via bash, then `bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh"` automatically. Do not ask for permission. After setup.sh completes, call `cortex:memory_stats({})` again to verify.
- If it still fails, report the error output and **stop**. Do not continue to later phases.
## Phase 2: Build Methodology Profiles
1. Call `cortex:rebuild_profiles({"force": true})` to scan all session history and build cognitive profiles per domain.
2. This creates the domain hubs that memories, entities, and discussions link to. It must run before seeding.
3. Record the domain count for the final summary.
## Phase 3: Codebase Seeding
1. Call `cortex:seed_project({"directory": "<cwd>"})` where `<cwd>` is the current working directory.
2. Record the count of discoveries for the final summary.
### Phase 3b: Pipeline Codebase Analysis (Optional)
The ai-architect-mcp-codebase MCP server provides structured codebase analysis (symbol graph, processes, communities, cross-file impact). It is optional — Cortex core memory/recall works without it. Enable only if the user asks for "deeper code understanding", "symbol-level memory", or the codebase is large (>5k files) where substring-based hooks underperform.
1. Detection: attempt `cortex:ingest_codebase({"project_path": "<cwd>"})`. If it succeeds, record the counts (wiki pages, memory entities, KG edges) for the summary and skip to Phase 4.
2. If `ingest_codebase` fails with `McpConnectionError` (pipeline not installed/configured):
- Check if the sibling checkout exists at `../anthropic/ai-architect-mcp-codebase/Cargo.toml` (or equivalent). If so, run `bash -c 'cd ../anthropic/ai-architect-mcp-codebase && cargo install --path . 2>&1 | tail -20'` (accepts ~1-2 min compile) and re-run the ingest.
- If the source checkout is missing or cargo is unavailable, **skip Phase 3b silently** and proceed to Phase 4. Do NOT block setup on this.
3. The pipeline's auto-wire happens on every SessionStart via `pipeline_discovery`, so once the binary exists on PATH (or sibling source is built), future sessions pick it up automatically. No manual mcp-connections.json editing needed.
## Phase 4: History Import
1. Call `cortex:backfill_memories({"dry_run": true, "max_files": 500})` to preview available session files.
2. If files are available, call `cortex:backfill_memories({"max_files": 500, "min_importance": 0.35})` to import.
3. Record the count of imported memories for the final summary.
## Phase 5: Consolidation and Verification
1. Call `cortex:consolidate({})` to run decay, compression, CLS, and causal discovery on all memories.
2. Call `cortex:memory_stats({})` to get the final system state.
3. Call `cortex:detect_gaps({})` to identify knowledge gaps.
## Final Summary
After all phases complete, print a single summary block:
```
Cortex Setup Complete
---------------------
Domains: <count from rebuild_profiles>
Memories stored: <total from memory_stats>
Entities: <count from memory_stats>
Relationships: <count from memory_stats>
Pipeline: <"active — N wiki pages, M memories" | "skipped (not installed)">
Gaps found: <count and brief description from detect_gaps>
```
Do not print intermediate status updates between phases beyond what the tool calls themselves return. One summary at the end.
Versions
The database has no other skills named cortex-setup-project.
Database snapshot: 13.11.2026 · package version a88cf4407227 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95cortex-import
Import memories from other AI memory systems into Cortex. Supports claude-mem (SQLite), Claude Desktop sessions, ChatGPT web export (JSON), Gemini Takeout (JSON), Cursor conversations, and Claude Code JSONL. Use when the user says 'import from claude-mem', 'migrate memories',… - 100cortex-run
ONLY load this skill when the user explicitly types $cortex-run or /cortex-run. NEVER load this skill from auto-routing hooks or keyword matching. For auto-routed prompts, use snowflake-cortex-code:cortex-router instead. - 96cortex-mcp-project
Use when working on the Cortex MCP server repo. - 100cortex-evolve
Save knowledge to the cortex vault. Use when the user says "存到 cortex", "記一下", "save to cortex", "記到筆記", "cortex evolve", or when the session-suggest hook recommends saving content. Handles Notes and Projects. - 90cortex-context-digest
整理当前会话上下文 → 记忆库. 自动判定全局 (L0 关键词/跨项目语义) vs 项目级 (默认/含 repo 特定); 用户可 --scope global|project 显式覆盖. 复用 cortex-extract 三轴 + cortex-schema 路径. 任务收尾或显式 'digest 上下文/沉淀' 触发. - 100cortex-m
Build, test, or develop the Cortex-M (CMSIS-NN) backend. Use when working on backends/cortex_m/, running Cortex-M tests, or exporting models for Cortex-M targets.