Name: datascope
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

datascope

DataScope integration. Manage Organizations. Use when the user wants to interact with DataScope data.

Quality

72%

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

Quality

Content

82%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 strong state-driven connection workflow including a feedback loop. Its main weaknesses are minor verbosity in the overview/auth prose and inconsistent step numbering that slightly muddies the workflow sequence.

Suggestions

Tighten the intro and auth prose by dropping marketing-style explanations (e.g. 'so you can focus on the integration logic rather than auth plumbing') and the generic DataScope product pitch.

Make the workflow numbering consistent: either relabel 'Step 2' explicitly or remove the 'skip to Step 2' / lone '1b' references in favor of a flat, clearly ordered sequence.

Consider moving the Popular actions table and proxy flag reference into a reference file referenced one level deep from SKILL.md to reduce the monolithic length and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with copy-paste command blocks and tables, but includes light padding such as 'so you can focus on the integration logic rather than auth plumbing' and a marketing-style product overview of DataScope, placing it just below the fully lean anchor at 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure, polling, action list/run, request) plus a concrete popular-actions table and flag reference, covering the common cases comprehensively.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with an explicit polling feedback loop and state-based next actions (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the step numbering is inconsistent ('skip to Step 2' with no labeled Step 2, and a lone '1b' subsection), leaving minor gaps versus the fully checkpointed anchor at 5.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-organized into clear sections (install, auth, connecting, searching, actions, proxy, best practices) and does not need external references, but at ~155 lines the popular-actions and proxy-option tables could live in separate files, keeping it just short of the ideal split structure at 5.	4 / 5
	Total	17 / 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 correctly pairs a 'what' with an explicit 'Use when...' trigger and leverages a distinctive product name, but the capability list is thin and generic ('Manage Organizations') compared to the rich action surface the body documents. Adding concrete action keywords would lift specificity and trigger coverage.

Suggestions

Replace the generic 'Manage Organizations' with 2-3 concrete capabilities, e.g. 'Manage datasets, metadata objects, locations, and form answers in DataScope.'

Expand the 'Use when' clause with natural trigger phrases users would say, such as 'Use when the user wants to query DataScope datasets, update metadata, or list locations and form answers.'

Include entity-level keywords (datasets, schemas, metadata, locations, forms) so the description surfaces the breadth shown in the body's Popular actions table.

Dimension	Reasoning	Score
Specificity	The description names the domain ("DataScope integration") and one action ("Manage Organizations"), but that action is generic and the broad capability set documented in the body (datasets, queries, models, locations, forms) is not reflected, so it sits at the 'names domain + 1-2 actions, not comprehensive' anchor rather than the fuller coverage of 4-5.	3 / 5
Completeness	It states both what ("DataScope integration. Manage Organizations.") and when ("Use when the user wants to interact with DataScope data."), matching the anchor where both are present but the 'when' could be more specific; it does not reach 5 because neither side names concrete trigger phrases beyond the product name.	4 / 5
Trigger Term Quality	"DataScope" is a distinctive proper-noun trigger a user would naturally say, and "interact with DataScope data" repeats it, but there are no synonyms or entity-level terms (datasets, metadata, locations) that users would also say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The "DataScope" proper noun gives it a clear, low-conflict niche, but the generic "Manage Organizations" verb keeps it just short of the maximal-distinctiveness anchor at 5.	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/datascope/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.