Name: flowla
Rating: 64.8 (1 reviews)
Author: membranedev

flowla

Flowla integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with Flowla data.

Quality

77%

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

Quality

Content

76%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.

A highly actionable integration guide built around executable Membrane CLI commands with good structure and conciseness. Its main gap is the absence of explicit validation/verification checkpoints for destructive operations (proxy mutations, action runs), which caps workflow clarity.

Suggestions

Add explicit verification steps before destructive operations — e.g., after connecting, confirm the connectionId is valid via `connection list`; before running a mutating action or proxy POST/DELETE, confirm the target and check the response status.

Introduce a validate-then-fix feedback loop for the connect/run workflow (run command -> inspect `--json` output -> if error, diagnose and retry) to mirror the rubric's checkpoint expectation.

Tighten the intro by dropping the audience sentence and the vague "Use action names and parameters as needed" line to remove residual over-explanation.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, built around concrete commands and a compact flag table, with only minor over-explanation such as the intro's sentence on who typically uses Flowla and the vague "Use action names and parameters as needed".	4 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands (login, search, connect, action list, action run, request) with clearly marked placeholders (CONNECTOR_ID, CONNECTION_ID, ACTION_ID) and a complete proxy flag table covering the common cases.	5 / 5
Workflow Clarity	The setup-to-run sequence is clearly laid out with numbered steps and commands, but there are no explicit validation/verification checkpoints; because proxy requests and action runs support destructive operations (POST/PUT/PATCH/DELETE), the missing-feedback-loop cap holds this at 3.	3 / 5
Progressive Disclosure	The single-file body is well organized into clear, navigable sections (Overview, Working with Flowla, setup, connecting, searching, proxy, best practices); with no bundle files present and content appropriately placed inline, only minor organization gaps remain versus a reference-split structure.	4 / 5
	Total	16 / 20 Passed

Description

78%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.

A solid description that clearly states both the capability and trigger condition with a distinctive product name. The main weakness is a single "Manage" verb spread across entity nouns and a trigger clause that could enumerate the user-mentionable terms more explicitly.

Suggestions

Replace the single "Manage" verb with multiple distinct actions per entity (e.g., "Create, list, update, and delete Organizations, Pipelines, Users, and Filters") to raise specificity.

Expand the "Use when..." clause to enumerate concrete trigger phrases, e.g., "Use when the user wants to manage Flowla organizations, pipelines, users, or filters, or mentions Flowla data."

Dimension	Reasoning	Score
Specificity	Names the Flowla domain and enumerates four concrete entity targets ("Manage Organizations, Pipelines, Users, Filters"), but relies on a single verb ("Manage") rather than multiple distinct actions, leaving minor coverage gaps versus a fully comprehensive list.	4 / 5
Completeness	Both "what" (Flowla integration, manage four entity types) and "when" ("Use when the user wants to interact with Flowla data") are present and explicit; the "when" could be more specific by enumerating concrete trigger phrases, so it falls just short of the top anchor.	4 / 5
Trigger Term Quality	Good keyword coverage including the distinctive product name "Flowla" plus natural entity terms (Organizations, Pipelines, Users, Filters); the "Use when..." trigger is explicit but slightly generic ("interact with Flowla data") without re-stating the user-mentionable entity terms.	4 / 5
Distinctiveness Conflict Risk	The distinctive product name "Flowla" defines a clear niche with minimal conflict risk; while the entity types are somewhat generic, the explicit Flowla anchoring makes triggering for the wrong skill unlikely.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/flowla/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.