Name: scaledrone
Rating: 55.2 (1 reviews)
Author: membranedev

scaledrone

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

Quality

62%

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/scaledrone/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 highly actionable with executable Membrane CLI commands, a clear connection state machine, and useful reference tables, weakened only by a redundant section and a broken 'Step 2' cross-reference.

Suggestions

Remove or merge the 'Popular actions' section, which repeats the action-list command already shown under 'Searching for actions'.

Fix the dangling 'Step 2' reference by either labeling the post-connection steps (e.g. searching/running actions) as Step 2 or removing the reference.

Trim the introductory paragraph defining Scaledrone, since Claude can infer the service's purpose from the official docs link.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and tables, but the intro paragraph explaining what Scaledrone is and the duplicated action-list command under 'Popular actions' add padding that could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands with flags, JSON input examples, and a thorough proxy-options table cover the common cases, with only minor placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	The connect-to-ready workflow has explicit state polling and feedback loops (re-poll after CLIENT_ACTION_REQUIRED), though the undefined 'Step 2' reference and the '1b' sub-step labeling introduce a minor sequencing gap.	4 / 5
Progressive Disclosure	Content is well-sectioned with no bundle files present or referenced; organization is good, though the ~140-line length with an inline flags table could arguably be split, leaving minor organization gaps.	4 / 5
	Total	15 / 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 correctly pairs a 'what' with an explicit 'Use when' trigger and leverages a distinctive brand name, but its action vocabulary is generic rather than reflecting Scaledrone's realtime-messaging capabilities.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Scaledrone actions such as 'publish messages to rooms, subscribe to channels, and manage room members'.

Expand the trigger phrase to include natural synonyms users say, e.g. 'Use when the user wants to send realtime messages, build chat, or work with Scaledrone rooms and channels'.

Drop the generic nouns 'data' and 'records' which do not map to any Scaledrone concept and dilute distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the Scaledrone domain but the actions ('Manage data, records, and automate workflows') are generic and not concrete Scaledrone-specific operations like publishing to rooms or subscribing to channels, matching the 'minimal or generic' anchor rather than the comprehensive one.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Scaledrone data') are present, though the 'when' trigger is somewhat generic.	4 / 5
Trigger Term Quality	The main natural keyword is the 'Scaledrone' brand name itself, but common user synonyms like 'realtime messaging', 'chat', 'rooms', or 'messages' are absent, leaving some natural variations missing.	3 / 5
Distinctiveness Conflict Risk	The 'Scaledrone integration' proper-noun brand gives it a clear niche with minimal conflict risk, though the generic action language ('manage data, records') introduces minor overlap with adjacent data skills.	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/scaledrone/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.