Name: mindbreeze
Rating: 43.2 (1 reviews)
Author: membranedev

mindbreeze

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

Quality

44%

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

Quality

Content

38%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 CLI usage sections are genuinely actionable, but they are buried under a massive, duplicated, concept-free bullet dump that wastes the context window and should live in a separate reference file. A clear numbered workflow with validation checkpoints would also raise the workflow score.

Suggestions

Move the ~300-line enumeration of Mindbreeze objects into a references/ file (e.g. OBJECTS.md) and replace it with a one-line pointer, eliminating the padding and deduplication.

Add an explicit numbered workflow (connect -> wait for READY -> discover actions -> run) with a validation checkpoint that confirms the action output before continuing.

Remove duplicated list entries (Category, Event, Image, Defense, etc. each appear twice) and drop generic nouns unrelated to Mindbreeze to tighten the body.

Dimension	Reasoning	Score
Conciseness	The body opens with an ~300-line flat bullet list of hundreds of generic nouns (Company, Law, Music, etc.) many duplicated (Category, Event, Image, Defense all appear twice) that explain nothing Claude needs, fitting 'severely verbose; heavily padded'.	1 / 5
Actionability	It provides concrete, executable CLI commands ('membrane login --tenant', 'membrane connection ensure "https://inspire.mindbreeze.com/" --json', 'membrane action run ...') covering the common flow with only minor gaps, matching 'mostly executable guidance; concrete commands with minor gaps'.	4 / 5
Workflow Clarity	A connect -> wait/poll -> search actions -> run sequence is present with state-checking, but the overall flow lacks a clear numbered spine and there is no validation/feedback loop verifying action results before proceeding, fitting 'steps listed but validation gaps; checkpoints implicit'.	3 / 5
Progressive Disclosure	The giant inlined noun list clearly belongs in a separate reference file yet is dumped into SKILL.md, and there are no bundle files or one-level-deep references to offload it, matching 'content that clearly belongs in separate files is inlined'.	2 / 5
	Total	10 / 20 Passed

Description

50%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 correctly identifies the Mindbreeze product niche and includes an explicit 'Use when' trigger, but its action verbs are generic and it lacks the natural search/insight vocabulary users would actually invoke. Tightening with concrete Mindbreeze capabilities and richer trigger terms would lift the middle dimensions.

Suggestions

Replace generic actions with concrete Mindbreeze operations, e.g. 'Search indexed data sources, inspect query profiles, and manage datasources, indices, and roles'.

Expand trigger terms to natural user phrasing: 'search Mindbreeze', 'query insights', 'manage Mindbreeze datasources', 'inspect Mindbreeze index'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to search, query, or administer Mindbreeze data sources and indices'.

Dimension	Reasoning	Score
Specificity	The description names the Mindbreeze domain but its actions are generic ('Manage data, records, and automate workflows') with no concrete Mindbreeze-specific operations, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Mindbreeze data'), but the 'when' is generic rather than tied to concrete trigger phrases, matching the 'both present; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	Only the bare term 'Mindbreeze' and 'data'/'records' appear; the natural phrases a user would say (search, insights, datasource, query) are missing, fitting 'one or two generic keywords; missing the natural phrases'.	2 / 5
Distinctiveness Conflict Risk	Naming the proprietary product 'Mindbreeze' makes it largely distinct from other skills, though the generic 'Manage data, records' wording leaves minor overlap risk, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	12 / 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/mindbreeze/SKILL.md
Commit: f484c82

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