CtrlK
BlogDocsLog inGet started
Tessl Logo

memberful

Memberful integration. Manage Members, Plans, Products, Discounts. Use when the user wants to interact with Memberful data.

62

Quality

74%

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 ./skills/memberful/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 delivers highly actionable, executable CLI guidance with a well-validated connection workflow and clear structure, but carries some marketing-fluff padding, a repeated command, and minor organizational inconsistencies.

Suggestions

Trim the marketing intro paragraph ("It's used by bloggers, podcasters, and online educators") and the "so you can focus on the integration logic rather than auth plumbing" clause to respect the token budget.

De-duplicate the `membrane action list --intent=QUERY` command that appears in both "Searching for actions" and "Popular actions", and either list actual popular actions under that heading or rename it.

Reconcile the step numbering — either label explicit "Step 1"/"Step 2" sections or drop the orphaned "#### 1b" and "Step 2" references.

DimensionReasoningScore

Conciseness

The body is mostly efficient concrete commands, but includes unnecessary padding (the marketing intro "It's used by bloggers, podcasters, and online educators", the "so you can focus on the integration logic rather than auth plumbing" fluff) and repeats the `action list` command, matching the "mostly efficient but includes some unnecessary explanation" anchor 3 rather than the lean anchor 4.

3 / 5

Actionability

It provides copy-paste-ready commands across the full lifecycle (`npm install -g @membranehq/cli`, `membrane connection ensure`, `membrane action run ... --input '{...}'`, `membrane request`) plus a concrete proxy options table, covering the common cases and matching the "fully executable; copy-paste ready" anchor 5.

5 / 5

Workflow Clarity

The install→authenticate→connect→search→run sequence is clear, and the connection step includes a real validation checkpoint with a feedback loop (poll `--wait`, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after action), but post-run verification of action results is absent, matching anchor 4 rather than the full-checklist anchor 5.

4 / 5

Progressive Disclosure

Sections are well-organized and the self-contained CLI guide is easy to navigate with no external references needed, but the "#### 1b" / "Step 2" numbering is inconsistent (no labeled Step 1/Step 2 exist) and the "Popular actions" heading lists no actual actions, giving minor organization gaps consistent with anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

73%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 the Memberful niche and includes an explicit use-when clause, but its action vocabulary is limited to a single generic "Manage" verb and the trigger phrase is brand-level rather than enumerating concrete user-facing triggers.

Suggestions

Replace the single generic verb "Manage" with distinct concrete actions per entity (e.g., "Create and update Members, subscribe them to Plans, issue Discounts, list Products").

Expand the trigger clause to enumerate concrete triggers a user would naturally say (e.g., "Use when the user mentions Memberful, memberships, subscriptions, plans, or discounts").

Add common synonyms ("subscriptions", "memberships") to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Manage Members, Plans, Products, Discounts" names the domain and enumerates four concrete entities, but relies on a single generic verb ("Manage") rather than listing distinct concrete actions, matching the "names domain and 1-2 concrete actions" anchor and falling short of the multi-verb anchor 4.

3 / 5

Completeness

It states a clear "what" ("Memberful integration. Manage Members, Plans, Products, Discounts.") and an explicit "when" ("Use when the user wants to interact with Memberful data."), satisfying both, but the trigger is generic rather than enumerating concrete trigger phrases, matching anchor 4 and not the explicit-trigger anchor 5.

4 / 5

Trigger Term Quality

It surfaces natural entity terms ("Members", "Plans", "Products", "Discounts") plus the brand "Memberful", giving good keyword coverage, but misses common synonyms a user would naturally say such as "subscriptions" or "memberships", so it sits at anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The unique brand name "Memberful" acts as a distinct niche trigger with minimal conflict risk against other skills, matching the "clear niche with distinct triggers; minimal conflict risk" anchor 5.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.