Name: reviewstudio
Rating: 52.8 (1 reviews)
Author: membranedev

reviewstudio

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

Quality

59%

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

Quality

Content

61%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, actionable Membrane CLI guide with good command coverage and a connection-state polling loop, but it carries some filler prose and omits validation/verification steps after action runs and proxy requests.

Suggestions

Add a validation step after running actions or proxy requests (e.g. check the `output`/response status and confirm the expected change) to support destructive and batch operations.

Trim editorial prose like "so you can focus on the integration logic rather than auth plumbing" and the token-burn/marketing framing in Best practices.

Include one fully worked end-to-end example with concrete values (a sample action id and input) so Claude can copy-paste without substituting every placeholder.

Dimension	Reasoning	Score
Conciseness	It is mostly commands and a lean flag table, but includes unnecessary prose such as "so you can focus on the integration logic rather than auth plumbing" and marketing-leaning best-practice lines that could be trimmed.	3 / 5
Actionability	It provides concrete, executable membrane commands for install, login, connection ensure/get, action list/run, and proxy requests with a full flag table; gaps are only the placeholder substitutions and lack of a fully worked end-to-end example.	4 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear and the connection-state polling loop is a real checkpoint, but running actions and proxy requests (including PUT/DELETE) lack post-action validation, capping destructive/batch workflows at 3.	3 / 5
Progressive Disclosure	The single ~140-line SKILL.md is well organized with clear section headers and one external link, with content appropriately placed; it earns 4 rather than 5 because the skill exceeds 50 lines with no offloaded reference files.	4 / 5
	Total	14 / 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 correctly pairs a what and a when and is anchored to a specific product, but its actions are generic buzzwords and it relies on the product name as the sole trigger, missing natural domain terms.

Suggestions

Replace generic verbs with concrete Review Studio actions, e.g. "Review and approve designs, videos, and documents; add annotations and manage proofing workflows."

Add natural trigger phrases and synonyms users say, such as "proofing," "annotations," "approvals," or "Review Studio comments."

Tighten the "Use when" clause to reference the actual scenarios, e.g. "Use when the user wants to review, annotate, or approve creative assets in Review Studio."

Dimension	Reasoning	Score
Specificity	It names the domain ("Review Studio") and a few action areas, but "Manage data, records, and automate workflows" are generic abstractions rather than concrete Review Studio actions like proofing, annotating, or approving.	2 / 5
Completeness	It states both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Review Studio data"), though the trigger clause is generic.	4 / 5
Trigger Term Quality	The only real keyword is the product name "Review Studio" repeated as the trigger; it lacks natural variations or domain synonyms (proof, annotation, approval) users would actually say.	3 / 5
Distinctiveness Conflict Risk	Being tied to a specific named product gives it a clear niche with minimal conflict risk, but the generic "interact with data" phrasing leaves minor overlap with other data-integration skills.	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/reviewstudio/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.