memory
Store and recall long-term memory. Use when persisting facts learned during conversations or recalling stored knowledge about projects and preferences.
What this skill does
# Memory Skill
You have access to a long-term memory system. Use it to remember important facts across sessions.
## When to Store Facts
After completing a task or learning something important about the project, store durable facts using `memory.store_extraction`. Look for:
- **Tech stack**: databases, frameworks, languages, platforms
- **Conventions**: coding standards, naming patterns, preferences
- **Decisions**: architectural choices, design decisions
- **Preferences**: user preferences that should persist
## How to Store Facts
Call the `memory.store_extraction` MCP tool with:
```json
{
"entities": [
{"type": "database", "name": "postgresql"}
],
"facts": [
{
"subject": "repo",
"predicate": "uses_database",
"object": "postgresql",
"quote": "We use PostgreSQL for persistence",
"strength": "stated",
"scope_hint": "project"
}
]
}
```
### Predicates
| Predicate | Use for | Example |
|-----------|---------|---------|
| `uses_database` | Database choice | postgresql, redis |
| `uses_framework` | Framework | rails, react, nextjs |
| `deployment_platform` | Where deployed | vercel, aws, heroku |
| `convention` | Coding standard | "4-space indentation" |
| `decision` | Architectural choice | "Use microservices" |
| `auth_method` | Auth approach | "JWT tokens" |
### Scope
- `project`: Only this project (default)
- `global`: All projects (user preferences)
Use `global` when user says "always", "in all projects", or "my preference".
## How to Recall Facts
Use `memory.recall` to search for relevant facts:
```json
{"query": "database", "limit": 10}
```
## Available Tools
- `memory.recall` - Search facts by query
- `memory.store_extraction` - Store new facts
- `memory.explain` - Get fact details with provenance
- `memory.promote` - Promote project fact to global
- `memory.status` - Check database health
- `memory.changes` - Recent updates
- `memory.conflicts` - Open contradictions
## Best Practices
1. **Be selective**: Only store durable facts that will be useful later
2. **Include quotes**: Add the source text for provenance
3. **Set scope correctly**: Project-specific vs global preferences
4. **Check before storing**: Use `memory.recall` to avoid duplicates
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.