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

survey2connect

Survey2Connect integration. Manage Users, Surveys, Respondents, Responses, Reports, Integrations. Use when the user wants to interact with Survey2Connect 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/survey2connect/SKILL.md

Quality

Content

75%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 an efficient, well-structured CLI integration guide with executable commands and a clear connection-state workflow including feedback loops. Its main gaps are the placeholder 'Popular actions' section and slightly inconsistent step numbering.

Dimension	Reasoning	Score
Conciseness	The body is dominated by tight, executable command blocks and a flag table; only minor lines are padded ('so you can focus on the integration logic rather than auth plumbing', the elaboration of who uses Survey2Connect), placing it just below the fully lean anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxy with a flags table, but the 'Popular actions' section only re-states the discovery command instead of naming concrete Survey2Connect actions, a minor gap keeping it below 5.	4 / 5
Workflow Clarity	The connect-to-ready flow has explicit state branching and feedback loops (poll until state changes, re-poll after user action, handle CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step numbering is inconsistent (a '1b' and 'Step 2' reference without a clearly numbered 1/2/3), leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	There are no bundle files and none are strictly needed; the single file is well-organized into clear sections (Overview, Working with, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with easy navigation, though at ~140 lines some detail (the clientAction state machine, flags table) could arguably live in a reference file.	4 / 5
	Total	16 / 20 Passed

Description

62%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 pairs a 'what' with an explicit 'Use when' trigger and anchors on a specific product, but its actions are bundled under a single generic verb 'Manage' and its trigger terms lack synonyms or natural variations.

Suggestions

Replace the generic 'Manage' with concrete verbs per resource (e.g. 'Create and invite respondents, collect and analyze survey responses, generate reports').

Expand the 'Use when' clause with natural trigger phrases users would say, e.g. 'Use when the user mentions Survey2Connect, sending a survey, collecting responses, or pulling survey reports.'

Add common synonyms/extensions (e.g. 'S2C', 'survey responses') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain and lists several resource categories ('Manage Users, Surveys, Respondents, Responses, Reports, Integrations'), but the only action verb is the generic 'Manage' rather than concrete verbs like extract/fill/merge, so it falls at the 'domain + items but not specific actions' level rather than 4.	3 / 5
Completeness	It explicitly answers both 'what' (manage the listed Survey2Connect resources) and 'when' ('Use when the user wants to interact with Survey2Connect data'), but the 'when' is generic ('interact with... data') rather than concrete trigger phrases, so it is above 3 but below 5.	4 / 5
Trigger Term Quality	The trigger relies almost entirely on the product name ('Survey2Connect data') with no synonyms or natural variations (e.g. 'surveys', 'S2C', 'respondents'), matching the 'some relevant keywords but missing common variations' anchor rather than the broad coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Anchoring on the specific named Survey2Connect platform gives it a clear niche with minimal conflict risk, but the generic resource list (Users, Surveys, Respondents) has minor overlap with general survey/CRM skills, so it is mostly distinct rather than fully so.	4 / 5
	Total	14 / 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/survey2connect/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.