Skip to content
Back to skills

Yesmem Remember

ASecurity

Use after ANY decision, correction, gotcha, or discovery worth preserving. Also on task completion — resolve open tasks via resolve_by_text() after commits, "fertig", or confirmed fixes. Trigger on "remember this"/"merk dir das", confirmed approaches, debugging surprises, and relate_learnings() for connecting insights.

  • 42 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
ai-agentsrustgodebugging

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add carsteneu/yesmem --skill yesmem-remember --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Yesmem Remember?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Yesmem Remember
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/carsteneu-yesmem-remember/badge)](https://www.skillsdirectory.com/skills/carsteneu-yesmem-remember)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: yesmem-remember
description: Use after ANY decision, correction, gotcha, or discovery worth preserving. Also on task completion — resolve open tasks via resolve_by_text() after commits, "fertig", or confirmed fixes. Trigger on "remember this"/"merk dir das", confirmed approaches, debugging surprises, and relate_learnings() for connecting insights.
---

# Saving Knowledge

Store learnings with structured metadata for better retrieval.

## Workflow
1. Identify what to save (decision, gotcha, pattern, preference, teaching)
2. Call `remember()` with rich metadata
3. For completed tasks: `resolve_by_text(text)` or `resolve(learning_id, reason)`
4. For connected insights: `relate_learnings(id_a, id_b, relation_type)`

## remember() Parameters

| Parameter | Purpose | Example |
|-----------|---------|---------|
| `text` | What to remember | "CGO is disabled in yesmem Makefile" |
| `category` | gotcha, decision, pattern, preference, explicit_teaching, strategic | "decision" |
| `entities` | Files, systems, people | ["Makefile", "CGO"] |
| `actions` | Commands, operations | ["go build", "make deploy"] |
| `trigger` | When to surface this | "When discussing CGO or cross-compilation" |
| `context` | Why this matters | "Breaks tree-sitter integration" |
| `anticipated_queries` | 3-5 search phrases | ["CGO disabled", "cross compile yesmem"] |
| `source` | user_stated, agreed_upon, claude_suggested | "agreed_upon" |
| `project` | Project scope | "yesmem" |
| `supersedes` | ID of learning this replaces | 12345 |

## relate_learnings()

Connect two learnings with semantic edges:
- `supports` — one learning confirms another
- `contradicts` — learnings conflict
- `depends_on` — one requires the other
- `relates_to` — general connection

## Tips
- `anticipated_queries`: vary between short keywords and full questions
- `source` trust hierarchy: user_stated > agreed_upon > claude_suggested
- Use `supersedes` when updating outdated knowledge — don't create duplicates
- `resolve_by_text` finds matching open tasks by text search

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.