Name: userleap
Rating: 55.2 (1 reviews)
Author: membranedev

userleap

UserLeap integration. Manage data, records, and automate workflows. Use when the user wants to interact with UserLeap data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/userleap/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 content is a well-structured, actionable CLI integration guide with executable commands and a sensible connection workflow with validation checkpoints. It is held back by an unnecessary product-explainer paragraph, vague filler, inconsistent step numbering, and a hollow 'Popular actions' section.

Suggestions

Trim the opening UserLeap explainer paragraph and the vague 'When to use which actions' filler line; assume Claude knows what a survey platform is.

Fix the step numbering — label 'Step 1'/'Step 2' consistently and resolve the dangling '1b' and 'skip to Step 2' references.

Either populate 'Popular actions' with concrete example actions (e.g. list surveys, send survey, fetch responses) or remove the empty section.

Dimension	Reasoning	Score
Conciseness	The bulk is lean, copy-paste CLI commands, but the opening paragraph explaining what UserLeap is and who uses it, plus the vague filler line 'When to use which actions: Use action names and parameters as needed.', are unnecessary explanation Claude does not need.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, action run, request) with a flags table, covering the common cases; the 'Popular actions' section is hollow since it only restates the discovery command rather than listing actions.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-check checkpoints and a poll-after-user-action feedback loop, but the step numbering is inconsistent — it references 'Step 2' and a '1b' section that are not clearly labeled.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) in a single file with no bundle references, which is appropriate for a CLI integration guide; minor gaps where detailed clientAction handling could live in a reference.	4 / 5
	Total	15 / 20 Passed

Description

57%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 and names the UserLeap product, giving it a distinct niche. It is weakened by generic action language and a lack of natural domain keywords like surveys, micro-surveys, or feedback.

Suggestions

Replace generic verbs with concrete UserLeap actions, e.g. 'Create and send in-product surveys and micro-surveys, collect user feedback, and review responses.'

Add natural trigger terms users would say — 'surveys', 'micro-surveys', 'feedback', 'in-product surveys' — to the 'Use when...' clause.

Tighten the 'when' trigger to reference specific UserLeap concepts rather than the vague 'interact with UserLeap data'.

Dimension	Reasoning	Score
Specificity	Names the UserLeap domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete UserLeap-specific actions like creating surveys or collecting feedback.	2 / 5
Completeness	Both 'what' ('UserLeap integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with UserLeap data.') are present, but the trigger could be more concrete and specific.	4 / 5
Trigger Term Quality	Includes the natural brand keyword 'UserLeap' plus generic terms ('data', 'records', 'workflows'), but misses the natural domain synonyms users would say such as surveys, micro-surveys, or feedback.	3 / 5
Distinctiveness Conflict Risk	The explicit 'UserLeap integration' framing gives it a clear niche with minimal conflict risk, though the generic 'manage data, records, and automate workflows' phrasing could overlap with other data-oriented skills.	4 / 5
	Total	13 / 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/userleap/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.