Name: surveybot
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

surveybot

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

Quality

70%

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

Quality

Content

78%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 copy-paste commands and a solid polling workflow, but it carries minor prose padding and is a single long file with no progressive disclosure to reference materials. Trimming the intro and splitting detailed references would raise the weaker dimensions.

Suggestions

Cut the opening "Surveybot is a platform..." marketing paragraph; assume Claude knows what a survey platform is.

Move the proxy flag table and the connection state-machine detail into a separate reference file (e.g. references/proxy.md) and link to it from the body to enable progressive disclosure.

Number the end-to-end flow explicitly (1. Install, 2. Authenticate, 3. Connect, 4. Poll until READY, 5. Search/run actions) and label the currently dangling "Step 2" reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, but it opens with unnecessary product explanation ("Surveybot is a platform that allows users to create and distribute surveys. It's used by researchers, marketers, and businesses...") and some marketing prose that could be trimmed, fitting the efficient-with-minor-over-explanation anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure, polling, action list/run with JSON input, proxy) plus a complete proxy flag table, with no real gaps.	5 / 5
Workflow Clarity	A clear install → auth → connect → poll → run sequence exists with a polling state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and retry-after-action recovery, but step numbering is loose ("Step 2" is referenced yet unlabeled) and not presented as a crisp checklist.	4 / 5
Progressive Disclosure	No bundle files exist and the entire ~120-line guide lives in one file with good headers, but content that could be split out (the proxy flag table, the detailed connection state machine) is inlined and there are no references to deeper material, matching the some-structure-but-could-be-better-organized anchor.	3 / 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 cleanly answers both what and when and ties to a distinctive named platform, but its action verbs are generic and its trigger vocabulary is narrow. Expanding concrete actions and natural synonyms would lift the weaker dimensions.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create and distribute surveys, manage respondents and responses."

Broaden trigger terms with natural synonyms users say, e.g. add "polls, questionnaires, responses, feedback" to the Use-when clause.

Make the when-clause list concrete triggers (e.g. "Use when the user wants to create surveys, collect responses, or manage Surveybot users") rather than the generic "interact with Surveybot data".

Dimension	Reasoning	Score
Specificity	"Manage Surveys, Users" names the Surveybot domain plus two entity types to act on, but the verb "Manage" is generic and only 1-2 actions are given, matching the anchor for domain + 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both what it does ("Surveybot integration. Manage Surveys, Users.") and when to use it ("Use when the user wants to interact with Surveybot data"), but the when-clause is generic rather than enumerating concrete trigger phrases, so it falls just short of a 5.	4 / 5
Trigger Term Quality	Keywords like "Surveybot", "Surveys", and "Users" plus the trigger "interact with Surveybot data" are relevant, but common synonyms users might say (polls, questionnaires, responses, feedback) are missing, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	"Surveybot" is a specific named platform giving it a clear niche with low conflict risk, but the "Surveys, Users" triggers are generic enough to risk minor overlap with other survey or user-management skills, keeping it below a 5.	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/surveybot/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.