Install
$ agentstack add skill-cdeust-cortex-cortex-setup-project ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
- 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 runpg_isreadyor any PostgreSQL setup when this passes). Proceed to Phase 2. - Only if
memory_statsfails: callcortex:check_setup({})(backend-aware diagnostics) to identify the failure.
- SQLite backend reported: fix per the check output (usually
~/.claude/methodologypermissions or a corruptmemory.db); do NOT install PostgreSQL. - PostgreSQL backend reported: run
pg_isreadyvia bash, thenbash "${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh"automatically. Do not ask for permission. After setup.sh completes, callcortex: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
- Call
cortex:rebuild_profiles({"force": true})to scan all session history and build cognitive profiles per domain. - This creates the domain hubs that memories, entities, and discussions link to. It must run before seeding.
- Record the domain count for the final summary.
Phase 3: Codebase Seeding
- Call
cortex:seed_project({"directory": ""})where `` is the current working directory. - Record the count of discoveries for the final summary.
Phase 3b: Pipeline Codebase Analysis (Optional)
The ai-automatised-pipeline 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.
- Detection: attempt
cortex:ingest_codebase({"project_path": ""}). If it succeeds, record the counts (wiki pages, memory entities, KG edges) for the summary and skip to Phase 4. - If
ingest_codebasefails withMcpConnectionError(pipeline not installed/configured):
- Check if the sibling checkout exists at
../anthropic/ai-automatised-pipeline/Cargo.toml(or equivalent). If so, runbash -c 'cd ../anthropic/ai-automatised-pipeline && 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.
- 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
- Call
cortex:backfill_memories({"dry_run": true, "max_files": 500})to preview available session files. - If files are available, call
cortex:backfill_memories({"max_files": 500, "min_importance": 0.35})to import. - Record the count of imported memories for the final summary.
Phase 5: Consolidation and Verification
- Call
cortex:consolidate({})to run decay, compression, CLS, and causal discovery on all memories. - Call
cortex:memory_stats({})to get the final system state. - Call
cortex:detect_gaps({})to identify knowledge gaps.
Final Summary
After all phases complete, print a single summary block:
Cortex Setup Complete
---------------------
Domains:
Memories stored:
Entities:
Relationships:
Pipeline:
Gaps found:
Do not print intermediate status updates between phases beyond what the tool calls themselves return. One summary at the end.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: cdeust
- Source: cdeust/Cortex
- License: MIT
- Homepage: https://ai-architect.tools
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.