Name: fabrick
Rating: 59.2 (1 reviews)
Author: membranedev

fabrick

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

Quality

68%

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/fabrick/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 a strong, executable guide to driving Fabrick through the Membrane CLI, with a clear state-machine workflow for connections and a useful flags reference; its main weaknesses are some redundant/thin sections and the absence of validation guidance for destructive financial actions.

Suggestions

Remove or merge the redundant 'Popular actions' section into 'Searching for actions' and tighten the filler 'Fabrick Overview' to reduce token waste.

Define the unlabeled 'Step 2' (or replace 'skip to Step 2' references) so the connection workflow is fully navigable.

Add a validation checkpoint for destructive or financial actions (e.g. confirm parameters, dry-run, or inspect output before confirming payments) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the thin 'Fabrick Overview' ('Document / Page / Template', 'When to use which actions: Use action names and parameters as needed') and the redundant action-list blocks repeated across 'Searching for actions', 'Popular actions', and 'Best practices' could be tightened.	3 / 5
Actionability	It provides copy-paste ready CLI commands covering the common cases (install, login, connection ensure, --wait polling, action list/run with --input, request with a flags table), each executable as written.	5 / 5
Workflow Clarity	The connection flow has a clear state-driven sequence with explicit feedback loops (poll --wait, re-poll after CLIENT_ACTION_REQUIRED), but the repeated 'skip to Step 2' references a Step 2 that is not labeled, and there is no validation guidance for potentially destructive financial actions.	4 / 5
Progressive Disclosure	Content is organized into clear, navigable sections with no external bundle files needed; the main gap is the near-empty/redundant 'Popular actions' section that adds little structure, keeping it below 5.	4 / 5
	Total	16 / 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 is a functional trigger description with both what and when clauses anchored by the distinct Fabrick brand name, but its actions are generic and it omits Fabrick's concrete finance-domain capabilities and richer trigger terms.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Fabrick capabilities such as banking, payments, and lending actions.

Expand the 'Use when' trigger to enumerate natural phrases users would say (e.g. 'when the user wants to query Fabrick accounts, initiate payments, or read financial records').

Include entity synonyms (e.g. account balances, transactions) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Fabrick) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic and do not surface Fabrick's actual banking/payments/lending capabilities, so coverage is not 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 Fabrick data') are present; the when clause is reasonably explicit but could name more concrete trigger phrases, so it falls short of a 5.	4 / 5
Trigger Term Quality	The brand keyword 'Fabrick' and the phrase 'interact with Fabrick data' give some relevant triggers, but common variations or synonyms (e.g. payments, banking, finance data) are missing.	3 / 5
Distinctiveness Conflict Risk	The Fabrick brand name gives a clear niche with minimal conflict risk, though the generic 'manage data, records, and automate workflows' phrasing could overlap with other data/automation skills, keeping it just below 5.	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/fabrick/SKILL.md
Commit: f484c82

Reviewed: 5 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.