Name: fattmerchant
Rating: 61.6 (1 reviews)
Author: membranedev

fattmerchant

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

Quality

72%

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/fattmerchant/SKILL.md

Quality

Content

86%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 highly actionable with executable CLI commands, a clear validated workflow, and good section organization. Minor conciseness improvements (trimming the marketing intro and a few asides) and the absence of reference files for offloading detail are the only gaps.

Suggestions

Remove the marketing-style first line ('used by businesses of all sizes looking for transparent and cost-effective payment solutions') since Claude does not need it to operate the skill.

Trim rhetorical asides such as 'so you can focus on the integration logic rather than auth plumbing' that add tokens without executable value.

Consider extracting the connection-state reference (clientAction fields) into a references/ file to keep the core workflow leaner.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and minimal padding, though a few explanatory asides ('so you can focus on the integration logic rather than auth plumbing') and the marketing-style intro line could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready CLI commands with all flags, JSON parameter examples, and a full options table covering the common proxy and action-run cases.	5 / 5
Workflow Clarity	Clear sequenced workflow (install -> login -> connect -> poll for READY -> search actions -> run/proxy) with explicit validation via --wait polling and a CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR feedback loop that re-checks state after the user acts.	5 / 5
Progressive Disclosure	Single SKILL.md (~169 lines) with well-organized sections and no nested references; content is appropriately placed but has no reference files to offload detail, leaving minor organization headroom.	4 / 5
	Total	18 / 20 Passed

Description

58%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 identifies a distinct product niche and includes an explicit 'Use when' trigger, but its capability language ('manage data, records, automate workflows') is generic rather than concrete. Trigger-term coverage is adequate but lacks synonyms or file-extension variations.

Suggestions

Replace generic verbs with concrete Fattmerchant-specific actions (e.g., 'Create and send invoices, manage subscriptions, process transactions, handle customer payment methods').

Add natural trigger synonyms users might say, such as 'subscriptions', 'invoicing', 'payment processing', or 'Fattmerchant API'.

Tighten the 'what' so the capabilities mirror the actual action surface (invoices, transactions, plans) rather than 'manage data, records'.

Dimension	Reasoning	Score
Specificity	Names the domain (Fattmerchant) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic ('manage', 'automate') rather than concrete; not comprehensive but above anchor 2.	3 / 5
Completeness	States both what it does ('Manage data, records, and automate workflows') and an explicit when clause ('Use when the user wants to interact with Fattmerchant data'), though the 'what' is somewhat generic.	4 / 5
Trigger Term Quality	Includes 'interact with Fattmerchant data' which is a relevant phrase, but lacks common synonyms or file-extension variations; missing natural variations users might say.	3 / 5
Distinctiveness Conflict Risk	Fattmerchant is a specific named product niche, making it clearly distinguishable from other skills; minor overlap risk only with other payment-related 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/fattmerchant/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.