Name: unbounce
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

unbounce

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

Quality

64%

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/unbounce/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 is a well-structured, actionable guide to driving Unbounce via the Membrane CLI, with a clear connection state-machine and polling loop. Its main weaknesses are some over-explanatory prose and broken step numbering.

Suggestions

Remove the opening paragraph explaining what Unbounce is and trim explanatory prose (e.g. "This is the fastest way to get a connection...") to assume Claude's knowledge.

Fix the step numbering: label the "Searching for actions" section as "Step 2" (or remove the "skip to Step 2" / "1b" references) so the sequence is internally consistent.

Flesh out "Popular actions" with one or two concrete Unbounce action examples (e.g. list landing pages, fetch variant report) instead of only pointing to discovery.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph ("Unbounce is a landing page builder that helps marketers...") and scattered prose ("This is the fastest way to get a connection...") explain concepts Claude already knows and could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (login, connection ensure, action list/run, request) plus a flag options table, but the "Popular actions" section only redirects to discovery rather than showing concrete Unbounce-specific examples, leaving a minor gap.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → search → run sequence with a state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling, but step numbering is broken (a referenced "Step 2" is unlabeled and "1b" has no "1a"), creating minor gaps.	4 / 5
Progressive Disclosure	The single-file body is well-organized with clear section headers and no nested references, but at ~140 lines it exceeds the simple-skill threshold and has minor organization gaps ("Popular actions" overlaps with "Searching for actions").	4 / 5
	Total	15 / 20 Passed

Description

61%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 names the Unbounce niche and includes an explicit use-when clause, making it distinct and reasonably complete. Its weakness is generic, non-concrete action language and a lack of domain-specific natural trigger terms.

Suggestions

Replace generic verbs with concrete Unbounce actions, e.g. "Create and optimize landing pages, manage variants, and automate lead-capture workflows."

Add domain-specific trigger terms users naturally say, such as "landing pages," "variants," "A/B tests," or "lead generation."

Tighten the "when" clause to concrete triggers, e.g. "Use when the user wants to manage Unbounce landing pages, variants, or campaign data."

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the Unbounce domain but the verbs are minimal and generic; there are no concrete Unbounce-specific actions (e.g. create landing pages, manage variants) to lift it to a 3.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Unbounce data") are present, but the trigger phrase is generic rather than concrete, so it stops short of a 5.	4 / 5
Trigger Term Quality	The distinctive keyword "Unbounce" appears with a trigger clause ("Use when the user wants to interact with Unbounce data"), but supporting terms (data, records, workflows) are generic and Unbounce-specific natural phrases like landing pages, variants, or leads are missing.	3 / 5
Distinctiveness Conflict Risk	"Unbounce integration" names a specific product, giving it a clear niche with a distinct trigger (the word "Unbounce") and minimal conflict risk with other skills.	5 / 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/unbounce/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.