Skip to content
Skills Library
AI & agents · Learning & explanation

keep

/keep

Reflective Memory. Use when working with memory, reflection, context management, or intent tracking. Provides the reflective memory practice — how and when to use keep tools for capturing insights, tracking commitments, and maintaining awareness.

Repository
keep ↗
Licence
MIT
Last repository change
22.10.2026

Assessment and security

91/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content26 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Reflective Memory. Use when working with memory, reflection, context management, or intent tracking. Provides the reflective memory practice — how and when to use keep tools for capturing insights, tracking commitments, and maintaining awareness.

Original author description

Reflective Memory. Use when working with memory, reflection, context management, or intent tracking. Provides the reflective memory practice — how and when to use keep tools for capturing insights, tracking commitments, and maintaining awareness.

How it works

  1. keep: Reflective Memory
Original SKILL.md headings · 24 lines, 205 words
SKILL.md preview
---
name: keep
description: >
  Reflective Memory. Use when working with memory, reflection, context management,
  or intent tracking. Provides the reflective memory practice — how and when to use
  keep tools for capturing insights, tracking commitments, and maintaining awareness.
---

## keep: Reflective Memory

*Your actions have consequences. Context is fleeting. Pay attention to what is being asked.*

**The practice is `keep_prompt(name="reflect")`.** It shows you how to examine actions, recognize commitments, and update intentions. Run it. Follow the steps. Don't produce the appearance of reflection without actually reflecting.

**Three tools:** `keep_flow` (all operations), `keep_help` (documentation), `keep_prompt` (practice prompts).

```
keep_prompt(name="reflect")                                                               # The practice
keep_flow(state="get", params={item_id: "now"}, token_budget=2000)                        # Current intentions
keep_flow(state="query-resolve", params={query: "topic"}, token_budget=2000)              # What do I know?
keep_flow(state="put", params={content: "what's true now", id: "now"})                    # Update intentions
keep_flow(state="put", params={content: "learning", tags: {kind: "learning"}})            # Capture insight
keep_flow(state="put", params={uri: "https://example.com/doc", tags: {topic: "X"}})       # Index a document
keep_flow(state="tag", params={id: "item", tags: {reviewed: "true"}})                     # Tag an item
keep_help(topic="flow-actions")                                                            # Action reference
```

**No MCP?** Every flow has a CLI equivalent: `keep flow get -p item_id=now --token-budget 2000`, `keep flow query-resolve -p query=X --token-budget 2000`, `keep flow put -p content=X`. CLI `--budget` limits execution ticks; `--token-budget` limits rendered response text. Use Bash to run them.

**Protocol:** Reflect using `keep` tools — before, during, and after action. Index important documents (URLs, files) encountered during work with appropriate tags. When writing a plan, incorporate this practice into the plan itself. If the practice is unclear, use `keep_help(topic="index")`.

Versions

The database has no other skills named keep.

Database snapshot: 13.11.2026 · package version 76b35d9a139f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100vector-memory-usage
    This skill should be used when the user asks to "store a memory", "remember this", "search memories", "what did we decide", "find relevant context", "update a memory", "delete a memory", "that memory was useful", discusses "memory quality", "memory best practices", "proactive…
  • 100dspy-gepa-reflective
    Use for GEPA reflective optimization, ReAct agent optimization, feedback metrics, LLM reflection, and execution trajectories.
  • 95claw-memory-management
    Workspace memory management guide: memory layers, writing rules, entry format, and maintenance. Use when writing, updating, or maintaining memory files (memory/YYYY-MM-DD.md and MEMORY.md).
  • 90m3-guide
    How to use m3 memory well — search-first protocol, write vs supersede, chatlog access and its store-topology trap, and verifying capture is live. Use when working with m3 memory tools or unsure which one fits.
  • 100agent-memory-discipline
    Teaches when to recall from long-term memory before acting and when to save durable decisions, corrections and failures afterwards. Use when a memory tool or MCP memory server is connected but the agent is not using it consistently, when the user complains that the assistant…
  • 100memory-consolidate
    Reflective consolidation pass over Serena memory files. Separates durable context (preferences, working style, key relationships, recurring workflows) from dated context (projects, deadlines, one-off tasks), merges duplicate topic files onto the richer path, converts relative…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.