Name: wisepops
Rating: 56.8 (1 reviews)
Author: membranedev

wisepops

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

Quality

65%

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/wisepops/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 delivers executable CLI guidance with a well-sequenced connection workflow and solid state-handling feedback loops. It would score higher by trimming the introductory product explanation, consolidating the duplicated actions section, and replacing placeholders with fully concrete examples.

Suggestions

Cut or compress the opening 'What is WisePops' paragraph since Claude does not need the platform explained.

Merge 'Searching for actions' and 'Popular actions' into one section to remove duplicated command guidance.

Add a final verification step (e.g. confirming an action's output field or a sample GET via the proxy) so the run workflow closes with an explicit success check.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but the opening 'WisePops is a popup and marketing message platform...' paragraph and asides like 'This is the fastest way to get a connection' explain context Claude largely already knows and could be trimmed.	3 / 5
Actionability	Concrete, executable commands appear throughout ('membrane connection ensure', 'membrane action run', 'membrane request') with a flags table and JSON input examples, covering the common cases; placeholder tokens like CONNECTION_ID and <actionId> are the only minor gaps keeping it from a 5.	4 / 5
Workflow Clarity	A clear install → auth → connect → search → run/proxy sequence is present with explicit polling checkpoints and state branches (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) for error recovery; the redundant 'Popular actions' section and absence of a final success-check are minor gaps below a 5.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is organized into clearly headed sections with no nested or broken references and one external docs link, giving good navigable structure, though the 'Popular actions' block duplicates 'Searching for actions' content.	4 / 5
	Total	15 / 20 Passed

Description

62%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 pairs a what/when structure around a clearly named product, but its action verbs are generic and it leans heavily on the brand name rather than varied natural trigger terms. Tightening the capabilities and adding synonyms would lift the specificity and trigger scores.

Suggestions

Replace generic verbs with concrete WisePops operations, e.g. 'create and target popups, manage campaigns, sync audiences, and review display-condition rules'.

Add natural user phrasings/synonyms such as 'popups, on-site messages, email capture, promo bars' so the trigger matches how users actually ask.

Sharpen the 'Use when' clause to name the specific situations, e.g. 'Use when the user wants to create or edit WisePops popups, campaigns, or audience segments'.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the WisePops domain plus a couple of actions, but the verbs ('manage', 'automate') are generic rather than concrete operations; not comprehensive enough for a 4.	3 / 5
Completeness	It states a clear 'what' ('WisePops integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with WisePops data.'); both are present though the trigger clause is somewhat thin, which keeps it just below a 5.	4 / 5
Trigger Term Quality	The description repeats the brand ('WisePops', 'WisePops data', 'WisePops integration') but lacks synonyms or natural user phrasings beyond the product name, matching the anchor with 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'WisePops' carves out a distinct niche with minimal overlap risk against other skills; only the generic 'data, records' phrasing keeps it from a 5.	4 / 5
	Total	14 / 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/wisepops/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.