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

Blog Docs Log in Get started

range

Range integration. Manage Workspaces. Use when the user wants to interact with Range 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/range/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, highly actionable guide with a clear connection-state workflow and feedback loop. Its weaknesses are a small amount of marketing padding and the absence of a fully worked example plus result-validation guidance.

Suggestions

Trim the marketing-style Range intro to one factual sentence and remove 'so you can focus on the integration logic rather than auth plumbing'.

Add one worked end-to-end example (e.g. list and run a 'create update' action) with a concrete intent and the resulting output field, replacing generic QUERY/<actionId> placeholders.

Add a brief validation step after running actions or proxy requests, such as checking the response status/error fields before reporting success.

Dimension	Reasoning	Score
Conciseness	The command snippets and state tables are lean, but the Range marketing intro ('built for high-performing teams... used by managers, project managers...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need, matching the mostly-efficient-with-some-excess anchor.	3 / 5
Actionability	Provides copy-paste-ready commands across install, login, connection ensure/get, action list/run, and request proxy, plus a flag table; falls short of 5 because intent and action IDs remain generic placeholders (QUERY, <actionId>) without a worked end-to-end example.	4 / 5
Workflow Clarity	Sequences install -> authenticate -> connection ensure -> poll for READY -> search/run actions, with explicit state branches (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop; short of 5 because there is no validation of action results or output-checking checkpoint after running actions.	4 / 5
Progressive Disclosure	Single well-organized file with clear section headers covering overview, setup, connection, discovery, actions, proxy, and best practices; no external references are needed and none are bundled, so it fits the good-structure anchor rather than the one-level-deep-references anchor.	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 is functional and explicitly answers both what and when, anchored to a named product for distinctiveness. Its main weaknesses are a single generic action verb and a thin set of natural trigger terms.

Suggestions

Replace or expand 'Manage Workspaces' with 2-3 concrete actions such as 'plan check-ins, run meetings, track action items'.

Broaden the 'Use when' clause with natural trigger phrases like 'meeting agendas, async check-ins, action items, or Range tasks'.

Add file-extension or entity keywords (e.g. 'Range updates, goals, tasks') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Range domain and a single action ('Manage Workspaces'), but 'Manage' is generic and no other concrete capabilities are listed, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both a 'what' ('Range integration. Manage Workspaces.') and an explicit 'when' ('Use when the user wants to interact with Range data') are present; the when clause is explicit rather than implied, though it could be more specific, fitting the anchor for both present with room for sharper triggers.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Range data' supplies the product keyword and 'Workspaces', but misses common natural synonyms users would say (meetings, check-ins, agendas, tasks), so coverage has gaps rather than being comprehensive.	3 / 5
Distinctiveness Conflict Risk	'Range' names a specific product and 'Range data' is a distinct trigger, giving a clear niche with low conflict risk; falls short of 5 only because the trigger vocabulary is thin enough that overlap with generic 'data' skills is conceivable.	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/range/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.