Name: scaled-access
Rating: 56.8 (1 reviews)
Author: membranedev

scaled-access

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

Quality

65%

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/scaled-access/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 a well-structured, actionable integration guide with executable commands and a real polling/state feedback loop. Its main weakness is mild padding in the overview and slightly broken step numbering.

Suggestions

Trim the opening "Scaled Access is a SaaS platform..." paragraph and the Overview entitlement bullet list, which restate concepts Claude already knows.

Fix the broken step numbering: label an explicit "Step 2" (or relabel "1b") so the "skip to Step 2" reference resolves.

Consider splitting the flags table and clientAction state-machine reference into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening platform description ("Scaled Access is a SaaS platform that helps manage and control user access...") and the Overview bullet list explain concepts Claude largely already knows and could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready commands across install, auth, connection, action search/run, and proxy, plus a flags table; minor gaps are limited to placeholders like CONNECTION_ID and a vague "Agent Types... etc." list.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→poll→search→run sequence with a state-machine feedback loop (poll again after CLIENT_ACTION_REQUIRED) is present, but the dangling "skip to Step 2" and an unlabeled "1b" create a minor sequencing gap.	4 / 5
Progressive Disclosure	No bundle files are present, but the single-file body is well-organized with clear section headers and the reference-like flags table and state details are appropriately inline for this size; minor gaps only.	4 / 5
	Total	15 / 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 clearly states both purpose and trigger tied to a specific named product, but the capability verbs are generic. It is solid and serviceable, just lacking concrete action specificity and trigger synonyms.

Suggestions

Replace generic verbs with concrete Scaled Access capabilities (e.g., "provision entitlements, manage roles, audit user access") to lift specificity.

Add natural trigger synonyms users might say (e.g., "access governance", "entitlements", "least privilege") beyond the product name.

Tighten the "what" clause so it reads as a list of specific actions rather than abstract categories.

Dimension	Reasoning	Score
Specificity	Names the domain (Scaled Access) and a couple of actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete capabilities, matching the anchor for 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Both "what" (manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Scaled Access data") are present and explicit, though the "what" is somewhat generic rather than fully concrete.	4 / 5
Trigger Term Quality	Includes the product name and terms ("data", "records", "workflows") plus an explicit trigger ("Use when the user wants to interact with Scaled Access data"), but lacks synonyms or natural variations beyond the product name.	3 / 5
Distinctiveness Conflict Risk	Tying the description to the named product Scaled Access gives it a clear niche with minimal conflict risk, but the generic verb phrases ("manage data, records, automate workflows") leave minor overlap risk with other integration skills.	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/scaled-access/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.