Name: maxmind-minfraud
Rating: 63.2 (1 reviews)
Author: membranedev

maxmind-minfraud

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

Quality

75%

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

Quality

Content

88%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 highly actionable with executable commands and a well-sequenced, validation-checked connection workflow. The main improvement is trimming background explanation and considering splitting the proxy/options reference into a separate file.

Suggestions

Remove the opening minFraud overview paragraph ('MaxMind minFraud is a service that helps businesses prevent online fraud...') — Claude already knows this and it adds tokens without actionability.

Trim editorializing like 'so you can focus on the integration logic rather than auth plumbing' to keep the prose lean.

Consider moving the proxy request flags table into a references file (e.g. references/proxy.md) and signaling it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout, but includes a background overview paragraph explaining what minFraud is and some editorializing ('so you can focus on the integration logic rather than auth plumbing') that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, action list/run with JSON input, and proxy requests with a clear flags table, covering the common cases and noting where the result appears.	5 / 5
Workflow Clarity	Clear sequence (install → login → ensure connection → poll for READY) with explicit state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and feedback loops for re-polling after user action and error recovery.	5 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear section headers and no nested references; no bundle files exist so one-level references aren't required, though the proxy flags table and popular-actions detail could be split out for tighter navigation.	4 / 5
	Total	18 / 20 Passed

Description

61%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 its niche and includes an explicit 'Use when' trigger, but its capability phrasing is generic rather than concrete minFraud actions. Strengthening the action list with specific fraud-scoring terms would lift specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete minFraud actions such as 'score transactions for fraud risk, retrieve risk scores and factors, and submit minFraud queries'.

Add natural trigger terms users say beyond the product name — e.g. 'fraud', 'risk score', 'transaction risk', 'chargeback risk'.

Tighten the 'when' clause to specific intents, e.g. 'Use when the user wants to score a transaction's fraud risk or query minFraud data'.

Dimension	Reasoning	Score
Specificity	Names the MaxMind minFraud domain but the actions ('Manage data, records, and automate workflows') are generic and not concrete minFraud-specific operations like scoring transactions or checking fraud risk.	2 / 5
Completeness	Provides a 'what' ('MaxMind minFraud integration... manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with MaxMind minFraud data'), though the 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes the natural product name 'MaxMind minFraud' plus 'data' and 'records', but misses common variations and synonyms a user would say such as 'fraud', 'risk score', or 'transaction'.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (MaxMind minFraud) with a distinct trigger ('interact with MaxMind minFraud data'), giving minimal conflict risk with other skills.	5 / 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/maxmind-minfraud/SKILL.md
Commit: f484c82

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