CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memcode

Use the enabled Memcode MCP connection to explicitly save approved facts and recall relevant memories across DeepChat conversations. Never save a transcript or retrieve memory automatically.

62

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/memcode/skills/memcode/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is an excellent example of a lean, instruction-only MCP skill: every line is a specific directive, the save and recall workflows include explicit validation checkpoints and error-recovery paths, and the short single-file structure needs no progressive disclosure. The only minor gap is the absence of example tool invocations or parameter shapes.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with no padding and no explanation of concepts Claude already knows (e.g., no "what is MCP" preamble); every sentence is a Memcode/DeepChat-specific directive such as "Do not pass a caller-chosen user ID. The server identifies the user from the OAuth credential." This matches the anchor for lean, efficient content where every token earns its place, not the 4 anchor which requires instances of over-explanation to trim.

5 / 5

Actionability

Concrete, executable guidance throughout: named tools ("save_memory", "get_memory_ingest_status", "search_memories", "retrieve_answer"), a specific server URL, a menu path ("Plugins > Memcode"), and explicit conditions ("use get_memory_ingest_status before claiming it was stored"). It falls at anchor 4 rather than 5 because no example invocations or parameter shapes are shown for the MCP tools — a minor gap for an otherwise actionable instruction-only skill.

4 / 5

Workflow Clarity

The save flow has an explicit validation checkpoint ("use get_memory_ingest_status before claiming it was stored") with a feedback loop ("Report a partial or failed ingest as such"), the recall flow handles the empty case ("Say when no relevant memory was found"), and a failure-recovery path covers a disabled or failing connection. This matches the anchor for a clear sequence with explicit validation steps and error-recovery loops; no destructive or batch operations apply, so no cap is triggered.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no need for external reference files (none exist in the bundle), and is organized into clear sections (connection setup, Save, Recall, failure handling). Per the simple-skill guideline, this scores 5 with well-organized sections alone.

5 / 5

Total

19

/

20

Passed

Description

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

The description clearly states what the skill does within its niche, but omits any explicit "Use when..." trigger guidance and lacks natural trigger synonyms (especially "remember"). Trigger-term quality and completeness are the main weaknesses, keeping it at the anchor-3 level on three of four dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to remember, save, or recall a fact, or mentions their Memcode memories during a DeepChat conversation" — this lifts completeness from 3 toward 5.

Include natural user phrasings as trigger synonyms: "remember this", "recall what I told you", "my saved memories", alongside the current "save facts" / "recall memories" wording.

Enumerate the concrete capabilities more fully (e.g. saving approved facts, searching memories, retrieving sourced answers with citations) to raise specificity from naming two actions to listing several.

DimensionReasoningScore

Specificity

The description names the domain ("Memcode MCP connection", "DeepChat conversations") and exactly two concrete actions ("explicitly save approved facts" and "recall relevant memories"), which matches the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage. It is not a 4 because it does not list several specific actions — the save/recall pair exhausts the stated capabilities.

3 / 5

Completeness

The "what" is clear ("explicitly save approved facts and recall relevant memories across DeepChat conversations"), but there is no "Use when..." clause or equivalent explicit trigger guidance — "explicitly" and "Never... automatically" are constraints, not triggers. Per the guideline that a missing 'Use when' clause caps completeness at 3, this cannot score higher.

3 / 5

Trigger Term Quality

Relevant keywords are present ("save", "recall", "memories", "facts", "Memcode", "DeepChat"), but common natural user phrasings such as "remember this", "my notes", or "what did I tell you" are missing. This fits the anchor for some relevant keywords missing common variations or synonyms, rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

"Memcode MCP connection" and "DeepChat conversations" anchor a clear, named niche, giving mostly distinct triggers. It is not a 5 because the underlying capability phrasing ("save... facts and recall... memories") has minor overlap risk with other memory or note-taking skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

ThinkInAIXYZ/deepchat

Path

plugins/memcode/skills/memcode/SKILL.md

Reviewed

Table of Contents

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.