Name: flowtrack
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

flowtrack

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

Quality

66%

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/flowtrack/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 action-dense with executable commands and a state-aware connection workflow, but it carries some unnecessary intro prose and inconsistent CLI invocation.

Suggestions

Cut the opening "FlowTrack is a SaaS application..." paragraph and the auth-plumbing aside; assume Claude knows what a SaaS workflow tool is.

Standardize on one invocation form (`membrane` or `npx @membranehq/cli@latest`) and note the alias once instead of mixing both.

Fix the step numbering so connecting has a labeled Step 1 and the referenced "Step 2" resolves clearly.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and concrete guidance, but the opening paragraph about who uses FlowTrack and asides like "so you can focus on the integration logic rather than auth plumbing" are explanation Claude does not need and could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxying with flag tables, but invocation is inconsistent (`membrane` vs `npx @membranehq/cli@latest`) which is a minor gap.	4 / 5
Workflow Clarity	The connection flow is sequenced (install → login → connection ensure → poll for READY → search → run) with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, though step numbering is slightly inconsistent ("1b", an unlabeled step 1, and a referenced "Step 2").	4 / 5
Progressive Disclosure	No bundle files exist and the skill is organized into clear sections (Overview, Working with FlowTrack, Auth, Connecting, Searching, Actions, Proxy, Best practices); content stays one level deep with no nested references, though some reference-style material (proxy flags, popular actions) is inlined.	4 / 5
	Total	15 / 20 Passed

Description

66%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 is clearly scoped to the FlowTrack app, but its action verbs and trigger phrases are generic and could be more concrete.

Suggestions

Replace generic verbs with concrete operations, e.g. "search FlowTrack records, run flows, create tasks, and pull reports".

Add natural trigger phrases users would say, such as "FlowTrack flows, stages, tasks, or reports" instead of only "interact with FlowTrack data".

Mention key entities (flows, stages, tasks, dashboards) as trigger terms to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("FlowTrack integration") and a few actions ("Manage data, records, and automate workflows"), but those actions are generic abstractions rather than concrete operations, so coverage is not comprehensive.	3 / 5
Completeness	Both "what" (manage data, records, automate workflows) and an explicit "when" clause are present, but the trigger ("interact with FlowTrack data") is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with FlowTrack data" supplies one plausible natural phrase, but it lacks synonyms, common variations, or file/format terms that users would actually say.	3 / 5
Distinctiveness Conflict Risk	FlowTrack is a named SaaS application, giving the description a clear niche with named triggers and minimal risk of firing for an unrelated skill.	5 / 5
	Total	15 / 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/flowtrack/SKILL.md
Commit: f484c82

Reviewed: 5 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.