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

userflow

Userflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with Userflow 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/userflow/SKILL.md

Quality

Content

68%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 highly actionable, built from copy-paste CLI commands and a well-structured connection workflow with state-based feedback loops. Its main gaps are a few trimmable explanatory bits and a lack of validation steps for data-mutating actions, which cap workflow clarity.

Suggestions

Add a verification step after running data-mutating actions (e.g., re-query the affected record or check the response status) so the workflow includes an explicit validate-and-confirm loop.

Trim the filler "Use action names and parameters as needed" line and the duplicate action-list command under "Popular actions", and tighten the "auth plumbing" sentence.

Clarify the step numbering (the "skip to Step 2" reference points at no labeled Step 2) so the connection sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient, executable CLI commands, but it includes trimmable bits: the "auth plumbing" aside, the sparse "Userflow Overview" section ending in "Use action names and parameters as needed", and a duplicated action-list command, fitting the 3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, polling, action list/run, proxy) plus a flag table, matching the 5 anchor of fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with polling feedback loops, but running actions on Userflow data is a data-mutating workflow with no validation or verification steps, which caps workflow clarity at 3 per the destructive/batch rule.	3 / 5
Progressive Disclosure	The body is organized into clear sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, but the thin overview section and inline flag table represent minor organization gaps, matching the 4 anchor.	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 and when with an explicit trigger clause and is anchored to a named product, giving it solid completeness and distinctiveness. Its weakness is generic action language and thin trigger-term coverage, which keep specificity and trigger quality at the midpoint.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Userflow capabilities such as "build flows, manage users and groups, and trigger surveys".

Expand the trigger clause with natural phrasing users would say, e.g. "Use when the user wants to build onboarding flows, manage Userflow users/groups, or automate user engagement workflows."

Dimension	Reasoning	Score
Specificity	Names the Userflow domain and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete capabilities, matching the 3 anchor of domain plus 1-2 non-comprehensive actions.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Userflow data"), but the what is somewhat generic so it does not reach the fully concrete 5 anchor.	4 / 5
Trigger Term Quality	The only natural keyword is the product name "Userflow" and "Userflow data"; it lacks synonyms or common variations a user might say, fitting the 3 anchor of some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a named product (Userflow) makes it mostly distinct with only minor overlap risk against other integration skills, matching the 4 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/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.