Name: memberstack
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

memberstack

Memberstack integration. Manage Members, Plans, Workspaces. Use when the user wants to interact with Memberstack data.

Quality

70%

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

Quality

Content

68%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 content is highly actionable with executable commands and a strong connection workflow, but it loses points for an unnecessary introductory explanation and, critically, lacks validation guidance around destructive operations like member deletion. Organization is solid but monolithic.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive actions (e.g. 'Before running delete-member, confirm the member ID with the user and consider listing the member first to verify').

Trim or remove the introductory paragraph explaining what Memberstack is and the empty Memberstack Overview bullet list, which add tokens without operational value.

Consider moving the full proxy flag table and Popular actions reference into a separate reference file, keeping SKILL.md as a concise overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient executable CLI guidance, but the introductory paragraph explaining what Memberstack is (membership platform, logins, gated content, no-code solution) and the near-empty Memberstack Overview bullets are unnecessary background Claude does not need, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Provides fully executable, copy-paste-ready membrane CLI commands with flags across install, auth, connection, action search/run, and proxy, plus a concrete Popular actions table — specific examples cover the common cases.	5 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state checkpoints and a poll-after-action feedback loop, but destructive actions (e.g. 'Delete Member') are presented in a table with a generic run command and no validation checkpoint before execution, so the destructive-operation cap holds at 3.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references, but it is a monolithic ~150-line single file with inlined reference-style content (the proxy flag table and action list) that could be split; good structure with minor organization gaps rather than the content-splitting required for a 5.	4 / 5
	Total	15 / 20 Passed

Description

71%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 identifies a specific platform and states both capability and trigger, but the trigger phrasing is somewhat generic and lacks synonym coverage. Strong on distinctiveness, slightly weaker on trigger-term breadth and trigger specificity.

Suggestions

Expand the 'Use when' clause with concrete trigger phrases users would say (e.g. 'Use when the user wants to add or remove member plans, manage member logins, or work with Memberstack subscriptions').

Replace the single generic verb 'Manage' with multiple distinct actions (e.g. 'Create, update, and delete Members; add or remove Plans; manage Workspaces') to lift specificity.

Add natural synonyms such as 'subscriptions' or 'gated content' so the description surfaces for a wider range of user phrasings.

Dimension	Reasoning	Score
Specificity	Names the Memberstack domain and three concrete entities ('Manage Members, Plans, Workspaces'), which is several specific actions with minor coverage gaps rather than the multiple distinct verbs required for a 5.	4 / 5
Completeness	Explicitly answers both what ('Manage Members, Plans, Workspaces') and when ('Use when the user wants to interact with Memberstack data'), but the 'when' trigger is a single broad phrase rather than concrete enumerated triggers, so it is not a 5.	4 / 5
Trigger Term Quality	Includes the natural domain terms ('Members, Plans, Workspaces', 'interact with Memberstack data') but offers no synonyms or common variations (e.g. subscriptions, logins, gated content), leaving keyword coverage relevant but incomplete.	3 / 5
Distinctiveness Conflict Risk	Targets a specific named platform with triggers tied to Memberstack's own entities, giving it a clear niche and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/memberstack/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.