Name: surveysparrow
Rating: 62.4 (1 reviews)
Author: membranedev

surveysparrow

SurveySparrow integration. Manage Surveys, Contacts, Responses, Reports, Users, Workspaces. Use when the user wants to interact with SurveySparrow data.

Quality

73%

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/surveysparrow/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.

A highly actionable skill body with copy-paste commands and a well-validated connection workflow. It loses points for an unnecessary marketing intro, repeated command examples, and the absence of validation guidance around destructive proxy requests.

Suggestions

Trim the opening 'SurveySparrow is an omnichannel experience management platform...' paragraph and deduplicate the `action list` command that appears in Searching, Popular actions, and Best practices.

Add a validation/verification checkpoint before destructive proxy or action calls (e.g., confirm the HTTP method and target with the user before running DELETE/PUT, or dry-run where supported) to lift the destructive-operation workflow cap.

Consider moving the proxy-flags table and clientAction state-machine details into a separate reference file referenced one level deep, to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening marketing paragraph explaining what SurveySparrow is and the repeated `action list` command across three sections add noticeable padding Claude does not need.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common flow end-to-end (install, login, connection ensure/get, action list, action run with JSON input, request proxy) plus a concrete proxy-flags table.	5 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state validation and a poll-after-user-action feedback loop, but proxy requests support destructive methods (DELETE/PUT) with no validation or verification guidance, capping this dimension at 3.	3 / 5
Progressive Disclosure	There are no bundle files and the skill is self-contained with clear, well-organized section headers; it is held below 5 because ~130 lines (proxy flag table, clientAction state machine) are all inline with no split reference material.	4 / 5
	Total	15 / 20 Passed

Description

78%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.

A solid, third-person description that names the platform and its concrete domain entities with an explicit 'Use when' clause. It is held below top marks by the generic 'Manage' verb and a single, broad trigger phrase rather than multiple concrete trigger terms.

Suggestions

Replace the single generic verb 'Manage' with a few distinct concrete actions (e.g., 'Create and distribute surveys, fetch responses, manage contacts and lists') to reach comprehensive specificity.

Expand the 'Use when' clause with concrete trigger phrases (e.g., 'Use when the user mentions SurveySparrow, wants to fetch survey responses, or manage contacts') to add natural synonym coverage.

Dimension	Reasoning	Score
Specificity	Enumerates concrete entities (Surveys, Contacts, Responses, Reports, Users, Workspaces) but relies on a single generic verb (Manage) rather than listing multiple distinct concrete actions, so it sits below the comprehensive anchor 5.	4 / 5
Completeness	Both the 'what' (manage the listed entities) and an explicit 'Use when' clause are present; the trigger is single and somewhat generic ('interact with SurveySparrow data') rather than multiple concrete trigger phrases, so it is below the anchor 5.	4 / 5
Trigger Term Quality	Natural entity names a user would say (surveys, contacts, responses, reports) are present, but there are no synonyms or variations beyond the single brand and entity list, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	SurveySparrow is a named SaaS platform with a distinct brand trigger and entity scope, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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/surveysparrow/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.