Name: simplesat
Rating: 56.8 (1 reviews)
Author: membranedev

simplesat

Simplesat integration. Manage Surveys, Users, Teams, Integrations. Use when the user wants to interact with Simplesat data.

Quality

65%

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

Quality

Content

67%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 well-organized, highly actionable CLI integration guide with a genuine polling/validation feedback loop for connection readiness. Its main weaknesses are mild marketing padding in the intro and inconsistent step numbering that muddies the workflow structure.

Suggestions

Trim the introductory marketing sentence ("It's used by customer support, product, and marketing teams to improve customer experience and drive business growth") and the "so you can focus on the integration logic rather than auth plumbing" aside.

Make the workflow numbering explicit and consistent: label "Step 1: Install & authenticate", "Step 2: Connect", "Step 3: Discover actions", "Step 4: Run or proxy", replacing the dangling "Step 2" references and lone "1b" heading.

Consider moving the detailed CLIENT_ACTION_REQUIRED state reference and the proxy flag options table into a separate reference file linked from SKILL.md to reduce inline bulk and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Most of the body is concrete commands, but the intro paragraph ("helps businesses collect and analyze... improve customer experience and drive business growth") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding, fitting the 3 anchor of mostly efficient with some over-explanation.	3 / 5
Actionability	It provides copy-paste-ready commands for every phase (install, login, connection ensure, action list/run, request) with flags and a proxy options table, but uses unfilled placeholders (CONNECTION_ID, <actionId>) and leaves a few common cases implicit, matching the 4 anchor.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence has a real feedback loop (poll until READY; handle CLIENT_ACTION_REQUIRED then re-poll), but the step numbering is inconsistent (references to "Step 2" without a matching heading, a lone "1b" subsection), keeping it at 4 rather than 5.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear headed sections covering overview, setup, actions, proxy, and best practices; the detailed client-action states and proxy options table are operational enough to live inline, placing it at 4 though it is over 50 lines and somewhat monolithic.	4 / 5
	Total	15 / 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 answers both what and when with an explicit trigger and a distinct brand anchor, but its actions are generic ("Manage") and the when clause lacks concrete trigger variations. Tightening the verb variety and adding natural synonyms would push it toward the top anchors.

Suggestions

Replace the single verb "Manage" with several distinct concrete actions (e.g., "Create and send surveys, view results, manage users and teams, configure integrations").

Expand the "Use when" clause with concrete user phrases such as "when the user mentions Simplesat, customer feedback, CSAT, or survey responses".

Add natural synonyms/variants (feedback, CSAT, questionnaire) alongside "Surveys" to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (Simplesat) and lists concrete entities (Surveys, Users, Teams, Integrations) but relies on a single generic verb ("Manage") rather than enumerating distinct actions, so it sits at the 3 anchor with only minimal action variety.	3 / 5
Completeness	It states both the what ("Manage Surveys, Users, Teams, Integrations") and an explicit when ("Use when the user wants to interact with Simplesat data"), but the when clause is generic and could be more specific, matching the 4 anchor rather than 5.	4 / 5
Trigger Term Quality	It includes the strong brand keyword "Simplesat" plus a natural phrase ("wants to interact with Simplesat data") and entity names, but misses common synonyms/variations a user might say (e.g., "feedback," "CSAT," "survey responses"), so it fits the 3 anchor.	3 / 5
Distinctiveness Conflict Risk	Being tied to the named platform "Simplesat" gives it a clear niche with low conflict risk, though it could still overlap with generic survey/feedback skills, placing it at 4 rather than 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/simplesat/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.