Name: userpilot
Rating: 52.8 (1 reviews)
Author: membranedev

userpilot

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

Quality

59%

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

Quality

Content

61%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 mostly executable, well-structured CLI integration guide with good connection-state handling. Its main weaknesses are a verbose marketing intro, redundancy between action-search sections, and missing validation guidance before destructive proxy or batch action operations.

Suggestions

Trim the opening marketing paragraph to one neutral sentence about what Userpilot is, or remove it and rely on the official-docs link.

Add an explicit verification checkpoint before destructive proxy calls (e.g. 'For -X DELETE or -X PUT, confirm the target id and dry-run a GET first').

Merge the redundant 'Popular actions' section into 'Searching for actions' to remove the duplicated command.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and flags, but the marketing-style intro ('helps SaaS companies improve user onboarding...') and the redundant 'Popular actions' command could be tightened.	3 / 5
Actionability	It provides concrete, executable CLI commands (install, login, connection ensure, action run) and a flag table, with only minor gaps such as templated placeholders and an example proxy path.	4 / 5
Workflow Clarity	The connect-search-run sequence is clear with explicit connection-state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive proxy verbs (DELETE) and batch action runs lack explicit validation/verification steps, capping this at 3.	3 / 5
Progressive Disclosure	The single-file body is well-organized into clear sections (overview, install, auth, connecting, searching, actions, proxy, best practices) with no nested references; minor redundancy between 'Searching for actions' and 'Popular actions'.	4 / 5
	Total	14 / 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 covers what and when at a basic level and leverages a distinct product name, but it relies on generic action verbs ('manage', 'automate') instead of concrete capabilities. Tightening the trigger phrasing and listing specific Userpilot operations would raise specificity and completeness.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Userpilot capabilities such as 'create users, update account attributes, track events, and build in-app onboarding flows'.

Broaden the trigger clause to include natural phrasings like 'when the user mentions Userpilot, user onboarding, in-app experiences, or feature adoption'.

Add synonyms or platform-specific terms (e.g. 'Userpilot Assistant', 'feature tags') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the Userpilot domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete capabilities.	2 / 5
Completeness	It answers both 'what' (Userpilot integration that manages data/records/workflows) and 'when' ('Use when the user wants to interact with Userpilot data'), though the when-clause could be more specific.	4 / 5
Trigger Term Quality	It includes 'Userpilot', 'data', and 'records' but the trigger phrasing ('interact with Userpilot data') misses common variations and synonyms a user might say.	3 / 5
Distinctiveness Conflict Risk	Userpilot is a specific branded niche so the skill is mostly distinct, but the generic 'interact with Userpilot data' trigger leaves minor overlap risk with adjacent data 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/userpilot/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.