Name: memberspotio
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

memberspotio

Memberspot.io integration. Manage Organizations. Use when the user wants to interact with Memberspot.io data.

Quality

74%

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/memberspotio/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 copy-paste CLI commands and a clear, checkpointed connection workflow. Its main weaknesses are minor verbosity in a few explanatory passages and the absence of any progressive-disclosure references to split out the longer reference material.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven documentation with minor padding (e.g., "so you can focus on the integration logic rather than auth plumbing" and the introductory paragraph on what Memberspot is). It fits anchor 4 (efficient with minor over-explanation) rather than 5, which requires every token to earn its place.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a complete proxy flag table, fully covering the common cases. This matches anchor 5 for fully executable, specific examples.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop. It fits anchor 4 (clear sequence, most checkpoints present) rather than 5 because post-action result validation is left implicit.	4 / 5
Progressive Disclosure	Content is organized into well-signaled sections (Overview, Install, Authentication, Connecting, Searching, Proxy, Best practices) with no bundle files to navigate. It fits anchor 4 (good structure, well-placed content) rather than 5 because all material lives inline in one file with no one-level-deep references for the longer reference material.	4 / 5
	Total	17 / 20 Passed

Description

66%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 distinct and complete with an explicit use-when clause, but it is thin on concrete capabilities (only "Manage Organizations") and offers just one trigger keyword. Expanding the action list and trigger synonyms would raise specificity and trigger-term quality.

Suggestions

List more concrete actions beyond "Manage Organizations" (e.g., manage members, spaces, events, courses, payments) to improve specificity.

Add natural trigger synonyms users might say, such as "Memberspot", "membership site", or "gated community", to broaden keyword coverage.

Make the "when" clause more concrete by tying it to specific intents (e.g., "Use when the user wants to manage members, courses, or gated content in Memberspot.io").

Dimension	Reasoning	Score
Specificity	"Manage Organizations" names the domain (Memberspot.io integration) with one concrete action, matching the anchor for 1-2 concrete actions without being comprehensive. It is above score 2 (which only names the domain generically) but lacks the multiple specific actions needed for score 4.	3 / 5
Completeness	It answers both what ("Memberspot.io integration. Manage Organizations.") and when ("Use when the user wants to interact with Memberspot.io data") with an explicit trigger clause, avoiding the score-3 cap for missing triggers. It falls short of 5 because the "when" is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural keyword is "Memberspot.io" / "Memberspot.io data", with no synonyms or variations users might say. It has a relevant keyword but misses common variations, fitting anchor 3 rather than 4's broader coverage.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Memberspot.io creates a clear niche with distinct triggers and minimal overlap with other skills. It clearly fits the score-5 anchor for a distinct, low-conflict niche.	5 / 5
	Total	15 / 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/memberspotio/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.