Name: breeze
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

breeze

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

Quality

69%

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/breeze/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.

The body is highly actionable with concrete, executable Membrane commands and a useful action reference, organized into clear sections. Its main weakness is the absence of validation/verification guidance around destructive and batch operations, which limits workflow clarity.

Suggestions

Add an explicit validation/confirmation step before running destructive actions (delete-project, delete-card), e.g. confirm the targeted ID with the user or fetch-then-verify before deleting.

Trim promotional padding in "Best practices" (e.g. "This will burn less tokens and make communication more secure") to lean, directive guidance.

Consider moving the 20-row popular-actions table into a references file and keeping only the most common actions inline, to improve progressive disclosure for this >50-line skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command references and tables, with only minor over-explanation (e.g. the promotional "Best practices" prose and "This is the fastest way to get a connection") that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands for every stage (login, connection ensure, action list/run, proxy) plus a concrete popular-actions table with keys and a proxy flag reference, covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll loop, but destructive actions (delete-project, delete-card) and batch list operations lack any validation/verification step, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references and no bundle files present; the only gap is the large popular-actions reference table that is inlined rather than split out.	4 / 5
	Total	16 / 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 is third-person and answers both what and when, but the trigger guidance and action list are generic and omit the concrete Breeze concepts (projects, tasks, cards, time entries) that appear in the body. It is solid but could be sharpened with specific trigger terms.

Suggestions

Replace generic phrasing with concrete Breeze actions, e.g. "Manage Breeze projects, tasks (cards), stages, and time entries."

Expand the "Use when" clause with natural trigger phrases: "Use when the user wants to manage Breeze projects, tasks, cards, or time tracking."

Add the most common nouns users say (projects, tasks, cards, time entries) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (Breeze) and a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic and coverage is not comprehensive.	3 / 5
Completeness	States both a what ("Manage data, records, and automate workflows") and a when ("Use when the user wants to interact with Breeze data"), but the when is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Breeze", "Breeze data") but misses common natural variations users would say like projects, tasks, cards, or time entries.	3 / 5
Distinctiveness Conflict Risk	The named product Breeze gives it a clear niche with minimal conflict risk, though the generic "manage data, records" wording leaves minor overlap with other project-management skills.	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/breeze/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.