Name: userflow-1
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

userflow-1

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

Quality

61%

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/userflow-1/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 content delivers actionable, executable CLI guidance and a reasonably clear connection workflow with state-based checkpoints, but is held back by some over-explanation filler, broken step numbering, and a missing labeled Step 2. It is solidly usable without reaching the lean, fully-sequenced top anchors.

Suggestions

Fix the broken step numbering: either label the post-connection section as "Step 2" or remove the "skip to Step 2" references so the workflow is self-consistent.

Trim the introductory "Userflow is a product tour..." paragraph and the awkward agent-type trailing sentence to respect token budget and assume Claude's knowledge.

Add an explicit validation/verification checkpoint after running actions or proxy requests (e.g. checking the `output` field or response status) to strengthen feedback loops for batch operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with direct CLI commands and code blocks, but includes some unneeded explanation (the opening "Userflow is a product tour and onboarding software..." background and the awkward "Those will be used to adjust tooling to be used best with your harness" filler), fitting the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) plus a flags table, with only minor gaps such as unsubstituted <actionId>/CONNECTION_ID placeholders, matching the mostly-executable-with-minor-gaps anchor.	4 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, but the step numbering is broken ("skip to Step 2" with no labeled Step 2, a lone "1b" section), leaving checkpoints partially present with navigation gaps, fitting the steps-listed-but-validation/sequence-gaps anchor.	3 / 5
Progressive Disclosure	As a single self-contained SKILL.md with no bundle files, content is well-sectioned under clear headers with no nested or buried references; there is only minor room for tighter organization, matching the good-structure-with-minor-gaps anchor.	4 / 5
	Total	14 / 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 correctly pairs a what-statement with an explicit Use-when trigger and is anchored to the distinct Userflow product, but its capability verbs are generic and it lacks richer trigger-term synonyms. It sits solidly above the midpoint without reaching the comprehensive-anchor level.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Userflow-specific actions such as "create flows and steps, manage users and segments, run in-app surveys."

Expand the trigger clause with natural phrasings users would say, e.g. "Use when the user wants to create onboarding flows, manage Userflow users/segments, or run in-app surveys."

Add the docs/file-context cue (e.g. mentioning Userflow flows or segments) to strengthen distinctiveness and trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Userflow) plus actions like "Manage data, records, and automate workflows," but the verbs are generic ("manage," "automate") rather than concrete, matching the anchor for domain + 1-2 actions that are not comprehensive.	3 / 5
Completeness	Both a clear "what" (Userflow integration, manage data/records/automate workflows) and an explicit "when" ("Use when the user wants to interact with Userflow data") are present, but the trigger is somewhat generic rather than listing concrete trigger phrases, matching the anchor for both present with the "when" improvable.	4 / 5
Trigger Term Quality	"Userflow" and "Userflow data" are the natural trigger terms, but coverage lacks synonyms, file extensions, or common variations users might say, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The Userflow brand name pins it to a distinct niche with minimal conflict risk, though the broad "manage data, records, and automate workflows" phrasing leaves minor overlap with general data/automation skills, fitting the mostly-distinct anchor.	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/userflow-1/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.