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

Blog Docs Log in Get started

stripo

Stripo integration. Manage Users, Workspaces. Use when the user wants to interact with Stripo 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/stripo/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 body is a well-structured, actionable guide to driving Stripo through the Membrane CLI with real feedback loops for connection setup. Its main weaknesses are a padded introductory paragraph, a missing concrete Stripo action example, and inconsistent step numbering.

Suggestions

Trim or remove the opening marketing paragraph about what Stripo is and who uses it; Claude does not need that context to operate the CLI.

Fix the step numbering in 'Connecting to Stripo' — label the connection-ensure step as Step 1 and resolve the orphaned 'Step 2' / '1b' references so the sequence is unambiguous.

Add one fully worked example of running a concrete Stripo action (e.g. listing email templates with a real input) end-to-end, including how to parse the `output` field.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI commands, but the opening paragraph explaining what Stripo is and who uses it ('drag-and-drop interface... used by email marketers, designers, and agencies') is padding Claude does not need, matching the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Provides many copy-paste-ready CLI commands plus a flags table for proxy requests, but stops short of a concrete worked example running an actual Stripo action with real parameters, leaving a minor gap versus the fully executable 5.	4 / 5
Workflow Clarity	Clear install→authenticate→connect→poll→run sequence with a genuine feedback loop (poll --wait, branch on state, re-poll after CLIENT_ACTION_REQUIRED), but the step numbering is broken ('skip to Step 2' with no Step 1/2, a '1b' with no 1a), a minor gap.	4 / 5
Progressive Disclosure	A single well-sectioned file with clear headers and no unnecessary external references (none provided, none needed); minor redundancy between 'Searching for actions' and 'Popular actions' keeps it just below 5.	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 answers both what and when in third person and names a distinct app, but its action list and trigger keywords are narrow relative to the skill's full scope. Expanding the entity coverage and concrete trigger phrases would raise it.

Suggestions

Expand 'Manage Users, Workspaces' to mention more of the key Stripo entities (Email Templates, Folders, Emails, Contacts, Segments) to improve specificity and trigger coverage.

Replace the generic 'interact with Stripo data' with concrete trigger phrases users would say, e.g. 'Use when managing Stripo users, workspaces, email templates, or contacts'.

Add the natural term 'email templates' since Stripo is fundamentally an email template builder — it is currently absent from the description.

Dimension	Reasoning	Score
Specificity	Names the domain (Stripo) and two concrete actions ('Manage Users, Workspaces'), but coverage is thin given the body lists ~20 entities; this matches the '1-2 concrete actions' anchor rather than the comprehensive 5.	3 / 5
Completeness	Both 'what' ('Manage Users, Workspaces') and an explicit 'when' ('Use when the user wants to interact with Stripo data') are present, but the trigger clause is generic rather than concrete, matching the 4 anchor over the explicit-phrase 5.	4 / 5
Trigger Term Quality	Includes the app name and a couple of entity keywords ('Users', 'Workspaces', 'interact with Stripo data'), but misses common variations and the many other Stripo entities a user might name, fitting the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app Stripo gives it a clear niche with minimal conflict risk, though the generic 'interact with Stripo data' trigger keeps it just below the maximally distinct 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/stripo/SKILL.md
Commit: f484c82

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