cortex-manage
Manage memories - search, view, update, delete, rename projects
What this skill does
# Memory Management Help the user manage their Cortex memories. ## Capabilities ### Search and View Memories Use `cortex_recall` to find specific memories: - Search by content - Filter by project - View memory details ### Update Memory Use `cortex_update` to edit a memory: - Update content (will re-generate embedding) - Move to different project - Both at once ``` cortex_update(memoryId: 123, content: "corrected content") cortex_update(memoryId: 123, projectId: "new-project") ``` ### Rename Project Use `cortex_rename_project` to move all memories from one project to another: - Useful when project directory is renamed - Bulk operation - moves all memories at once ``` cortex_rename_project(oldProjectId: "old-name", newProjectId: "new-name") ``` ### Delete Specific Memory Use `cortex_delete` to remove a memory fragment: 1. First call WITHOUT `confirm: true` to preview what will be deleted 2. Show the user the preview (content, project, timestamp) 3. Ask for explicit confirmation 4. If confirmed, call with `confirm: true` to delete ### Forget Project Memories Use `cortex_forget_project` to delete all memories for a project: 1. First call WITHOUT `confirm: true` to get count 2. Show the user how many memories will be deleted 3. Ask for explicit confirmation 4. If confirmed, call with `confirm: true` to proceed ## Important Safety Rules **ALWAYS follow these rules for destructive actions:** 1. **Preview First**: Always call the delete/forget tool without confirm first 2. **Show Impact**: Display exactly what will be affected 3. **Explicit Confirmation**: Ask user "Are you sure you want to delete X?" 4. **Never Assume**: Don't delete without explicit user approval 5. **Be Clear**: State what will be permanently lost ## Example Flows ### Updating a Memory User: "Fix the typo in memory 42" 1. First recall to see the memory: ``` cortex_recall(query: "...") ``` 2. Update with corrected content: ``` cortex_update(memoryId: 42, content: "corrected content here") ``` ### Moving Memory to Different Project User: "Move memory 42 to project 'cortex'" ``` cortex_update(memoryId: 42, projectId: "cortex") ``` ### Renaming a Project User: "I renamed my project folder from 'old-name' to 'new-name'" ``` cortex_rename_project(oldProjectId: "old-name", newProjectId: "new-name") ``` ### Deleting a Specific Memory User: "Delete the memory about the auth bug fix" 1. Search for memories about auth bug: ``` cortex_recall(query: "auth bug fix") ``` 2. Show results and ask which one to delete 3. Preview the deletion: ``` cortex_delete(memoryId: 123) ``` 4. Show preview to user: "This will delete: 'Fixed auth bug by...' from project X" 5. Ask: "Are you sure you want to delete this memory?" 6. If yes: ``` cortex_delete(memoryId: 123, confirm: true) ``` ### Clearing a Project's Memories User: "Clear all memories for the old-project" 1. Preview: ``` cortex_forget_project(projectId: "old-project") ``` 2. Show: "This will delete 45 memories from old-project" 3. Ask: "This action cannot be undone. Are you sure?" 4. If yes: ``` cortex_forget_project(projectId: "old-project", confirm: true) ``` ## What NOT to Do - Never delete without showing what will be deleted - Never assume the user wants to delete - Never delete multiple memories without listing them first - Never forget a project without explicit confirmation
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.