Name: mem
Rating: 61.6 (1 reviews)
Author: membranedev

mem

Mem integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Mem data.

Quality

72%

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 ./skills/mem/SKILL.md

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.

The body is highly actionable with executable commands and a well-structured connection state machine including feedback loops, and it is mostly token-efficient. Its main weaknesses are a dangling 'Step 2' reference and a small amount of introductory padding.

Suggestions

Fix the dangling cross-reference: label the sections 'Step 1' / 'Step 2' or remove the 'skip to Step 2' phrasing so the sequence is coherent.

Trim the opening 'Mem is a self-organizing workspace...' paragraph and the filler 'Use action names and parameters as needed.' line.

Consider moving the proxy flags table and action-discovery details into a references file to keep SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command snippets, tables, and a state-machine description, with only minor over-explanation such as the opening 'Mem is a self-organizing workspace...' paragraph and the filler line 'Use action names and parameters as needed.'	4 / 5
Actionability	It provides copy-paste-ready, executable commands throughout (install, login, connection ensure/get with --wait, action list/run with --input, request proxy) plus a full flags table, covering the common cases concretely.	5 / 5
Workflow Clarity	The connection flow is a clear state machine with explicit polling and a re-poll feedback loop after CLIENT_ACTION_REQUIRED, plus error-state handling; the main gap is the dangling 'skip to Step 2' reference where no Step 1/Step 2 is labeled.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with one external reference (Notion docs link) and no nested references; with no bundle files present everything is appropriately inline, though some action-discovery detail could live in a reference file.	4 / 5
	Total	17 / 20 Passed

Description

62%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 is third-person, answers both what and when, and is anchored to a distinct named product, but it leans on the generic verb 'Manage' plus 'and more' rather than enumerating concrete actions. It sits solidly above average but short of exemplary.

Suggestions

Replace the generic 'Manage ... and more' with specific verbs (e.g., 'Create, edit, list, and delete Persons, Organizations, Deals, Leads, Projects, and Activities').

Broaden trigger coverage with natural synonyms users might say (e.g., 'Use when the user wants to manage Mem notes, tasks, collections, or tags').

Drop the vague 'and more' filler to tighten the what-clause.

Dimension	Reasoning	Score
Specificity	Names the concrete domain entities ('Persons, Organizations, Deals, Leads, Projects, Activities') but relies on a single generic verb ('Manage') and pads with 'and more', so the action coverage is minimal rather than comprehensive.	3 / 5
Completeness	It answers both 'what' ('Manage Persons, Organizations...') and 'when' ('Use when the user wants to interact with Mem data') explicitly, but the 'what' is weakened by the vague 'and more', keeping it just below the top anchor.	4 / 5
Trigger Term Quality	The trigger phrase 'Use when the user wants to interact with Mem data' is natural and on-brand, but offers no synonyms or variations beyond the product name, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Binding to the named product 'Mem' gives a clear niche with low conflict risk, though the generic CRM-style entity list (Persons, Deals, Leads) creates minor overlap with contact/CRM skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/mem/SKILL.md
Commit: f484c82

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