Name: roll
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

roll

Roll integration. Manage Organizations. Use when the user wants to interact with Roll 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/roll/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 delivers a concrete, executable Membrane CLI workflow with genuine validation feedback loops for connection setup. Its main weaknesses are prose padding in the intro and a serious internal inconsistency conflating the payroll product RollHQ with the tabletop product Roll20.

Suggestions

Trim the intro background paragraph and 'Think of it as a modern payroll solution' prose; Claude does not need Roll explained and the commands carry the content.

Resolve the Roll20/RollHQ confusion: the 'Roll Overview' lists Dice/Rolls and cites roll20.zendesk.com while the rest of the skill targets the payroll product at rollhq.com — pick one product and make the overview, docs link, and examples consistent.

Merge the redundant 'Popular actions' section into 'Searching for actions' and give the workflow explicit top-level numbered steps (1, 2, 3) instead of '1b' and an undefined 'Step 2'.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the intro paragraph over-explains what Roll is ('Think of it as a modern payroll solution...'), and several prose asides ('so you can focus on the integration logic', 'This is the fastest way to get a connection') pad beyond what Claude needs, fitting 'mostly efficient but includes some unnecessary explanation' at 3.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run with --input JSON, request with a full flag table), covering the common cases with only minor gaps like unresolved placeholders (CONNECTION_ID, actionId) and the vague 'Use action names and parameters as needed', placing it at 4 rather than fully-copy-paste at 5.	4 / 5
Workflow Clarity	The connection flow has explicit validation checkpoints and a feedback loop (poll until not BUILDING, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), but step numbering is loose ('1b', references to an undefined 'Step 2') and the roll20/rollhq inconsistency muddies the path, so it sits at 4 rather than the checklist-grade anchor at 5.	4 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and no nested references, and the CLI-guide content is appropriately kept inline; minor organization gaps (the contradictory Dice/Rolls overview, and 'Popular actions' duplicating 'Searching for actions') keep it at 4 rather than 5.	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 includes an explicit Use-when trigger and names a concrete action, but it is thin on capability breadth and natural trigger variations. It is functional and distinct but not comprehensive.

Suggestions

List 2-3 more concrete actions beyond 'Manage Organizations' (e.g., run payroll, manage employees, handle tax filings) to lift specificity toward the several-actions anchor.

Expand the Use-when clause with natural trigger phrases and synonyms users would actually say (e.g., 'Use when the user asks about payroll, employee payments, or managing Roll organizations').

Dimension	Reasoning	Score
Specificity	It names the domain ('Roll integration') plus one concrete action ('Manage Organizations'), but 'interact with Roll data' is generic and coverage is not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	It has both a 'what' ('Manage Organizations' / 'Roll integration') and an explicit 'when' ('Use when the user wants to interact with Roll data'), but the 'when' is generic and the 'what' is thin, so it sits at 4 rather than the fully-concrete-trigger anchor at 5; the explicit Use-when clause keeps it above 3.	4 / 5
Trigger Term Quality	'Roll', 'Organizations', and 'Roll data' are relevant keywords, but it lacks common variations, synonyms, or entity names beyond the single proper noun, fitting 'some relevant keywords but missing common variations' at 3 rather than the broader coverage at 4.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Roll' gives a clear niche with low conflict risk, but the trigger 'interact with Roll data' is generic enough to leave minor overlap risk, matching 'mostly distinct; minor overlap risk' at 4 rather than the minimal-risk 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/roll/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.