Name: ro-innovation
Rating: 59.2 (1 reviews)
Author: membranedev

ro-innovation

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

Quality

68%

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/ro-innovation/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 body is actionable and well-structured with concrete CLI commands and a clear connection state-machine. Minor issues are inconsistent step numbering, light over-explanation in the intro, and the absence of explicit recovery feedback loops.

Suggestions

Fix the step numbering so references like 'Step 2' and '1b' map to actual numbered steps.

Trim the opening platform description and auth-plumbing commentary since they restate concepts Claude can infer.

Add an explicit validate/fix/retry loop for connection errors (e.g., on CONFIGURATION_ERROR, surface the error field, correct, and re-run connection ensure).

Dimension	Reasoning	Score
Conciseness	Largely efficient with concrete commands and minimal padding, though the opening platform explainer and a few phrases like 'so you can focus on the integration logic rather than auth plumbing' are mild over-explanation that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands for install, auth, connection, action discovery/running, and proxy requests with a useful flag table, with only minor gaps like unfilled placeholders that are expected.	4 / 5
Workflow Clarity	Clear connection-setup sequence with a state-machine and polling checkpoint, but step numbering is inconsistent (references 'Step 2' with no Step 1, a '1b' with no 1a) and recovery feedback loops are only partially explicit.	4 / 5
Progressive Disclosure	A single self-contained file with well-organized sections and clear navigation; no bundle files exist or are needed, though the body is somewhat long for a single-file overview.	4 / 5
	Total	16 / 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 clearly identifies the integration and provides both a what and a when, with reasonable distinctiveness from the named app. It is held back by generic action phrasing and limited trigger-term coverage rather than specific capabilities like Ideas or Users.

Suggestions

Add concrete capabilities from the body (e.g., 'browse Ideas and Users') instead of the generic 'manage data, records, and automate workflows'.

Expand the Use-when clause with natural trigger phrases users would say, such as 'when the user mentions Ro Innovation, sales content, or Ideas'.

Use third-person concrete verbs tied to the platform's entities to improve specificity and reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of generic actions ("Manage data, records, and automate workflows") but lacks specific concrete capabilities from the body like Ideas or Users, so it is not comprehensive enough for a 4.	3 / 5
Completeness	Clearly states what it does and includes an explicit "Use when the user wants to interact with Ro Innovation data" trigger, though the when-clause could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Ro Innovation data", "Ro Innovation") but misses common user variations or synonyms such as "sales content" or "ideas," matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tied to a named app (Ro Innovation) giving it a distinct niche with minimal conflict risk, though the generic "data, records" framing leaves minor overlap with other data 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/ro-innovation/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.