Name: softlayer
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

softlayer

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

Quality

66%

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

Quality

Content

75%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 CLI commands and a clear connection state machine with feedback loops. Its weak spots are an unnecessary marketing-style opener and slightly loose step labeling ('Step 2' references) that slightly muddy the workflow.

Suggestions

Trim or remove the opening background paragraph ('SoftLayer, now part of IBM Cloud...') since it does not guide execution.

Either add a labeled 'Step 2: Search and run actions' section or remove the dangling 'Skip to Step 2' references so the workflow numbering is consistent.

Consider moving the proxy request flag table and action-run details into a references/ file, keeping SKILL.md as a lean overview with a one-level-deep pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and examples, but the opening paragraph ('SoftLayer, now part of IBM Cloud, provides on-demand bare metal and virtual servers. It's used by businesses...') explains background Claude does not need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action run, request) plus a complete flag table, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The install-authenticate-connect-search-run sequence is clear with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and feedback loops ('poll again'), but references to 'Step 2' are not backed by a labeled Step 2 section, leaving a minor navigation gap below the 5 anchor.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly labeled sections with no nested references and no bundle files present, but the ~147-line body keeps proxy/action reference material inline where a separate reference file could improve navigation, fitting the 'good structure; minor organization gaps' anchor.	4 / 5
	Total	16 / 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 successfully pairs a clear SoftLayer niche with an explicit 'Use when' trigger, satisfying both what and when. Its main weakness is generic action language that under-specifies the concrete capabilities and natural trigger terms.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete SoftLayer operations such as 'provision bare metal and virtual servers, manage bandwidth pools, and open support tickets'.

Expand the trigger clause with natural user phrases, e.g. 'Use when the user wants to manage SoftLayer/IBM Cloud infrastructure, servers, or support tickets'.

Keep the existing third-person voice and concise length; only swap vague nouns for specific SoftLayer entities.

Dimension	Reasoning	Score
Specificity	The description names the SoftLayer domain but its actions are generic ('Manage data, records, and automate workflows') rather than concrete operations like provisioning servers or managing bandwidth pools, matching the 'actions are minimal or generic' anchor rather than the 3 anchor which expects concrete actions.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with SoftLayer data'), but the 'when' clause is somewhat generic and could name more specific triggers, fitting the 4 anchor.	4 / 5
Trigger Term Quality	'SoftLayer' is a relevant natural keyword and 'interact with SoftLayer data' is a usable phrase, but coverage is thin with no synonyms or common variations beyond the product name itself.	3 / 5
Distinctiveness Conflict Risk	SoftLayer is a distinct, named niche so conflict risk is low, but the surrounding language ('manage data', 'records') is generic enough to leave minor overlap risk, placing it just below the 5 anchor.	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/softlayer/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.