Name: zixflow
Rating: 62.4 (1 reviews)
Author: membranedev

zixflow

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

Quality

74%

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

Quality

Content

82%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 strong, executable CLI usage guide with a well-sequenced connection workflow and explicit validation via connection states. Its main gaps are a stray unlabeled step reference and a long single-file structure that could offload reference material.

Suggestions

Label the referenced "Step 2" explicitly (e.g. a "## Step 2: Search and run actions" header) or remove the cross-reference so the sequence is self-consistent.

Move the verbose proxy flag table and action-listing details into a separate reference file, keeping SKILL.md a concise overview with one-level-deep pointers.

Trim the opening "Zixflow is a SaaS application..." marketing sentence; Claude does not need the CI/CD backstory to use the CLI.

Dimension	Reasoning	Score
Conciseness	Mostly efficient commands with minimal padding, but the opening CI/CD description and some Membrane-proxy explanation could be trimmed; assumes Claude's competence otherwise.	4 / 5
Actionability	Provides copy-paste-ready executable commands for install, login, connection, action search/run, and proxy requests, with flags and JSON parameter examples covering the common cases.	5 / 5
Workflow Clarity	Clear install→authenticate→connect→search→run sequence with explicit state-based polling and error recovery (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but it references an unlabeled "Step 2" and the step numbering is inconsistent.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested references, but the entire CLI guide (~150 lines) is inlined in a single file with no offloaded reference for the action/proxy details.	4 / 5
	Total	17 / 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 cleanly states what the skill does and when to use it in third person, and the product name keeps it distinct. Its weakness is generic action verbs and thin trigger-term coverage.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete operations a user would perform, e.g. "create and update records, list collections, and trigger workflows".

Broaden trigger terms beyond the product name, e.g. "Use when the user wants to query, create, or update Zixflow records or run Zixflow workflows".

Tighten the "when" clause to name the specific objects users mention (records, flows, collections) rather than just "Zixflow data".

Dimension	Reasoning	Score
Specificity	Names the domain ("Zixflow integration") and lists a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete like "extract" or "fill".	3 / 5
Completeness	Explicitly answers both what (integration; manage data, records, automate workflows) and when ("Use when the user wants to interact with Zixflow data"), though the "when" clause is somewhat generic.	4 / 5
Trigger Term Quality	Includes the product keyword "Zixflow" and "Zixflow data", but offers no synonyms, file extensions, or common natural-language variations users might say.	3 / 5
Distinctiveness Conflict Risk	Anchored to a specific named SaaS product (Zixflow), giving it a clear niche with minimal overlap risk against other skills.	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/zixflow/SKILL.md
Commit: f484c82

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