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

Blog Docs Log in Get started

rev

Rev integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Rev data.

Quality

63%

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

Quality

Content

63%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 strong, executable integration guide with a clear connection state machine and feedback loops, but it is held back by duplicated commands, light filler, and a fully monolithic structure with no progressive disclosure.

Suggestions

De-duplicate the `membrane action list` command and remove the empty "When to use which actions" filler line.

Move the detailed connection state-machine and proxy flag table into a reference file (e.g. REFERENCE.md) with clearly signaled links from the body.

Tighten the opening "Rev is a service..." preamble or move it to a one-line context note, since Claude can infer Rev's purpose from the linked docs.

Dimension	Reasoning	Score
Conciseness	Mostly concrete commands, but it repeats the action-list command ("Searching for actions" and "Popular actions"), includes filler like "When to use which actions: Use action names and parameters as needed.", and spends lines describing what Rev is.	3 / 5
Actionability	It provides concrete executable commands throughout (connection ensure, action list/run with flags, request proxy with a full flag table), with only placeholder gaps like <actionId> and CONNECTION_ID that are expected.	4 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but the step numbering is loose ("1b", an unlabeled "Step 2") which leaves minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline in one file with no external references; sections are reasonably organized, but detailed material like the state-machine handling and proxy flag table could be split into one-level-deep reference files.	3 / 5
	Total	14 / 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 covers what and when with a clear trigger clause, but relies on one generic verb and omits transcription/captioning keywords that would sharpen both specificity and trigger quality.

Suggestions

Replace the generic "Manage" with concrete verbs per entity (e.g. "Create and update Organizations, invite Users, set Goals, configure Filters").

Add transcription/captioning trigger terms (e.g. "Use when the user wants to transcribe or caption audio/video via Rev").

Reveal Rev's purpose in one phrase so the trigger is distinct from other 'Rev'-named or generic data-management skills.

Dimension	Reasoning	Score
Specificity	It names the domain ("Rev integration") and lists several specific entities ("Organizations, Users, Goals, Filters"), but the only action verb is the generic "Manage", so concrete actions are minimal rather than comprehensive.	3 / 5
Completeness	It states both a clear "what" ("Manage Organizations, Users, Goals, Filters") and an explicit "when" ("Use when the user wants to interact with Rev data"), matching the anchor that has both but a 'when' that could be more specific.	4 / 5
Trigger Term Quality	"Rev" and "Rev data" are natural terms, but the description omits what Rev actually does (transcription, captioning, audio/video), so it misses the common synonyms and task words a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	"Rev integration" pins a clear niche with low conflict risk, but the generic entity list (Organizations, Users, Goals) and absence of the service's purpose leave minor overlap risk with similarly named integrations.	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/rev/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.