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

uservoice

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

Quality

62%

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

Quality

Content

67%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 a solid, mostly executable guide to driving UserVoice through the Membrane CLI with good validation checkpoints in the connection flow. Its main weaknesses are redundancy in the action-discovery sections and minor gaps in concrete UserVoice-specific examples and result validation.

Suggestions

Collapse the duplicate action-list instructions in 'Searching for actions' and 'Popular actions' into a single section to remove redundancy.

Replace the generic proxy example '/path/to/endpoint' with a concrete UserVoice API endpoint (e.g. '/api/v1/suggestions') so the proxy section is immediately actionable.

Add a brief result/error-handling note after 'Running actions' (e.g. checking the 'output' field and interpreting error responses) to close the validation gap in the run step.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but it includes redundant action-discovery instructions (the 'Searching for actions' and 'Popular actions' sections repeat the same list command), a purposeless Overview bullet list, and filler like 'Use action names and parameters as needed.' that could be trimmed.	3 / 5
Actionability	Concrete, copy-pasteable commands cover install, login, connection ensure/get, action list/run, and proxy requests, but minor gaps remain: placeholders (CONNECTION_ID) without resolution guidance and a generic '/path/to/endpoint' proxy example rather than a real UserVoice endpoint.	4 / 5
Workflow Clarity	The connect flow has a clear sequence with explicit state-based validation checkpoints and a re-poll feedback loop for CLIENT_ACTION_REQUIRED, but later steps (running actions) lack result/error validation and the 'Step 2' reference has no matching numbered 'Step 1'.	4 / 5
Progressive Disclosure	The single-file skill is well-organized into clear sections (Overview, Working with UserVoice, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices), but it is over 50 lines with no external references, so some inline material like the proxy flags table could arguably live in a reference file.	4 / 5
	Total	15 / 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 identifies UserVoice and includes a 'Use when' trigger, satisfying the basic what/when contract. Its weaknesses are generic, non-concrete action verbs and thin keyword coverage that misses the natural terms users say about UserVoice.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete UserVoice capabilities such as 'submit and vote on ideas, manage forums and articles, and respond to product feedback'.

Broaden trigger terms to include natural synonyms users say, e.g. 'Use when working with UserVoice feedback, ideas, suggestions, forums, or votes'.

Make the 'when' clause more specific by tying it to the actual entities and workflows (suggestions, comments, articles, users) instead of the generic 'interact with UserVoice data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('UserVoice integration') but its actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete UserVoice capabilities like submitting ideas, voting, or tracking feedback.	2 / 5
Completeness	It states both what the skill does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with UserVoice data'), though the 'when' trigger is generic and could be more specific.	4 / 5
Trigger Term Quality	'UserVoice' is a relevant natural keyword, but the description omits common variations and synonyms a user would actually say such as 'feedback', 'ideas', 'suggestions', 'votes', or 'forums'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product UserVoice gives it a clear niche with minimal conflict risk, though the generic 'manage data and automate workflows' phrasing could lightly overlap with other 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/uservoice/SKILL.md
Commit: f484c82

Reviewed: 3 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.