1---
2name: remember-as-skill
3description: Capture a successful solution, repeated workflow, or hard-won preference as a reusable skill or durable agent memory asset. Use when the user asks to remember something, wants a result to happen more often, wants to package a workflow for reuse across devices or accounts, or wants a portable bundle that could later be shared, gifted, or sold. Skip one-off details that are not worth reusing.
4---
5 
6# Remember as Skill
7 
8Use this skill when the right next step is not "nice, that worked" but "save this so the agent can do it again."
9 
10Translate praise into procedure. If the result was unusually strong, distill what made it work and store it in a reusable form before the context disappears.
11 
12## Workflow
13 
141. Identify the reusable asset:
15   - a workflow
16   - a decision rubric
17   - a prompt pattern
18   - a preference or guardrail
19   - a checklist
202. Strip away one-off noise and keep the part that should survive:
21   - what triggered the approach
22   - what constraints mattered
23   - what steps or rules produced the result
24   - what outcome should repeat next time
253. Choose the right artifact:
26   - short memory note for a durable preference, rule, or trigger
27   - skill update or new skill for a multi-step reusable workflow
28   - marketplace-ready bundle when the workflow is portable and could be shared
294. Write activation guidance that helps the agent decide when to load it.
305. Write a boundary for when not to use it so the skill does not over-trigger.
316. Replace secrets, private hosts, account ids, and machine-specific paths with parameters or placeholders.
327. Save the artifact in the real system of record before ending the task. If the user explicitly wants something remembered, do not leave it only in chat.
33 
34## Guardrails
35 
36- Do not turn every decent answer into memory. Save only patterns that are likely to matter again.
37- Do not preserve accidental hacks, temporary incidents, or brittle local quirks as general guidance unless the user explicitly wants that.
38- Do not embed secrets or private identifiers into a reusable bundle.
39- Prefer a small durable instruction set over a long retrospective.
40 
41## Output Contract
42 
43When you create or update the artifact, include:
44 
45- the reusable pattern in one sentence
46- the trigger for when it should be used
47- the core steps or rules
48- the explicit non-trigger boundary
49- portability notes or publication risks if relevant
50 
51## Marketplace Angle
52 
53If the workflow is portable, package it so it can move across devices, accounts, and runtimes. A good memory can stay private; a good skill can also be installed, shared, gifted, or sold.
54