Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davepoon/capture
Save a memory to Origin in flow. Active capture verb — use proactively when the user states a preference, makes a decision, corrects you, or shares a durable fact. Invoked as `/capture <content>`.
Passed 4 of 9 test cases with the skill, and 2 of 9 without it.
and 3 more in the full report
6 fixed3 passed either way12 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I typed 'sounds good' in our chat. Save this single-word acknowledgment into my memory.
| Checked | Without skill | With skill |
|---|---|---|
| Refrains from calling the capture tool | Passed | Passed |
| Explains that single-word acknowledgments should not be saved | Missed | Passed |
The instructions your model reads when the skill loads.
Capture a single memory in the moment. Active verb: agent captures the moment of insight, like a photograph.
Call the origin MCP server's capture tool with the user's content as a
complete, self-contained statement. Attach topic from cwd or the
conversation — don't make the user type it.
capture(content="<args, written as a full sentence with WHY>",
memory_type="<picked from the 6 types>",
entity="<primary entity name, if any>",
space=<inferred>)
memory_type — agent picks one of 6The daemon classifies when a local model or API key is configured. In local memory mode it does not, so the agent picks the type from the content itself. Use this mapping:
| Type | Use for |
|---|---|
identity | Durable facts about the user (role, company, language preference) |
preference | "I prefer X because Y" — a habit, a correction, a stylistic choice |
decision | "Going with A over B because C" — a specific choice with rationale |
lesson | Root cause found, workaround discovered, technical insight earned |
gotcha | Sharp edge, surprising behavior, a thing to watch out for |
fact | Durable info about people, projects, tools — anchor to entity when possible |
If two types fit, pick the one closest to why the memory matters. A
decision also implies a preference, but decision is more specific.
entity — extract the anchorPick the single most important named thing in the content: a person, project, tool, place. Use the exact name. Example: "Alice prefers TDD
test cases passed, vs 2 / 9 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.