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

Blog Docs Log in Get started

scopemaster

ScopeMaster integration. Manage Organizations, Users. Use when the user wants to interact with ScopeMaster 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/scopemaster/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 content is a well-structured, actionable guide to the Membrane/ScopeMaster CLI workflow with concrete commands and state-based checkpoints, though it carries some padding and a couple of structural inconsistencies.

Suggestions

Trim the ScopeMaster overview paragraph and the 'auth plumbing' aside to assume Claude's competence and save tokens.

Remove or merge the 'Popular actions' section, which duplicates the 'Searching for actions' guidance.

Fix the 'skip to Step 2' reference by numbering the workflow steps explicitly (e.g., 1. Connect, 2. Search actions, 3. Run actions).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI guidance, but the ScopeMaster intro paragraph, the 'so you can focus on the integration logic rather than auth plumbing' aside, and the redundant 'Popular actions' section could be tightened, fitting anchor 3.	3 / 5
Actionability	It provides copy-paste-ready bash commands throughout (install, login, connection ensure, action list/run, proxy with a flags table) with --json usage, matching anchor 4; only minor placeholder gaps (CONNECTION_ID, actionId) keep it from 5.	4 / 5
Workflow Clarity	A clear install-to-run sequence with state-based feedback checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-polling) fits anchor 4; the dangling 'skip to Step 2' with no labeled Step 2 is a minor gap preventing 5.	4 / 5
Progressive Disclosure	A single well-organized file with clear section headers and no nested references fits anchor 4; minor organization gaps (the dangling step reference and the redundant 'Popular actions' section) and the lack of any split-out detail files keep it from 5.	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 successfully pairs a what-statement with an explicit 'Use when...' trigger and anchors on a distinct named product, but its action verbs are generic and the trigger terms lack synonyms or specificity.

Suggestions

Replace the generic verb 'Manage' with concrete actions (e.g., 'Create, list, and update Organizations and Users').

Expand the 'Use when...' clause with concrete trigger phrases users would actually say (e.g., 'when the user asks to create ScopeMaster projects, analyze requirements, or manage users').

Add natural synonyms or feature names (e.g., 'requirements', 'user stories', 'scopes') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and two entities ('Manage Organizations, Users') but the verb 'Manage' is generic with no concrete action, matching anchor 2 rather than 3 which requires a concrete action like 'extracts content'.	2 / 5
Completeness	It states both what ('Manage Organizations, Users') and an explicit when ('Use when the user wants to interact with ScopeMaster data'), matching anchor 4; not 5 because the 'what' is thin and the when-trigger is broad rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes relevant natural terms ('ScopeMaster', 'Organizations', 'Users', 'interact with ScopeMaster data') but coverage is limited with no synonyms or variations, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	'ScopeMaster' is a specific named product giving a distinct niche, but the generic 'Manage Organizations, Users' creates minor overlap risk with other user-management skills, fitting anchor 4 rather than 5.	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/scopemaster/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.