Install
$ agentstack add skill-xbluesky-cortexes-cortex-query ✓ 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
Cortex Query — Search the Vault
Search the cortex Obsidian vault using semantic search.
Resolve Vault Path
Read ~/.cortex/config.json to get vault_path. If the file doesn't exist, tell the user to run /cortex:genesis first.
Search Strategy (Layered)
Layer 1: Vector Search (primary)
Use cortex-vec for semantic search:
cortex-vec search "" --n 5
cortex-vec is installed as a CLI tool (from PyPI via uv tool install cortex-vec or pip — see the README's Quick Start; /cortex:genesis offers the install when it is missing).
Context-aware filtering: If the current session is inside a git repo, detect the repo name and add --repo filter as default scope:
cortex-vec search "" --repo --n 5
The user can override this by saying "search all" or "search across everything".
Additional filters: Apply when the user specifies:
--type note|project|weekly— filter by content type--category Nginx|Linux|...— filter by category
Interpreting scores:
- Score > 0.80: High confidence match — present prominently
- Score 0.60-0.80: Possible match — present as suggestions
- Score " /Notes/ /Projects/
Show matching files with brief excerpts.
### Layer 3: Raw Search (archive, on request)
Only when the user specifically asks about recent sessions or raw data:
```bash
grep -ri "" /Raw/
Show matches with date and repo context.
Response Format
Present results to the user:
Found N results for "":
1. [score] Title (Type, Category/Repo)
→ one-line summary
2. [score] Title (Type, Category/Repo)
→ one-line summary
- Use wikilink format when referencing notes:
[[note-name]] - If multiple matches, list them and ask which one to read
- If user wants details → read the full file
- For Weekly entries, show the date and summary line
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: XBlueSky
- Source: XBlueSky/cortexes
- License: Apache-2.0
- Homepage: https://cortexes.pages.dev
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.