Name: bloom-growth
Rating: 60.8 (1 reviews)
Author: membranedev

bloom-growth

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

Quality

71%

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/bloom-growth/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 highly actionable with executable Membrane CLI commands and a clear connection workflow including polling/validation feedback loops. Its main weaknesses are minor marketing fluff in the intro and slightly loose step numbering that could be tightened.

Suggestions

Trim the intro to Bloom Growth's purpose in one line and drop the marketing clause about engagement/organizational growth to recover tokens.

Fix the step labeling: rename "1b" to a properly numbered step and add an explicit "## Step 2: Search and run actions" header so the "skip to Step 2" reference resolves.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste command blocks, but the opening "Bloom Growth is a platform that helps businesses manage..." paragraph carries marketing padding ("aims to improve employee engagement and drive organizational growth") and a few rhetorical asides ("so you can focus on the integration logic rather than auth plumbing"), matching the efficient-with-minor-over-explanation anchor rather than the lean 5-anchor.	4 / 5
Actionability	Concrete, copy-paste-ready commands cover the common cases end to end (install, login, connection ensure/get, action list/run, request) plus a flag table for proxy requests, matching the fully-executable copy-paste-ready anchor.	5 / 5
Workflow Clarity	The install→authenticate→connect→poll→search/run sequence is clear with a state-machine feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and "poll again"), but step labeling is loose ("skip to Step 2" with no defined Step 2 header, a "1b" with no "1a"), which is a minor clarity gap keeping it below the explicit-checklist 5-anchor.	4 / 5
Progressive Disclosure	At ~145 lines the skill exceeds the under-50-line simple-skill exception, but it is well-organized into clear sections with content appropriately kept inline since actions are discovered dynamically via the CLI rather than enumerated statically; there are no external references, matching the good-structure-minor-organization-gaps anchor.	4 / 5
	Total	17 / 20 Passed

Description

61%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 establishes a distinct niche (Bloom Growth) with both a what and a Use-when clause, but its action list is generic and its trigger language could be richer with concrete capability terms. It is solid but leaves specificity and trigger-term quality on the table.

Suggestions

Replace generic verbs with concrete Bloom Growth capabilities, e.g. "Create and track goals, run check-ins, and manage reflections and templates" instead of "Manage data, records, and automate workflows".

Expand the Use-when clause with natural trigger phrases users actually say, e.g. "Use when the user wants to manage Bloom Growth goals, check-ins, reflections, or performance reviews".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Bloom Growth domain but the actions are generic ("manage data", "automate workflows") rather than concrete capabilities, matching the anchor for minimal/generic actions and falling below the 3-anchor which requires genuinely concrete actions.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when..." "when" clause are present, but the trigger condition is generic, matching the both-present-but-when-could-be-more-specific anchor; it does not reach 5 because the trigger phrases are not concrete.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Bloom Growth data" includes the natural keyword "Bloom Growth", but lacks common variations or synonyms a user might say (e.g. "Bloom Growth records", "Bloom Growth check-ins", "performance reviews"), matching the some-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	"Bloom Growth integration" targets a single named niche application with a distinct trigger ("Bloom Growth"), giving it a clear niche with minimal conflict risk against other skills, matching the clear-niche-distinct-triggers anchor.	5 / 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/bloom-growth/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.