Name: poper
Rating: 48.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

poper

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

Quality

53%

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

Quality

Content

57%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 provides mostly executable, copy-pasteable membrane CLI guidance for connecting to Poper and running or proxying actions, but it opens with speculative filler, lacks verification checkpoints around mutating actions, and keeps everything in one file with no progressive disclosure references.

Suggestions

Remove the speculative opening paragraph ('Poper is a SaaS application that likely helps... It's probably used by marketers...') which Claude does not need.

Add explicit validation/verification steps after running actions or proxy requests (e.g., check the `output` field, confirm state changes, handle `CONFIGURATION_ERROR`) to lift workflow clarity.

Move the proxy flag reference table and the clientAction schema detail into a separate references file and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-pasteable commands, but the opening line ('Poper is a SaaS application that likely helps... It's probably used by marketers...') is speculative filler Claude does not need, and some prose restates CLI behavior already shown.	3 / 5
Actionability	Concrete, executable membrane CLI commands with flags and JSON examples cover installation, auth, connection, action search/run, and proxying; minor gaps such as leaving CONNECTION_ID as an unexplained placeholder keep it from 5.	4 / 5
Workflow Clarity	A connect -> poll -> READY/CLIENT_ACTION_REQUIRED sequence is present with state-based branching, but the documented actions (action run, proxy requests) involve external mutation yet lack explicit validation or verification checkpoints after execution, capping the score per the batch/destructive rule.	3 / 5
Progressive Disclosure	The single SKILL.md has no bundle files; section headers give some structure, but the proxy flag table and full clientAction schema are inlined content that could live in a reference file, and there are no one-level-deep references to split it out.	3 / 5
	Total	13 / 20 Passed

Description

48%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 identifies a clear niche (the Poper app) and includes an explicit 'Use when' trigger, but the 'what' is generic ('Manage data, records, and automate workflows') without Poper-specific concrete actions or richer trigger synonyms.

Suggestions

Replace generic verbs with concrete Poper-specific actions (e.g., 'Create and manage pop-up notifications, capture visitor data, and trigger workflows') to lift specificity.

Expand trigger terms with natural synonyms users would say, such as 'pop-ups', 'notifications', 'lead capture', or 'website overlays'.

Tighten the 'what' to name actual Poper objects the skill operates on so it is clearly distinguishable from generic data-management skills.

Dimension	Reasoning	Score
Specificity	The description 'Manage data, records, and automate workflows' names the domain but the actions are minimal and generic; no concrete Poper-specific capabilities are enumerated.	2 / 5
Completeness	There is a clear 'Use when...' trigger clause ('Use when the user wants to interact with Poper data') and a vague 'what' ('Manage data, records, and automate workflows'); the 'when' is present but the 'what' is only weakly concrete, so it sits at the clear-what/weak-when boundary, landing at 3.	3 / 5
Trigger Term Quality	'Poper data' is a relevant keyword and 'Use when the user wants to interact with Poper data' provides a natural trigger phrase, but synonyms and concrete variants (e.g., pop-ups, notifications) are missing.	3 / 5
Distinctiveness Conflict Risk	'Poper integration' and 'interact with Poper data' carve out a clear niche with a named app, so conflict risk with other skills is low; only minor overlap risk with generic data-management skills keeps it from 5.	4 / 5
	Total	12 / 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/poper/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.