Name: ibm-cloud
Rating: 55.2 (1 reviews)
Author: membranedev

ibm-cloud

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

Quality

63%

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

Quality

Content

63%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 executable Membrane CLI commands and a well-checkpointed connection workflow, but it carries concept-explanation padding and is a monolithic file with no progressive disclosure. Overall solid, with room to tighten and externalize.

Suggestions

Remove or drastically shorten the opening "IBM Cloud is a suite of cloud computing services..." paragraph and the resource overview list, which restate knowledge Claude already has.

Add a validation checkpoint before destructive operations, e.g. suggest confirming or dry-running before `membrane request` with `-X DELETE` or before running mutating actions.

Move the resource enumeration and the proxy options table into a separate reference file (e.g. references/resources.md) linked from SKILL.md so the main file stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The intro paragraph ("IBM Cloud is a suite of cloud computing services from IBM, offering IaaS, PaaS, and SaaS...") and the lengthy resource overview list explain concepts Claude already knows, while the Membrane CLI guidance that Claude does not know is reasonably efficient, leaving it mostly efficient with some removable padding.	3 / 5
Actionability	It provides many concrete, copy-paste-ready bash commands (install, login, connection ensure/get, action list/run, request) plus a concrete proxy-options table; the only gaps are expected placeholders like CONNECTION_ID and QUERY rather than missing steps.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR, SETUP_FAILED) and a re-poll feedback loop, but there is no validation guidance around potentially destructive action runs or proxy DELETE calls and the "Step 2" cross-reference is loose.	4 / 5
Progressive Disclosure	The header structure is reasonable, but there are no bundle files and the entire ~155-line skill is a monolithic document with zero file references, inlining content (the resource enumeration, proxy options, clientAction detail) that would be clearer split into separate reference files; the under-50-line exception does not apply.	3 / 5
	Total	14 / 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 correctly includes an explicit "Use when" trigger and ties it to a distinct named platform, but its action verbs are generic and it lacks keyword synonyms. It is competent but not exemplary.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Provision Kubernetes clusters, manage VPC resources, and invoke Cloud Functions" instead of "Manage data, records, and automate workflows".

Broaden trigger terms to include natural synonyms users say, such as "IBM Cloud services", "IBM cloud resources", or specific service names (VPC, Cloud Functions, Object Storage).

Tighten the "when" clause to name concrete scenarios rather than the broad "interact with IBM Cloud data".

Dimension	Reasoning	Score
Specificity	Names the IBM Cloud domain plus two-to-three action areas ("Manage data, records, and automate workflows"), but the verbs are generic ("manage", "automate") rather than concrete operations, sitting above the single-generic-action anchor yet short of comprehensive concrete coverage.	3 / 5
Completeness	It states both a "what" ("IBM Cloud integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with IBM Cloud data."), but the trigger is broad and the "what" is generic rather than concrete, so it falls short of the fully-explicit anchor.	4 / 5
Trigger Term Quality	It captures the core natural keyword "IBM Cloud" and pairs it with an explicit "Use when" clause, but offers no synonyms or variations users might say (e.g. "IBM Cloud services", "Bluemix", specific service names), so coverage is relevant but thin.	3 / 5
Distinctiveness Conflict Risk	"IBM Cloud" is a specific named platform giving a clear niche with distinct triggers; the only overlap risk is with closely related cloud-provider skills, which keeps it just below the minimal-conflict anchor.	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/ibm-cloud/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.