Name: scalr
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

scalr

Scalr integration. Manage Organizations, Users, Goals. Use when the user wants to interact with Scalr data.

Quality

67%

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

Quality

Content

68%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 commands and a solid connection-setup workflow, but loses points on conciseness (a non-essential product intro and minor redundancy) and on workflow clarity because action/proxy operations that can be destructive include no validation or verification step. Tightening the prose and adding a verify-after-run checkpoint would address the weakest dimensions.

Suggestions

Remove or shrink the product-description opening ("Scalr is a hybrid cloud management platform...") since it does not aid execution.

Merge the redundant "Searching for actions" and "Popular actions" sections into one discovery section to reduce repetition.

Add a verification step after `membrane action run` and `membrane request` (e.g., re-fetch or inspect the `output` field to confirm the change took effect) since these can perform destructive or batch operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes a product-marketing intro sentence ("hybrid cloud management platform used by enterprises...") Claude does not need and minor redundancy between the "Searching for actions" and "Popular actions" sections that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands for every common case (install, login, headless login, connection ensure, polling, action list/run, proxy) plus a complete options table, with clearly marked placeholders for substitution.	5 / 5
Workflow Clarity	The connection-setup flow is well sequenced with state-based validation checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but running actions and proxy requests (which support POST/PUT/PATCH/DELETE) lack any verification step, capping workflow clarity at 3 per the destructive/batch guidance.	3 / 5
Progressive Disclosure	The single self-contained file is organized into clear, navigable sections with no external bundle files and no large reference dump that belongs elsewhere; the only minor gap is the slight overlap between the "Searching for actions" and "Popular actions" sections.	4 / 5
	Total	15 / 20 Passed

Description

66%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 covers the essential what/when structure and is well-scoped to a distinct named platform, but relies on the generic verb "Manage" and narrow trigger phrasing that limit specificity and trigger-term coverage. Tightening the action verbs and broadening the natural-language triggers would lift the weaker dimensions.

Suggestions

Replace the generic verb "Manage" with specific concrete actions, e.g. "Create, list, update, and delete Organizations, Users, and Goals in Scalr."

Expand the trigger clause with natural user phrasings and entity terms, e.g. "Use when the user wants to manage Scalr organizations, users, goals, or workspaces, or interact with Scalr data."

Consider naming a few more Scalr entities (e.g. Environments, Workspaces, Policies) shown in the body to broaden capability coverage.

Dimension	Reasoning	Score
Specificity	It names the Scalr domain and three target entities ("Manage Organizations, Users, Goals"), but "Manage" is a single generic verb rather than several specific concrete actions (create/list/update/delete), so coverage is not comprehensive.	3 / 5
Completeness	It states both a clear "what" ("Manage Organizations, Users, Goals") and an explicit "when" ("Use when the user wants to interact with Scalr data"), though the trigger clause is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	The keyword "Scalr" and the phrase "interact with Scalr data" are present, but it omits the entity terms (Organizations, Users, Goals) as natural triggers and has no synonyms or variations a user might actually say.	3 / 5
Distinctiveness Conflict Risk	Scalr is a specific named platform, giving the skill a clear niche with distinct triggers and minimal risk of conflicting with unrelated skills.	5 / 5
	Total	15 / 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/scalr/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.