Name: surveymethods
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

surveymethods

SurveyMethods integration. Manage Surveys, Responses, Users. Use when the user wants to interact with SurveyMethods 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/surveymethods/SKILL.md

Quality

Content

61%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 largely actionable CLI integration guide with good command coverage and a sensible connection-state workflow. Its weaknesses are some unnecessary background prose, a broken 'Step 2' reference, and the absence of validation guidance for destructive proxy/action calls.

Suggestions

Remove the introductory paragraph explaining what SurveyMethods is and who uses it; Claude does not need this background.

Add an explicit validation/checkpoint step before destructive proxy requests (e.g. confirm the method is DELETE/PUT and show the affected resource before running), and resolve the orphaned 'Step 2' reference.

Add one or two concrete worked examples for common actions (e.g. listing surveys, retrieving responses) with real-shaped JSON inputs so the guidance is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Most of the body is useful CLI reference, but the opening paragraph explaining what SurveyMethods is and who uses it, plus the thin 'SurveyMethods Overview' bullet list, are background Claude does not need and could be trimmed.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) with a useful flag table, but common-case examples (e.g. listing surveys, fetching responses) are not shown with real inputs, leaving minor gaps.	4 / 5
Workflow Clarity	The connection flow is sequenced with state checks and a poll loop, but it references an undefined 'Step 2', and destructive operations via `membrane request` (DELETE/PUT) and `membrane action run` lack explicit validation checkpoints, which caps this at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested/deep references and all content appropriately inline for a single-file skill, though there is no external reference split and minor gaps like the orphaned 'Step 2' and overlapping 'Popular actions'/'Searching for actions' sections.	4 / 5
	Total	14 / 20 Passed

Description

66%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 niche and provides an explicit 'Use when' trigger, but its action vocabulary is generic ('Manage') and it lacks natural synonyms users might say. It is solid but could be sharpened with concrete verbs and trigger terms.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create and distribute surveys, collect responses, and manage contacts and email campaigns.'

Expand the 'Use when' clause with natural trigger phrases users would actually say, e.g. 'Use when the user wants to send surveys, collect responses, or manage SurveyMethods contacts.'

Add common synonyms like 'polls', 'questionnaires', or 'feedback' so the description matches natural user language.

Dimension	Reasoning	Score
Specificity	Names the domain ('SurveyMethods') and enumerates concrete entities ('Manage Surveys, Responses, Users'), but the only verb is the generic 'Manage' with no concrete actions like create, analyze, or export, so it sits between anchors 2 and 3.	3 / 5
Completeness	Has both a clear 'what' (manage Surveys, Responses, Users) and an explicit 'when' ('Use when the user wants to interact with SurveyMethods data'), but the 'when' is generic rather than listing concrete trigger phrases, so it does not reach anchor 5.	4 / 5
Trigger Term Quality	Includes the brand 'SurveyMethods' and entity nouns 'Surveys, Responses, Users', but misses common natural synonyms users would say (polls, questionnaires, feedback) and the trigger 'interact with SurveyMethods data' is generic.	3 / 5
Distinctiveness Conflict Risk	The SurveyMethods brand name gives it a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/surveymethods/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.