Name: brex
Rating: 64.8 (1 reviews)
Author: membranedev

brex

Brex integration. Manage Accounts, Vendors, Bills, Expenses, Budgets. Use when the user wants to interact with Brex data.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/brex/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 content is a strong, actionable integration guide with executable commands throughout and a validated connection workflow. Its only notable gaps are a broken "Step 2" reference and a small amount of background padding at the top.

Suggestions

Fix the dangling "Step 2" references by numbering the connection workflow steps explicitly (1, 2, 3...) or relabeling the cross-references.

Trim or relocate the opening "Brex is a corporate credit card..." paragraph and the bare "Brex Overview" bullet tree, which add little actionable value.

Add a brief verification step after running mutating actions (e.g., re-list the resource to confirm a create/update/delete succeeded).

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient, command-driven prose, but the opening Brex background paragraph and the skeletal "Brex Overview" tree add minor over-explanation Claude largely does not need.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxying, plus a populated Popular actions table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow has explicit state checks and a poll-after-action feedback loop, but it references a "Step 2" that is never labeled, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections with no nested references; the inline Popular actions table is the only bulk reference content that might otherwise live in a separate file.	4 / 5
	Total	17 / 20 Passed

Description

73%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 identifies a distinct niche (Brex) and includes both a what and a when clause. Its main weakness is the generic "Manage" verb and a somewhat broad "interact with Brex data" trigger, which keep it from full marks on specificity and completeness.

Suggestions

Replace the generic verb "Manage" with concrete actions (e.g., "List, create, update, and delete Accounts, Vendors, Bills, Expenses, and Budgets").

Tighten the "when" clause with concrete triggers (e.g., "Use when the user asks about Brex cards, expenses, vendors, budgets, or account transfers").

Dimension	Reasoning	Score
Specificity	It names the Brex domain plus several concrete resource types ("Accounts, Vendors, Bills, Expenses, Budgets"), but the only action verb is the generic "Manage", so coverage is solid yet not action-specific.	3 / 5
Completeness	It states what ("Manage Accounts, Vendors, Bills, Expenses, Budgets") and when ("Use when the user wants to interact with Brex data"), but the "when" clause is fairly generic and could be more specific.	4 / 5
Trigger Term Quality	Natural terms like "Brex", "Brex data", and the named resource categories are present and would be said by users; lacking synonyms beyond these but otherwise good coverage.	4 / 5
Distinctiveness Conflict Risk	Brex is a specific named platform with distinct triggers, so the description carves a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/brex/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.