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

Blog Docs Log in Get started

brick

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/brick/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, command-driven integration guide with good actionability and a connection workflow that includes real validation checkpoints. Its main weaknesses are mild verbosity, an unexplained Overview section, and a broken step reference that muddy the workflow.

Suggestions

Remove or explain the 'Brick Overview' list (Dataset/Schema/Model/Inference) — it currently reads as filler unrelated to the Membrane-based workflow.

Fix the dangling 'skip to Step 2' reference by labeling the subsequent sections (e.g., rename 'Searching for actions' to 'Step 2: Search for actions') so the connection workflow is unambiguous.

Trim editorial padding such as 'so you can focus on the integration logic rather than auth plumbing' to keep every token load-bearing.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, but contains unnecessary padding ("so you can focus on the integration logic rather than auth plumbing") and an unexplained "Brick Overview" list (Dataset/Schema/Model/Inference) that earns no place, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (npm install, membrane login, connection ensure, action run) with clear placeholders; only minor gaps keep it from the fully comprehensive anchor 5.	4 / 5
Workflow Clarity	The connection flow is sequenced with state-based polling feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and retry guidance; gaps are the dangling 'skip to Step 2' with no labeled Step 2 and the orphan Overview section.	4 / 5
Progressive Disclosure	It is a single well-sectioned file (Install, Auth, Connecting, Searching, Popular actions, Best practices) with no nested references; the underdeveloped Overview list and inline proxy table 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 states both what the skill does and when to use it, anchored to a distinct named app (Brick), so it clears the key completeness and distinctiveness bars. It is held back from the top tier by generic action verbs ('manage data, records') and a thin set of natural trigger synonyms.

Suggestions

Replace generic verbs with concrete Brick-specific actions (e.g., 'pull financial/transaction records, sync project data, trigger workflow automations') to lift specificity.

Expand the 'Use when...' clause with natural user phrasings and synonyms (e.g., 'Use when the user wants to query Brick data, list records, or automate Brick workflows').

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Brick domain plus a couple of actions, but the verbs are generic ("manage") rather than concrete, matching the anchor that lists 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Brick data") are present; the 'what' is generic enough that it does not reach the fully concrete anchor 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Brick data" supplies relevant keywords (Brick, data, records, workflows), but it misses common variations or synonyms a user might actually say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Brick integration" targets a specific named application niche with a distinct trigger ("interact with Brick data"), giving mostly distinct triggers with only minor overlap risk from the generic action verbs.	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/brick/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.