Use when the user wants to persistently remember something across sessions (e.g., "always use bun", "never auto-commit", "my name is Alex"). Also use when you detect a clear user preference or constraint worth persisting.
Scanned 5/27/2026
Install via CLI
openskills install hatawong/claude-recap---
name: remember
description: Use when the user wants to persistently remember something across sessions (e.g., "always use bun", "never auto-commit", "my name is Alex"). Also use when you detect a clear user preference or constraint worth persisting.
---
# remember
## Overview
Saves a user preference, constraint, or fact to REMEMBER.md so it persists across sessions. The user chooses scope (global or project).
## When to Use
- User explicitly says "remember...", "always...", "never...", "don't forget..."
- User states a clear preference or constraint worth persisting (e.g., "I use bun not npm")
- User provides identity or context info they'd want every session to know
## Instructions
1. Distill what the user wants to remember into **one concise line** (imperative form, no filler).
- Good: "Use bun instead of npm for all package management"
- Bad: "The user mentioned they prefer bun over npm and would like us to always use it"
2. Ask the user which scope using AskUserQuestion:
```
Which scope should this apply to?
- Global: applies to all projects
- Project: applies only to this project
```
3. Get the **plugin scripts path** from the SessionStart injection in your context:
`Plugin scripts path: /path/to/scripts`
4. Run the remember script:
```bash
bash "<plugin_scripts_path>/remember.sh" "<scope>" "<content>"
```
Where:
- `plugin_scripts_path`: the path from SessionStart injection
- `scope`: `global` or `project`
- `content`: the distilled one-liner (quote it properly for shell)
## Rules
- One entry per invocation — don't batch multiple items
- Distill to a clear imperative statement, not a description of what happened
- If the user's intent is ambiguous, ask for clarification before writing
- Do NOT remember session-specific or temporary information (e.g., "I'm debugging auth today")
## Examples
| User says | Distilled entry |
|---|---|
| "Remember I always use bun" | `Use bun instead of npm for package management` |
| "Never auto-commit without asking" | `Never auto-commit; always ask before committing` |
| "My name is Alex" | `User's name is Alex` |
| "For this project, always run tests with --verbose" | `Run tests with --verbose flag` (project scope) |
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...