cortex-automate
SolidSet up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to automate memory behavior based on conditions.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- cdeust
- Repository
- cdeust/Cortex
- Created
- 5 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
cortex-remember
Store important decisions, patterns, errors, lessons, and context into Cortex persistent memory. Use when the user says 'remember this', 'save this', 'store this for later', 'note this down', 'don't forget', 'this is important', 'bookmark this', or when a significant decision, bug fix, architecture choice, or lesson learned occurs during a session. Also use after resolving tricky bugs, making technology choices, or discovering important patterns.
brain-recall
Search Symbiosis Brain for relevant context BEFORE acting. Trigger silently on these signals: (a) before first Edit/Write in an unfamiliar file or scope; (b) before grep across >3 files / a whole subtree; (c) when the user describes a bug or unexpected behavior — recall similar fix history; (d) after any subagent error or contradicted hypothesis — recall if this mistake is already documented; (e) before using an API / library that hasn't appeared in this session yet. Don't ask "should I check?" — just check. Report only when something relevant was found.
cortex-recall
Search and retrieve memories from Cortex persistent memory. Use when the user asks 'what did we decide about X', 'do you remember', 'what was the fix for', 'find that thing about', 'search memories', 'what do we know about', 'have we seen this before', or when you need context about past decisions, patterns, bugs, or architecture choices. Also use proactively when working on something that likely has relevant historical context.