mem0-tour

Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./integrations/mem0-plugin/.opencode-plugin/opencode-skills/mem0-tour/SKILL.md

Quality

Content

76%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.

Highly actionable content with concrete API calls and display templates organized into clear sections. Its notable gap is workflow clarity: the skill claims to fetch ALL memories but issues a single paginated call with no pagination loop or error-recovery validation, which is a real correctness risk for a batch read operation.

Suggestions

Add a pagination/validation loop after Step 1 (loop get_memories with the returned cursor/page_token until exhausted) so the skill actually retrieves ALL memories as claimed, and cap workflow_clarity above 3.

Add an explicit error-handling feedback loop (if a get_memories or search_memories call fails, surface the error and retry/adjust filters) to satisfy the validation requirement for batch operations.

Trim the multi-line mock output samples in Step 4 to one or two representative lines each to tighten conciseness toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is efficient and operational, giving API call parameters and display templates without explaining concepts Claude already knows; the main over-explanation is the long mock output blocks (e.g. the multi-line 'tooling_setup (119)' and 'bug_fixes (78)' samples) that could be trimmed, which keeps it just below the 'every token earns its place' of a 5.	4 / 5
Actionability	Fully executable guidance: exact get_memories and search_memories calls with concrete filter objects, page_size, top_k, and rerank values, plus a category-mapping table and copy-ready display templates covering all three modes (cross-project, peek, full tour).	5 / 5
Workflow Clarity	Steps are clearly numbered and sequenced (Steps 1-6, plus peek/cross-project modes) and an empty state is handled, but this is a batch operation that claims 'Fetch ALL memories' via a single page_size=100 call with no pagination/validation loop, and there is no error-handling feedback loop for failed API calls — the missing validation for a batch operation caps this at 3.	3 / 5
Progressive Disclosure	The skill is a self-contained operational doc with no bundle files and is organized into clear, well-signaled sections (Cross-project mode, Peek mode, Execution, Output formatting); the category table and display templates are appropriately inline for execution-time use, with only minor organization gaps, though at over 50 lines it does not fully meet the simple-skill exception for a 5.	4 / 5
	Total	16 / 20 Passed

Description

78%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 well-constructed description that clearly states both what the skill does and when to use it with natural trigger phrases. Its main weakness is specificity: it describes one composite browsing action rather than enumerating several concrete capabilities.

Suggestions

Expand the 'what' clause to list several distinct concrete actions (e.g. 'Browses, searches, and groups stored memories by category, displaying full content') to lift specificity toward a 5.

Add a synonym-style trigger term (e.g. 'memories', 'knowledge base') to broaden natural keyword coverage toward the 5 anchor.

Tighten the 'when' clause to emphasize memory-review-specific triggers over the more generic 'onboarding to a project' phrasing to reduce overlap risk with sibling skills.

Dimension	Reasoning	Score
Specificity	Names the domain and one composite action — 'Browses all stored memories grouped by category with full content display' — but does not enumerate multiple distinct concrete actions (e.g. search, filter, export), so it sits at '1-2 concrete actions, not comprehensive' rather than the 'several specific actions' of a 4.	3 / 5
Completeness	Explicitly answers both: what it does ('Browses all stored memories grouped by category with full content display') and when to use it via a concrete 'Use when...' clause with multiple trigger phrases, matching the anchor for clearly and explicitly answering both.	5 / 5
Trigger Term Quality	Provides several natural trigger phrases users would actually say — 'reviewing all project memories', 'exploring stored knowledge', 'onboarding to a project', 'overview of captured decisions, conventions, and learnings' — giving good coverage, though it lacks synonym/extension breadth that would push it to a 5.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (mem0 memory browsing) with distinct triggers, but 'exploring stored knowledge' and 'onboarding to a project' could overlap with sibling mem0 skills such as a search or remember skill, leaving minor overlap risk with closely related skills rather than minimal conflict.	4 / 5
	Total	16 / 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/.opencode-plugin/opencode-skills/mem0-tour/SKILL.md
Commit: dae67f7

Reviewed: 4 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.