Name: wishpond
Rating: 52.8 (1 reviews)
Author: membranedev

wishpond

Wishpond integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wishpond data.

Quality

59%

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

Quality

Content

61%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 actionable and the connection workflow is well-sequenced with validation states, but it carries some background padding and lacks verification checkpoints for the destructive action-running step.

Suggestions

Remove or condense the opening marketing paragraph about what Wishpond is; assume Claude knows the domain.

Add a verification checkpoint after running actions (e.g., check the output field for errors, confirm affected records) so destructive operations are validated.

Either populate the "Popular actions" section with actual commonly-used actions or remove the empty heading to avoid misleading the reader.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph ("Wishpond is a marketing platform designed to help small businesses grow their customer base...") and a few padded sentences explain background Claude does not need, so it could be tightened.	3 / 5
Actionability	It provides copy-paste ready commands (membrane connection ensure, action list, action run, request) with a full proxy-flag table, but the "Popular actions" heading only re-states the discovery command without listing actions, and membrane vs npx invocation is inconsistent — minor gaps.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state checks (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, but running actions on Wishpond data is a potentially destructive/batch operation with no verification checkpoint, capping this dimension at 3.	3 / 5
Progressive Disclosure	The body is organized into clearly labeled sections and uses runtime action discovery (membrane action list) instead of inlining a huge catalog; no bundle files exist, but structure is good with only minor gaps like the empty "Popular actions" section.	4 / 5
	Total	14 / 20 Passed

Description

57%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 correctly targets a named platform and includes an explicit Use-when trigger, but its action list is generic rather than concrete, limiting specificity and trigger richness.

Suggestions

Replace generic verbs with concrete Wishpond operations, e.g. "Manage campaigns, contacts, landing pages, promotions, and forms".

Expand the trigger clause to surface natural user phrasing such as "Wishpond contacts", "landing pages", or "marketing automation".

Name the actual Wishpond resources (Campaigns, Contacts, Forms) so the what-clause is comprehensive rather than abstract.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Wishpond integration") but its actions — "Manage data, records, and automate workflows" — are generic rather than concrete Wishpond-specific operations, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Wishpond data"), but the what is generic rather than concrete, so it sits at the level where both are present yet the when could be more specific.	4 / 5
Trigger Term Quality	It surfaces the product name "Wishpond" and the natural phrase "interact with Wishpond data", but beyond the product name the remaining keywords (data, records, workflows) are generic and lack common variations or synonyms.	3 / 5
Distinctiveness Conflict Risk	"Wishpond" is a named niche platform giving it a distinct trigger with minimal conflict risk, but the generic action phrasing ("manage data, records, automate workflows") leaves minor overlap risk with other marketing/CRM skills.	4 / 5
	Total	13 / 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/wishpond/SKILL.md
Commit: f484c82

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