Name: reviewsio
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

reviewsio

Reviews.io integration. Manage Reviews, Products, Companies. Use when the user wants to interact with Reviews.io data.

Quality

74%

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

Quality

Content

75%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 highly actionable with concrete, executable Membrane commands and a reasonably well-sequenced connection workflow, but it carries some unnecessary explanatory padding and an unresolved "Step 2" reference that slightly reduce conciseness and workflow clarity.

Suggestions

Trim the opening "Reviews.io is a platform for..." paragraph and explanatory asides (e.g. "This is the fastest way to get a connection...") since Claude can infer this context.

Fix the dangling "skip to Step 2" reference by labeling the action-discovery section as Step 2 or rewording to "skip to Searching for actions".

Consider moving the detailed clientAction state-machine handling into a references file (e.g. CONNECTION_STATES.md) with a one-line pointer, to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but the opening "Reviews.io is a platform for collecting and displaying customer reviews..." paragraph and explanatory asides like "This is the fastest way to get a connection. The URL is normalized..." are over-explanation Claude largely does not need, matching the anchor 3 (mostly efficient but includes some unnecessary explanation).	3 / 5
Actionability	It provides copy-paste-ready commands throughout — install, login, connection ensure, action list/run with --input JSON, and a proxy flag table — covering the common cases with fully executable examples, matching the anchor 5.	5 / 5
Workflow Clarity	There is a clear sequence (install → authenticate → connect → poll until ready → search → run) with state-based checkpoints and error recovery for BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, but the "skip to Step 2" reference points to no labeled Step 2, a minor validation/labeling gap keeping it at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), and the body is organized into clear logical sections (Overview, Authentication, Connecting, Searching, Actions, Proxy, Best practices); the content is well-structured with only minor organization gaps such as the detailed clientAction state machine being inlined rather than split out, fitting anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

73%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 states both purpose and trigger condition with a clear niche, but the action vocabulary is generic ("Manage") and the trigger phrasing is thin on concrete variations, capping it just below the top anchors.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Fetch and create product reviews, manage products and company profiles, send review invitations."

Expand the "Use when" clause with concrete trigger phrases and synonyms, e.g. "Use when the user wants to fetch reviews, manage products or companies, or send review invitations on Reviews.io."

Dimension	Reasoning	Score
Specificity	"Manage Reviews, Products, Companies" names the domain and enumerates three concrete entities, but the single verb "Manage" is generic rather than a set of specific actions, landing between the anchor 2 (minimal/generic actions) and anchor 3 (a concrete action or two).	3 / 5
Completeness	It answers both what ("Reviews.io integration. Manage Reviews, Products, Companies.") and when ("Use when the user wants to interact with Reviews.io data."), with the explicit "Use when" clause present; the "when" is slightly generic rather than enumerating concrete triggers, so it does not reach the anchor 5 example.	4 / 5
Trigger Term Quality	"Reviews, Products, Companies" plus "Reviews.io" and "interact with Reviews.io data" give good keyword coverage a user would naturally say, though a few synonyms or phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	"Reviews.io integration" is a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/reviewsio/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.