Name: questionpro
Rating: 59.2 (1 reviews)
Author: membranedev

questionpro

QuestionPro integration. Manage Surveys, Reports, Users, Groups. Use when the user wants to interact with QuestionPro 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/questionpro/SKILL.md

Quality

Content

70%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 skill body is highly actionable with copy-paste-ready Membrane CLI commands and a clear proxy escape hatch, but it is held back by mild verbosity (a marketing-style platform explainer and a duplicated action-list command) and by inconsistent workflow numbering plus absent validation checkpoints for state-changing operations. No bundle files exist, so progressive disclosure is judged on the in-body structure alone.

Suggestions

Remove or condense the opening paragraph explaining what QuestionPro is and who uses it; Claude already knows this and it competes for context.

De-duplicate the action-list command (it appears in both 'Searching for actions' and 'Popular actions') and fix the step numbering so 'Step 2' has an explicit Step 1.

Add explicit validation checkpoints and a feedback loop for state-changing operations, e.g. after `membrane action run` or proxy POST/PUT/DELETE, instruct Claude to check the `output`/error field and retry or surface `clientAction` guidance on failure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-focused, but it includes content Claude already knows (a paragraph explaining what QuestionPro is and who uses it) and restates the same action-list command twice in 'Searching for actions' and 'Popular actions', fitting the score-3 anchor of mostly efficient with some unnecessary explanation that could be tightened.	3 / 5
Actionability	The body provides copy-paste-ready, fully executable commands for install, login, connection ensure/get with --wait, action list/run with --input, and proxy requests with a complete flag table, covering the common cases exactly as the score-5 anchor describes.	5 / 5
Workflow Clarity	It sequences connection setup, waiting on BUILDING state, and branching on state outcomes, but the numbering is inconsistent ('Step 2' referenced without a numbered Step 1, a '1b' subsection) and there are no validation/checkpoint steps for destructive or batch operations such as action runs or proxy POST/PUT/DELETE, which caps the score at 3 per the rubric's destructive-operation guidance.	3 / 5
Progressive Disclosure	The body is well-sectioned (Overview, Install, Authentication, Connecting, Searching actions, Running actions, Proxy, Best practices) with no bundle files to split content into, so content stays appropriately inline; it is not a 5 because there are no separate reference files, yet it is not a 3 since organization is clear, placing it at the score-4 level of good structure with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

67%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 is clear and brand-specific, explicitly pairing a concise statement of capabilities with a 'Use when' trigger, which makes it distinctive and largely complete. Its main weakness is trigger-term breadth: it omits natural synonyms (polls, questionnaires, quizzes) that users would commonly say and that the body itself references.

Suggestions

Broaden trigger terms to include natural synonyms a user would say, e.g. 'Use when the user wants to create or analyze surveys, polls, questionnaires, quizzes, or manage QuestionPro contacts and reports.'

Replace generic 'Manage' verbs with more concrete actions (e.g. 'Create and distribute surveys, pull response reports, manage contacts and email lists') to lift specificity from 4 toward 5.

Keep the existing third-person voice and brevity; do not pad with platform marketing language.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete actions ('Manage Surveys, Reports, Users, Groups'), matching the score-4 anchor of listing several specific actions with minor gaps; it falls short of 5 because the actions are generic 'manage' verbs without finer-grained operations.	4 / 5
Completeness	It clearly answers 'what' ('Manage Surveys, Reports, Users, Groups') and provides an explicit 'when' clause ('Use when the user wants to interact with QuestionPro data'), matching the score-4 anchor where both what and when are present but the when could be more specific about concrete triggering situations.	4 / 5
Trigger Term Quality	It surfaces natural terms like 'Surveys', 'Reports', 'Users', and 'Groups' plus the explicit trigger 'Use when the user wants to interact with QuestionPro data', but it misses common synonyms/variations users might say (e.g. 'polls', 'questionnaires', 'quiz') that the body even mentions, fitting the score-3 anchor of some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The QuestionPro brand name plus its specific survey/report/user/group domain carves a clear niche with distinct triggers and minimal overlap with other skills, matching the score-5 anchor of a clear niche with distinct triggers.	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/questionpro/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.