Pins or unpins a memory to protect it from pruning during dream consolidation. Use when a memory is critical and must never be removed, such as architecture decisions, security constraints, or immutable team conventions.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable skill body with executable code across all cases and a clear sequenced workflow. The main gap is a missing post-update verification step (re-read to confirm the [PINNED] marker was applied) before reporting success.

Suggestions

Add a verify step after update_memory: re-call get_memory and confirm the text now starts with "[PINNED]" before reporting "Pinned:" — this closes the validation feedback loop.

Drop or tighten the opening line "Pin a memory to mark it as high-priority and protect from pruning" since it duplicates the frontmatter description and adds no new signal.

Make the search→pin path explicit about what happens if search_memories returns zero results (e.g. tell the user nothing matched and stop) to round out the workflow.

Dimension	Reasoning	Score
Conciseness	Efficient and lean with executable code earning its place; the only padding is the opening restatement "Pin a memory to mark it as high-priority and protect from pruning" which repeats the description, plus the justified tool-limitation note which is genuinely non-obvious.	4 / 5
Actionability	Fully executable, copy-paste-ready code for every common case — pin-by-ID, pin-by-search, pin-new-memory, and unpin — with concrete tool calls, filters, and the get_event_status retrieval pattern; specific examples cover the common cases.	5 / 5
Workflow Clarity	Steps are clearly sequenced (Step 1–4 plus Unpin) with most checkpoints present — user selection, reading current content, and a confirmation block — but no explicit re-read/verify feedback loop after update_memory to confirm the marker landed.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Execution, numbered steps, Unpin) with content appropriately inline for a self-contained single-purpose skill; slightly over the ~50-line simple-skill threshold and no external references are needed.	4 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-formed description: third-person voice, explicit what-and-when structure, and concrete trigger examples. Minor room to broaden trigger synonyms and sharpen the distinction from related memory-management skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — "Pins or unpins a memory to protect it from pruning during dream consolidation" — pinning, unpinning, and protecting-from-pruning are specific operations, with minor gaps in coverage.	4 / 5
Completeness	Clearly and explicitly answers both what ("Pins or unpins a memory to protect it from pruning during dream consolidation") and when ("Use when a memory is critical and must never be removed, such as...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage with natural phrases a user would say — "a memory is critical", "must never be removed", "architecture decisions", "security constraints", "immutable team conventions" — though a few common synonyms (e.g. "keep this memory forever", "don't forget") are missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (memory pinning during dream consolidation) with mostly distinct triggers, but minor overlap risk with sibling memory skills (delete/prune memories) within the same Mem0 family.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: mem0ai/mem0
Path: integrations/mem0-plugin/skills/pin/SKILL.md
Commit: 39bc023

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.