Name: cloudpress
Rating: 52 (1 reviews)
Author: membranedev

cloudpress

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

Quality

57%

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/cloudpress/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 is actionable with concrete executable membrane commands and a useful actions table, but it lacks validation/verification steps for destructive and batch operations and inlines reference material that could be split out. Adding checkpoints and reference files would notably improve workflow clarity and progressive disclosure.

Suggestions

Add explicit validation steps for destructive/batch operations — e.g. after running an export, verify with `membrane action run ... get-job` and confirm status before proceeding; before 'Delete Webhook', confirm the webhook ID via list-webhooks.

Move the popular-actions table and proxy flag reference into a separate reference file (e.g. actions.md) referenced from SKILL.md to improve progressive disclosure.

Provide one complete worked example showing full `--input` JSON for a real action (e.g. export-from-connection) so the actionability guidance is copy-paste ready rather than placeholder-based.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and a tight actions table, but it includes some unnecessary filler ('Use action names and parameters as needed') and mild redundancy between list-connections and list-jobs coverage. It is efficient yet could be tightened, matching score 3 rather than 4.	3 / 5
Actionability	It provides concrete, executable `membrane` commands with real flags (search, connect, action list/run, request) and a popular-actions table mapping names to keys. It falls short of 5 because parameter values are placeholders rather than a complete worked example showing full input JSON for a real action.	4 / 5
Workflow Clarity	A clear sequence exists (install CLI, login, connect, search actions, run) but there are no validation or verification checkpoints for destructive or batch operations such as 'Delete Webhook' and 'Export from Connection'. Per the rubric, a destructive/batch skill lacking validation is capped at 3.	3 / 5
Progressive Disclosure	The content is reasonably sectioned with no nested references, but the popular-actions table and the proxy flag reference are inlined rather than split into reference files, and no external references are used. At ~137 lines it does not qualify for the simple-skill exception, so it sits at 3 rather than higher.	3 / 5
	Total	13 / 20 Passed

Description

57%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 is in third person and includes an explicit 'Use when' trigger, but its capability list ('Manage data, records, and automate workflows') is generic and lacks concrete Cloudpress actions. Strengthening specificity and trigger term coverage would raise the score.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Cloudpress actions such as 'run content exports, manage webhooks, and list collections'.

Expand the 'Use when' clause with concrete trigger phrases users would say, e.g. 'Use when the user wants to export content between WordPress sites, manage Cloudpress webhooks, or check export job status'.

Mention key entities (webhooks, export jobs, collections, connections) so the description is more distinguishable from other Membrane integration skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Cloudpress integration') but the stated actions ('Manage data, records, and automate workflows') are minimal and generic, with no concrete Cloudpress capabilities (e.g. exports, webhooks, collections) listed. It sits below the score-3 anchor, which requires 1-2 concrete named actions.	2 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' with an explicit 'Use when the user wants to interact with Cloudpress data' clause. The 'when' is present and clear but could be more specific with concrete trigger phrases, matching score 4 rather than 5.	4 / 5
Trigger Term Quality	'Cloudpress' is named and 'interact with Cloudpress data' is a relevant phrase, but common natural variations or synonyms a user would say are missing. It has some relevant keywords without comprehensive coverage, matching the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The Cloudpress niche is named with distinct triggers, giving mostly-distinct identity with only minor overlap risk against other Membrane integration skills. It does not reach 5 because the actions themselves are generic enough that the skill is distinguished mainly by the product name.	4 / 5
	Total	13 / 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/cloudpress/SKILL.md
Commit: f484c82

Reviewed: ~11 hours 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.