Name: brass
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

brass

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

Quality

65%

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/brass/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 body is a solid, actionable integration guide with executable commands and a well-handled connection-state feedback loop, weakened mainly by a marketing-flavored intro, some vague filler, and a couple of duplicated or mislabeled steps.

Suggestions

Trim the opening company-description paragraph and 'Use action names and parameters as needed' to focus on what Claude does not already know.

Fix the 'skip to Step 2' reference by labeling the post-connection steps explicitly (e.g. 'Step 2: Search for actions') and renumber the '1b' polling subsection.

Remove the duplicated 'membrane action list' command block under 'Popular actions' since it already appears in 'Searching for actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening marketing paragraph ('Finance teams and business owners use Brass to gain better visibility into their cash flow and make data-driven financial decisions'), the vague 'Use action names and parameters as needed', and a duplicated 'membrane action list' command add padding Claude does not need.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) plus a flags table, with only minor gaps such as the CONNECTION_ID placeholder and the 'QUERY' intent stub, fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The install -> login -> connect -> search -> run sequence is clear and the connection state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) forms a real feedback loop, but the dangling 'skip to Step 2' reference (no labeled Step 2) and the oddly numbered '1b' subsection leave minor clarity gaps.	4 / 5
Progressive Disclosure	The content is well organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to navigate, though the out-of-place 'Brass Overview' hierarchy block and the duplicated action-list command are minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

62%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 answers what the skill does and when to use it with a clear platform-specific trigger, but its action verbs are generic and it lacks the concrete Brass domain terms (expenses, spend, budget) users would naturally say.

Suggestions

Replace generic verbs with Brass-specific actions, e.g. 'Track expenses, manage budgets, and view transactions' instead of 'Manage data, records, and automate workflows'.

Expand the 'Use when' clause with natural trigger terms users actually say, e.g. 'Use when the user wants to track Brass expenses, manage budgets, or pull spend/transaction data'.

Drop the redundant 'Brass integration.' opener so the description leads with the concrete capabilities.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Brass domain plus two-to-three actions, but the actions ('manage data', 'records') are generic rather than concrete, matching the anchor that names the domain with 1-2 actions but is not comprehensive.	3 / 5
Completeness	It states both the 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Brass data'), but the 'when' is somewhat generic and could name concrete triggers, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Brass data' includes 'Brass' and 'data' but misses natural variations users would say (e.g. 'expenses', 'spend', 'budget', 'transactions'), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Brass integration' framing and 'interact with Brass data' trigger tie it to a specific platform, giving it a clear niche with minimal conflict risk, though the generic 'manage data, records' verbs leave minor overlap with other data skills.	4 / 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/brass/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.