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

cloudbees

CloudBees integration. Manage data, records, and automate workflows. Use when the user wants to interact with CloudBees 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/cloudbees/SKILL.md

Quality

Content

72%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 highly actionable with concrete, executable membrane commands and a clear connection workflow, but it lacks validation steps for destructive operations and inlines a large reference table that should be split into a referenced file.

Suggestions

Add explicit validation/verification checkpoints before destructive actions (e.g., confirm the flag/environment exists and prompt for confirmation before delete-* actions).

Move the 20-row Popular actions table into a separate referenced file (e.g., references/actions.md) and link to it from the body.

Fix the undefined "Step 2" reference by either labeling the Searching/Running sections as numbered steps or removing the dangling cross-reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and a compact actions table, but the opening marketing-style paragraph ("CloudBees provides a software delivery platform for enterprises...") and the sparse Overview bullets could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste ready membrane commands (login, connection ensure, action list/run, request) with flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connection-setup sequence and polling loop are present, but destructive actions (delete-flag, delete-environment, delete-target-group) lack validation/verification checkpoints, and "Step 2" is referenced without being defined, so the workflow-clarity cap applies.	3 / 5
Progressive Disclosure	The body is well-sectioned with clear headings, but the 20-row Popular actions table is inline reference content that belongs in a separate file, and no bundle files are provided or referenced.	3 / 5
	Total	15 / 20 Passed

Description

73%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 with a clear CloudBees-specific trigger, but the capability actions ("manage data, records, automate workflows") are generic and would benefit from concrete verbs tied to CloudBees features.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete CloudBees capabilities such as managing feature flags, target groups, environments, and applications.

Expand the when-clause with concrete trigger phrases users would say (e.g., "Use when managing CloudBees feature flags, target groups, or environments").

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the CloudBees domain plus a few actions, but the actions are generic rather than concrete capabilities, matching the anchor that names the domain with limited action specificity.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with CloudBees data"), but the when-clause is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	"CloudBees", "interact with CloudBees data", "data, records", and "workflows" give good natural keyword coverage a user would actually say, though a few synonymous phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	CloudBees is a distinct branded product and the trigger "interact with CloudBees data" carves a clear niche with minimal overlap risk against other skills.	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/cloudbees/SKILL.md
Commit: f484c82

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