Name: surveymonkey
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

surveymonkey

SurveyMonkey integration. Manage Surveys, Users. Use when the user wants to interact with SurveyMonkey data.

Quality

67%

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

Quality

Content

68%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 highly actionable with concrete, copy-paste CLI commands and a well-organized structure, but it spends tokens explaining SurveyMonkey itself and, critically, offers no validation guidance for its destructive and batch operations. Tightening the intro and adding verification steps would lift its weakest dimensions.

Suggestions

Remove the SurveyMonkey definition intro (lines 17) and the "so you can focus on the integration logic rather than auth plumbing" padding to respect the token budget.

Add a verification step for destructive and batch actions, e.g. confirm the target id via a get/list call before running delete-survey or create-contacts-bulk, and check the response for success/failure counts afterward.

Fix the dangling "skip to Step 2" references (lines 70, 84) by labeling the next section as Step 2 or rewording to "skip to Searching for actions."

Dimension	Reasoning	Score
Conciseness	The body opens by explaining what SurveyMonkey is ("an online survey development cloud-based software... used by businesses of all sizes"), which Claude already knows, and includes mild fluff like "so you can focus on the integration logic rather than auth plumbing." The rest is mostly lean commands, so it fits anchor 3 (mostly efficient but some unnecessary explanation) rather than 4.	3 / 5
Actionability	It provides copy-paste-ready CLI commands with flags and a JSON-parameter example, covering install, auth, connection, action search, action run, and proxy requests. This matches anchor 5 (fully executable; copy-paste ready; specific examples cover common cases).	5 / 5
Workflow Clarity	The connection flow is sequenced with polling and state-based feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the skill exposes destructive actions (delete-survey, delete-webhook) and batch actions (create-contacts-bulk, get-responses-bulk) with no validation or verification steps, which per the rubric caps workflow clarity at 3. A dangling "skip to Step 2" reference (no Step 2 exists) further weakens the sequence.	3 / 5
Progressive Disclosure	No bundle files exist, and the single SKILL.md is organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices). The 20-row actions table is bulk that could live in a reference, but inlining it is reasonable for a CLI-wrapping skill, matching anchor 4 (good structure; minor organization gaps) rather than 5's explicit one-level-deep references.	4 / 5
	Total	15 / 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 cleanly answers both what and when and is anchored to a distinct brand niche, but its action vocabulary is generic ("manage") and its trigger terms lack the synonyms (responses, collectors, polls) users would naturally say. It is solid but not exemplary.

Suggestions

Replace the generic verb "Manage" with concrete operations, e.g. "Create and list surveys, collectors, and responses; manage contacts and webhooks."

Expand the "Use when" clause with concrete trigger phrases such as "Use when the user wants to create surveys, collect responses, or manage SurveyMonkey contacts and webhooks."

Add natural synonyms (responses, collectors, polls, webhooks) so the description surfaces for the full range of user requests.

Dimension	Reasoning	Score
Specificity	"Manage Surveys, Users" names the domain plus two concrete entity targets, but the verb "manage" is generic rather than enumerating specific operations like create, list, or delete. It sits at anchor 3 (1-2 concrete actions, not comprehensive) rather than 4 because coverage of the available actions is sparse.	3 / 5
Completeness	It states both what ("SurveyMonkey integration. Manage Surveys, Users.") and when ("Use when the user wants to interact with SurveyMonkey data"), matching anchor 4 (both what and when; when could be more explicit). It falls short of 5 because the "when" clause is generic and lacks concrete trigger phrases.	4 / 5
Trigger Term Quality	The phrase includes "SurveyMonkey", "Surveys", and "interact with SurveyMonkey data", which are relevant, but it misses common synonyms and concrete terms users say such as responses, collectors, polls, or webhooks. This matches anchor 3 (some relevant keywords, missing common variations) rather than 4's broader coverage.	3 / 5
Distinctiveness Conflict Risk	SurveyMonkey is a specific named brand with a clear niche, and the trigger is brand-anchored, so the risk of firing for an unrelated skill is minimal. This matches anchor 5 (clear niche with distinct triggers; minimal conflict risk).	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/surveymonkey/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.