AugmentClaude

Cortex Automate

Set up automated triggers and rules to manage memory and reminders based on conditions.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up β€” so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/cortex-automate-cdeust/ β€” the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Works for every skill.

    What this command does
    1. Makes a new, empty temporary folder.
    2. Downloads the skill's folder, skills/cortex-automate, from github.com/cdeust/Cortex (branch main), the GitHub repository it's listed from. You get the version that is there now, not a copy we keep.
    3. Copies that folder to ~/.claude/skills/cortex-automate-cdeust/.
    4. Deletes the temporary folder.

    Installing runs none of the skill's files; it only downloads and copies them. When you later use the skill, Claude follows its SKILL.md and may run scripts that come with it. Read them first.

    How we check skills, and what we don't Β· Report this skill

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates β€” they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description β€” no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the β€œWhat this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Set 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.

What this skill does

Automate β€” Triggers, Rules, and Sync

Keywords

trigger, rule, automate, remind me when, auto-remember, sync instructions, push to CLAUDE.md, prospective memory, keyword trigger, file trigger, domain trigger, time trigger, filter rule, boost rule

Overview

Set up proactive automation in Cortex β€” triggers that fire when conditions are met (like opening a specific file or entering a domain), rules that filter or boost memories during recall, and syncing top insights back into CLAUDE.md for persistent project instructions.

Use this skill when: You want Cortex to proactively surface information based on context, filter out noise during recall, or keep CLAUDE.md updated with memory-derived insights.

Workflow

Triggers β€” Proactive Memory Recall

Create triggers that fire automatically when conditions match:

Keyword trigger β€” fires when a query/context contains specific words:

cortex:create_trigger({
  "type": "keyword",
  "pattern": "authentication",
  "memory_id": <id>,
  "message": "Remember: we decided to use JWT with refresh tokens, not sessions"
})

File trigger β€” fires when a specific file is being worked on:

cortex:create_trigger({
  "type": "file",
  "pattern": "pg_store.py",
  "memory_id": <id>,
  "message": "This file has a known issue with connection pooling under load"
})

Domain trigger β€” fires when entering a specific project domain:

cortex:create_trigger({
  "type": "domain",
  "pattern": "cortex",
  "memory_id": <id>,
  "message": "Priority: finish the refactoring plan before adding new features"
})

Time trigger β€” fires after a time condition:

cortex:create_trigger({
  "type": "time",
  "pattern": "7d",
  "memory_id": <id>,
  "message": "It's been a week β€” run consolidation"
})

Triggers fire up to 5 times by default, then deactivate. They appear in the query_methodology response at session start.

Rules β€” Filter and Boost During Recall

Add rules that modify recall behavior:

Soft rule (boost/penalize score):

cortex:add_rule({
  "type": "soft",
  "scope": "domain:cortex",
  "condition": "tag:architecture",
  "weight": 1.5,
  "description": "Boost architecture memories in Cortex domain"
})

Hard rule (include/exclude):

cortex:add_rule({
  "type": "hard",
  "scope": "global",
  "condition": "tag:deprecated",
  "action": "exclude",
  "description": "Never surface deprecated memories"
})

Tag rule (auto-tag on store):

cortex:add_rule({
  "type": "tag",
  "scope": "domain:cortex",
  "condition": "content_match:refactor",
  "tag": "refactoring",
  "description": "Auto-tag refactoring memories"
})

List active rules:

cortex:get_rules({
  "scope": "domain:cortex"
})

Sync to CLAUDE.md

Push top memory insights into project CLAUDE.md for persistent context:

cortex:sync_instructions({
  "directory": "<project root>",
  "max_insights": 10
})

This extracts the most important, high-confidence memories and formats them as project instructions in CLAUDE.md. Useful for keeping the project-level instructions file updated with lessons and patterns discovered across sessions.

Tips

  • Triggers are personal reminders: Think of them as "note to future self" tied to a context
  • Rules shape retrieval: Soft rules are preferred over hard rules β€” they influence ranking without hiding potentially useful memories
  • Sync periodically: Run sync_instructions after significant sessions to keep CLAUDE.md current
  • Don't over-trigger: Too many triggers create noise. Use them for genuinely important context-dependent reminders

Related skills