Name: fraudlabs-pro
Rating: 52 (1 reviews)
Author: membranedev

fraudlabs-pro

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

Quality

58%

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/fraudlabs-pro/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 content is a solid, actionable integration guide with concrete CLI commands, a clear connection workflow with state-handling feedback loops, and good section organization. Its main weaknesses are mild marketing padding, inconsistent step numbering, and the absence of verification guidance for the destructive blacklist delete operations it exposes.

Suggestions

Trim the marketing-style intro paragraph and remove filler like 'Use action names and parameters as needed' to tighten token usage.

Fix the step numbering (label 'Step 1' before '#### 1b', and mark the referenced 'Step 2') so the connection workflow is unambiguous.

Add a validation/verification checkpoint for destructive operations, e.g. 'Get' the blacklist entry to confirm before deleting, and confirm deletion afterward — the skill surfaces Delete actions without any verification guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary padding such as the marketing-style intro ('helps online businesses detect and prevent fraudulent transactions... minimize chargebacks'), the filler line 'Use action names and parameters as needed', and the large 60-line action-enumeration tree, fitting the 3-anchor for 'mostly efficient but could be tightened'.	3 / 5
Actionability	It provides copy-paste-ready commands for the full lifecycle (install, login, connection ensure, action list/run with --input JSON, request proxy) plus a flags table and popular-actions table, but examples use unresolved placeholders (CONNECTION_ID, <actionId>) without one fully resolved end-to-end example, matching the 4-anchor for 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connection workflow is well sequenced with explicit state checkpoints and a feedback loop (poll --wait, branch on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), but step labels are inconsistent ('#### 1b' with no 1a, references to an unlabeled 'Step 2') and destructive blacklist/delete operations lack verification guidance, keeping it at 4 rather than 5.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested/deep references and no bundle files to navigate, but the large inline action tree could be externalized into a reference file for a 200-line skill, so it sits at 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

48%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 correctly includes an explicit 'Use when...' trigger and names the specific product, but its capability statement is generic fluff ('Manage data, records, and automate workflows') with no concrete fraud-specific actions or synonyms. It is adequate but undersells the skill's actual capabilities.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions, e.g. 'Screen orders for payment fraud, manage email/card/IP blacklists and whitelists, and retrieve transaction risk results'.

Add natural trigger terms and synonyms beyond the product name, such as 'fraud detection', 'fraud screening', 'blacklist/whitelist checks', or 'chargeback prevention'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to screen transactions for fraud or manage FraudLabs Pro blacklists/whitelists'.

Dimension	Reasoning	Score
Specificity	It names the domain ('FraudLabs Pro integration') but the actions are generic — 'Manage data, records, and automate workflows' names no concrete fraud-specific operations like screening orders or checking blacklists, matching the 'names domain but actions minimal/generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It has an explicit 'Use when...' trigger ('when') but the 'what' is vague ('Manage data, records, and automate workflows') rather than concrete, so it falls below the 4-anchor which requires both a clear what and a when; the weak what lands it at 3.	3 / 5
Trigger Term Quality	The 'Use when the user wants to interact with FraudLabs Pro data' clause surfaces the product name as a keyword, but it lacks natural variations/synonyms users would say ('fraud detection', 'fraud screening', 'blacklist check', 'chargeback prevention'), fitting the 3-anchor for 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'FraudLabs Pro' gives it a clear niche with minimal conflict risk, but the generic 'manage data/records/workflows' phrasing is broad enough to risk minor overlap with other integration skills, so it sits at 4 rather than 5.	4 / 5
	Total	12 / 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/fraudlabs-pro/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.