Name: jamroom
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

jamroom

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

Quality

66%

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

Quality

Content

71%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 highly actionable with copy-paste-ready Membrane CLI commands and a well-handled connection state machine, but it is padded by a long generic module enumeration and does not progressively disclose its reference material into separate files. Step numbering in the workflow is slightly broken.

Suggestions

Move the ~70-item module catalog into a references/ file (e.g. MODULES.md) and keep only a one-line pointer in SKILL.md to cut the bulk of the padding.

Fix the workflow numbering: add a labeled 'Step 1' / 'Step 2' (or 'Searching for actions' / 'Running actions') so 'skip to Step 2' and '1b' resolve to real headings.

Add an explicit validation/check step after `membrane action run` (e.g. inspect the `output` field and handle errors) so the run workflow has a feedback loop matching the connection flow.

Dimension	Reasoning	Score
Conciseness	The actionable sections (install, login, connection, search, run, proxy) are efficient, but the ~70-item module enumeration of repeated 'Get X' bullets and filler like 'Use action names and parameters as needed.' add noticeable padding, matching 'mostly efficient but includes some unnecessary explanation or could be tightened'; not a 2 because the command sections are genuinely lean, not a 4 because the module list is heavy.	3 / 5
Actionability	It provides copy-paste-ready commands with real flags and JSON examples across the full flow (npm install, membrane login, connection ensure, action list/run, request proxy), matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'; not a 4 because coverage is comprehensive rather than having minor gaps.	5 / 5
Workflow Clarity	The connection workflow has an explicit state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with polling and recovery loops, matching 'clear sequence with most checkpoints present; minor validation gaps'; not a 5 because step numbering is broken ('skip to Step 2' with no labeled Step 2, a '1b' with no '1a') and there is no validation checkpoint after running actions.	4 / 5
Progressive Disclosure	No bundle files exist and everything is inlined into one long SKILL.md, including a large module catalog and a proxy-flag reference table that would suit separate files, matching 'some structure but could be better organized; content that should be separate is inline'; not a 4 because there are no external references at all and the simple-skill exception does not apply to this long skill, not a 2 because section headings do provide real structure.	3 / 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 cleanly answers both what and when in third person with a clear platform-specific trigger, but its action verbs are generic rather than concrete Jamroom operations and it lacks trigger-term synonyms. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete Jamroom-specific actions (e.g., 'manage profiles, users, marketplace modules, themes, and content') drawn from the body's module list.

Broaden the trigger phrase with natural synonyms, e.g. 'Use when the user wants to manage Jamroom profiles, users, modules, themes, or content.'

Tighten the 'what' so it reads as distinct capabilities rather than 'manage data, records, and automate workflows', which overlaps with generic data skills.

Dimension	Reasoning	Score
Specificity	Names the Jamroom domain plus a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete Jamroom-specific operations, fitting 'names domain and 1-2 concrete actions but not comprehensive'; not a 2 because it lists multiple actions, not a 4 because none are specific.	3 / 5
Completeness	It states what ('Jamroom integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Jamroom data.'), matching 'has both what and when; when could be more explicit'; not a 5 because the 'what' is generic and the 'when' offers only a single trigger phrase rather than concrete varied triggers.	4 / 5
Trigger Term Quality	The trigger 'interact with Jamroom data' plus 'Jamroom', 'data', 'records', 'workflows' gives some relevant keywords but misses common synonyms or variations, matching 'some relevant keywords but missing common variations'; not a 4 because natural-term coverage is thin beyond the platform name.	3 / 5
Distinctiveness Conflict Risk	Jamroom is a specific platform niche with a distinct trigger ('interact with Jamroom data'), giving 'mostly distinct; minor overlap risk'; not a 5 because the generic verbs ('manage data, records, automate workflows') could overlap with other data-management 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/jamroom/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.