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

Blog Docs Log in Get started

braze

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

Quality

Content

75%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 copy-paste commands and a clear, checkpointed connection workflow, supported by good section structure. Its main weaknesses are minor padding (the platform overview and filler lines) and the absence of validation guidance for destructive operations.

Suggestions

Trim the introductory 'Braze is a customer engagement platform...' paragraph and filler lines like 'Use action names and parameters as needed' to assume Claude's prior knowledge.

Add an explicit validation or confirmation checkpoint before destructive batch actions such as 'delete-users' (e.g. list affected users and confirm before running).

Consider moving the popular-actions reference table into a separate bundled reference file, keeping the SKILL.md body a lean overview with a one-level-deep pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven guidance, but the opening paragraph explaining what Braze is ('Braze is a customer engagement platform used by marketing teams...') and filler lines like 'Use action names and parameters as needed' add unnecessary explanation, fitting anchor 3 rather than 4.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a thorough popular-actions table with keys covering common cases, matching the anchor 5 example.	5 / 5
Workflow Clarity	The connect-to-poll-to-act sequence is clearly sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and feedback loops (re-poll after user action), matching anchor 4; it does not reach 5 because destructive actions like 'delete-users' appear in the table without any explicit pre-destruction validation step.	4 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections with no nested references and no bundle files to navigate, but the large inline popular-actions table could reasonably live in a separate reference file, leaving it at anchor 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

57%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 clearly binds to a distinct named platform and includes both a 'what' and 'Use when' clause, but its action verbs are generic and its trigger coverage is limited to the platform name. It is solid but could be sharpened with concrete Braze operations and richer trigger terms.

Suggestions

Replace generic verbs with concrete Braze operations, e.g. 'Export users, list campaigns and canvases, track events, send messages, and manage subscription groups'.

Expand the 'Use when' clause with specific triggers users would say, such as 'Use when the user wants to query Braze campaigns, segments, canvases, or user profiles'.

Add file/term synonyms or sub-domain keywords (campaigns, segments, canvases, content blocks) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the Braze domain but the actions 'Manage data, records, and automate workflows' are generic rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor; it does not reach anchor 3 because no genuinely concrete verbs (like 'export users' or 'send messages') are stated.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Braze data'), matching anchor 4; it falls short of 5 because the 'when' clause is generic and circular rather than using concrete trigger phrases.	4 / 5
Trigger Term Quality	'Braze integration' and 'interact with Braze data' include the core natural keyword users would say, but coverage is limited to the platform name with no synonyms or sub-terms (campaigns, segments, canvases), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Binding everything to the named Braze platform gives a clear niche with low conflict risk, but the broad verbs 'manage data, records' carry minor overlap with generic data skills, placing it at anchor 4 rather than 5.	4 / 5
	Total	13 / 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/braze/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.