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

bloomreach

BloomReach integration. Manage data, records, and automate workflows. Use when the user wants to interact with BloomReach 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/bloomreach/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 highly actionable with a strong connection-workflow that includes explicit validation and error-recovery feedback loops, and it is well-structured in one file. It loses points mainly on a few padded explanatory passages and minor inconsistencies in command invocation and step labeling.

Suggestions

Trim the marketing overview paragraph and the "so you can focus on integration logic" padding to assume Claude's competence and improve token efficiency.

Normalize command invocations (membrane vs npx @membranehq/cli) and provide a concrete example actionId so the action-run steps are unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but includes unnecessary explanation such as the BloomReach marketing overview ("personalized customer experience platform... improve online sales") and padding like "so you can focus on the integration logic rather than auth plumbing", fitting the anchor for mostly-efficient content with some over-explanation to trim.	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands appear throughout (install, login, connection ensure, action list/run, request) with a full proxy flag table, but minor gaps remain (placeholder <actionId>, inconsistent membrane vs npx invocation), matching the anchor for mostly-executable guidance with minor gaps.	4 / 5
Workflow Clarity	The install → login → connection ensure → poll-for-ready → search-actions → run sequence has explicit state checks and feedback loops (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-poll recovery), but step labels are slightly inconsistent (an unlabeled "Step 2", a "1b" sub-step), fitting the clear-sequence-with-minor-gaps anchor.	4 / 5
Progressive Disclosure	The skill is a single well-organized SKILL.md with clear sections (Overview, Working with BloomReach, Popular actions, Best practices) and no nested references, but at ~145 lines it exceeds the under-50-line simple-skill exception, so it fits the good-structure anchor rather than the top anchor.	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 highly distinctive due to the named BloomReach product, but its actions are generic verbs on generic nouns and it lacks concrete trigger synonyms. Strengthening specificity and trigger terms would move it toward the top anchor.

Suggestions

Replace generic verbs ("Manage", "automate") with concrete BloomReach actions such as "manage catalog products, content documents, and email/web campaigns".

Add concrete trigger phrases users would say, e.g. "Use when working with BloomReach catalogs, content documents, campaigns, orders, or promotions".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the BloomReach domain and three actions, but the verbs (manage, automate) and nouns (data, records, workflows) are generic rather than concrete, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with BloomReach data"), but the trigger guidance is generic rather than tied to concrete phrases, fitting the anchor where both are present yet "when" could be more specific.	4 / 5
Trigger Term Quality	"BloomReach" and "interact with BloomReach data" provide some relevant natural keywords, but common variations or synonyms (e.g., specific product/record names, scenarios like SEO or content) are missing, matching the anchor for partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	"BloomReach" is a named product with a clear niche and distinct triggers, giving it minimal conflict risk with other skills, matching the anchor for a clear niche with distinct triggers.	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/bloomreach/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.