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

usersketch

UserSketch integration. Manage data, records, and automate workflows. Use when the user wants to interact with UserSketch 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/usersketch/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 provides strong executable guidance and a well-sequenced connection workflow with feedback loops, but it is padded with a conceptual intro and vague overview filler, and its step numbering is inconsistent.

Suggestions

Trim the opening 'what UserSketch is' paragraph and the 'UserSketch Overview — Use action names and parameters as needed' filler to assume Claude's competence and save tokens.

Fix the step numbering: label the 'Searching for actions' section as 'Step 2' (or remove the dangling 'Step 2' references) and renumber '1b' so the sequence is unambiguous.

Turn the 'Popular actions' section into 2-3 concrete UserSketch action examples instead of just restating the discovery command, to lift actionability toward fully copy-paste-ready coverage.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what UserSketch is ('user research platform... used by UX researchers, product managers...') and the vague 'UserSketch Overview — Use action names and parameters as needed' filler add unnecessary padding, fitting 'Mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete, copy-paste-ready commands are given throughout (install, login, connection ensure, action run, proxy with a full flags table), with only minor gaps such as the 'Popular actions' section merely instructing discovery rather than showing UserSketch-specific examples, matching 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-until-ready → search → run sequence is clear with an explicit state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-polling after action), but step labels are inconsistent ('Step 2' is referenced but never labeled, '1b' has no '1a'), leaving minor gaps per the 'Clear sequence with most checkpoints present' anchor.	4 / 5
Progressive Disclosure	No bundle files exist and the content is organized into clearly headed sections that read well as a single overview, though at ~140 lines some material (the proxy flags table, the detailed connection state machine) could be split out, fitting 'Good structure; most content is appropriately placed; minor organization gaps'.	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 covers both what the skill does and when to use it with a clear brand anchor, but its action language ('manage data, records, automate workflows') is generic and the trigger phrasing lacks concrete, varied keywords.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete UserSketch actions, e.g. 'pull user interview transcripts, search survey responses, and trigger research workflows'.

Expand the trigger clause with natural synonyms a user would say, e.g. 'Use when the user wants to query UserSketch feedback, search user research notes, or pull survey/interview data.'

Add file- or entity-style triggers (e.g. 'UserSketch records', 'UserSketch reports') to strengthen distinctiveness against other data-integration skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain and 2-3 actions, but the actions are generic ('manage data, records') rather than concrete, matching the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with UserSketch data') are present and explicit, though the 'when' clause is somewhat generic rather than listing concrete triggers — matching the 'Has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with UserSketch data' surfaces the brand keyword and 'data', but lacks common variations or synonyms a user might naturally say, fitting the 'Some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The brand name 'UserSketch' provides a distinct niche trigger with minimal conflict risk, though the generic 'manage data, records, automate workflows' actions create minor overlap with other data skills, fitting 'Mostly distinct; minor overlap risk'.	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/usersketch/SKILL.md
Commit: f484c82

Reviewed: 3 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.