Name: membervault
Rating: 59.2 (1 reviews)
Author: membranedev

membervault

Membervault integration. Manage Courses, Bundles, Members, Tags, Products, Offers and more. Use when the user wants to interact with Membervault data.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/membervault/SKILL.md

Quality

Content

67%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 a well-structured, highly actionable CLI guide with a genuine validation/feedback loop around connection state. Tightening the introductory prose and fixing the inconsistent step numbering would lift it further.

Suggestions

Trim the introductory platform description to one line and drop marketing phrasing ('so you can focus on the integration logic rather than auth plumbing').

Fix the step numbering so the referenced 'Step 2' maps to a labeled section (e.g., number Search and Run as Steps 2 and 3), and consolidate the '1b' sub-step.

Either populate 'Popular actions' with a few named high-value actions or rename the section to 'Discover actions' so it matches what it actually delivers.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference, but the opening platform description ('used by entrepreneurs, coaches, and educators...', 'Think of it as a simplified alternative to Teachable or Kajabi') and a few marketing-style sentences ('so you can focus on the integration logic rather than auth plumbing') are explanation that could be trimmed, fitting the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Copy-paste-ready commands cover install, auth, connect, search, run, and proxy with real flags and a flag table, but the 'Popular actions' section delivers only a discovery command instead of named actions and 'Use action names and parameters as needed' is vague, leaving minor gaps below the 5 anchor.	4 / 5
Workflow Clarity	The connection flow has an explicit sequence with validation checkpoints (poll until not BUILDING, handle CLIENT_ACTION_REQUIRED, inspect error on CONFIGURATION_ERROR/SETUP_FAILED), but step numbering is inconsistent ('1b', a referenced 'Step 2' with no matching header), keeping it just below the 5 anchor.	4 / 5
Progressive Disclosure	No bundle files are provided, so all content lives in one file, but it is well-organized into clear logical sections with no nested references; minor organization gaps (thin 'Popular actions', terse hierarchy overview) keep it below the ideal 5 anchor.	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 cleanly states both capability and trigger for a distinct niche platform, but relies on one generic verb and a narrow set of trigger keywords. Strengthening the verb variety and 'when' specificity would push it toward the top anchor.

Suggestions

Replace the single generic verb 'Manage' with distinct concrete actions per entity (e.g., 'Create and enroll members in courses, bundle products, tag members').

Expand the 'when' clause with concrete trigger phrases users would actually say (e.g., 'Use when the user mentions MemberVault courses, memberships, enrollments, or member tags').

Drop the vague 'and more' or replace it with the remaining named entities so coverage reads as comprehensive.

Dimension	Reasoning	Score
Specificity	Lists several specific entities to manage (Courses, Bundles, Members, Tags, Products, Offers) but applies a single generic verb 'Manage' and leaves gaps with 'and more', fitting the 'several specific actions, minor gaps' anchor rather than the comprehensive multi-verb anchor at 5.	4 / 5
Completeness	Both 'what' (manage Courses, Bundles, Members, etc.) and 'when' ('Use when the user wants to interact with Membervault data') are present, but the 'when' clause is generic rather than packed with concrete trigger phrases, fitting the 4 anchor over the 5 anchor.	4 / 5
Trigger Term Quality	The core keyword 'Membervault' appears but trigger coverage is essentially one proper noun repeated ('interact with Membervault data'), missing natural variations or synonyms, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	It names a specific niche platform (Membervault) with a platform-specific trigger, giving a clear niche with minimal overlap risk against 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/membervault/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.