Name: popupsmart
Rating: 61.6 (1 reviews)
Author: membranedev

popupsmart

Popupsmart integration. Manage Popups, Integrations, Domains, Accounts. Use when the user wants to interact with Popupsmart data.

Quality

73%

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

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 is highly actionable with concrete, executable Membrane CLI commands and a well-sequenced connection workflow with state checkpoints. Its main weakness is mild verbosity in the introductory and best-practices prose, and some reference material kept inline.

Suggestions

Trim the opening marketing paragraph to a one-line purpose statement; remove audience framing ('used by marketers, e-commerce businesses...') that Claude does not need.

Consider moving the proxy flags table and detailed action-discovery reference into a separate reference file, leaving SKILL.md as a concise overview with a one-level-deep pointer.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Popupsmart is a popup builder that helps businesses create website popups and forms to increase conversions. It's used by marketers, e-commerce businesses...") explains market positioning Claude does not need, and some Best Practices prose could be trimmed. This matches 'mostly efficient but includes some unnecessary explanation' rather than 4's 'minor instances only'.	3 / 5
Actionability	The body provides copy-paste-ready commands for every common case (install, login, connection ensure, polling get, action list/run with --input, request with a full flags table), fully executable. This matches 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-again feedback loop after user action, matching 'clear sequence with most checkpoints present'. It is not 5 because there is no explicit validation step or checklist for the overall process.	4 / 5
Progressive Disclosure	Content is organized into clear, navigable sections (Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no nested references and no bundle files present. It is not 5 because at ~150 lines some reference-style material (the proxy flags table, action-discovery details) is inlined rather than split into separate files.	4 / 5
	Total	16 / 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 what the skill does and when to use it, anchored to a distinct product niche. Its main weakness is generic trigger phrasing and a single generic verb ('Manage') applied to the listed entities.

Suggestions

Replace the generic 'Manage' with distinct concrete verbs per entity (e.g., 'Create and edit Popups, connect Integrations, register Domains, view Accounts').

Broaden the 'when' clause with natural user phrasings and synonyms (e.g., 'Use when the user wants to create or edit popups, connect Popupsmart integrations, or manage Popupsmart domains and accounts').

Dimension	Reasoning	Score
Specificity	"Manage Popups, Integrations, Domains, Accounts" enumerates four concrete domain entities, matching the 'lists several specific actions; minor gaps' anchor. It falls short of 5 because the verb is a generic 'Manage' rather than distinct concrete operations per entity.	4 / 5
Completeness	It has an explicit 'what' ("Manage Popups, Integrations, Domains, Accounts") and an explicit 'when' ("Use when the user wants to interact with Popupsmart data"), matching the 'both present; when could be more specific' anchor. It is not 5 because the 'when' trigger is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Trigger terms are limited to the product name and entity nouns ("Popupsmart", "Popups", "Integrations", "Domains", "Accounts"), with no common synonyms or phrasings a user would naturally say. This matches 'some relevant keywords but missing common variations or synonyms' rather than 4's broader coverage.	3 / 5
Distinctiveness Conflict Risk	"Popupsmart integration" names a specific third-party product, giving it a clear niche with distinct triggers and minimal conflict risk with other skills. It clearly matches the 'clear niche with distinct triggers' anchor.	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/popupsmart/SKILL.md
Commit: f484c82

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