Name: enfuce
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

enfuce

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

Quality

60%

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

Quality

Content

57%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 concrete Membrane CLI commands and a clear connection-state workflow, but it is held back by marketing-style padding, a lack of validation checkpoints for destructive/batch data operations, and an all-inline structure with no reference split-out.

Suggestions

Trim the introductory Enfuce marketing paragraph to one factual line about what the platform is, since Claude does not need the user-base context.

Add an explicit validation/verification step (e.g. dry-run or check the output field and confirm counts) before running actions that mutate records or settlements.

Move the proxy-flag reference table and agent-type list into a separate REFERENCE.md, linking to it from the main body to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands, but opens with marketing-flavored context ('It helps businesses launch and manage their own payment cards... Fintech companies... are their primary users') that pads rather than instructs; fits 'mostly efficient but includes some unnecessary explanation' rather than the leaner 4.	3 / 5
Actionability	Concrete, executable `membrane` commands with flags, --json output, and JSON input examples cover the common cases (login, connection ensure, action list/run, request proxy); minor gaps like placeholder actionIds keep it just short of fully copy-paste-ready 5.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with state polling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a --wait feedback loop, but because this skill manages records and can drive destructive or batch actions with no explicit validation/verification step before running them, workflow clarity is capped at 3 per the batch/destructive guideline.	3 / 5
Progressive Disclosure	The body is organized into clear sections (install, auth, connecting, actions, proxy, best practices) with no nested references, but it is a single ~100-line monolith with inline content like the proxy-flag table and agent-type list that could live in separate files; fits 'some structure but could be better organized' rather than the well-split 4.	3 / 5
	Total	13 / 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 third-person, names the Enfuce domain, and includes an explicit 'Use when' trigger, giving it solid completeness and distinctiveness. It is held back by generic actions and limited keyword variation rather than Enfuce-specific capability language.

Suggestions

Replace generic verbs with Enfuce-specific capabilities, e.g. 'Enfuce integration. Issue and manage payment cards, query transactions and chargebacks, and reconcile settlements.'

Broaden the trigger clause with natural synonyms, e.g. 'Use when the user wants to work with Enfuce cardholder, transaction, or settlement data.'

Dimension	Reasoning	Score
Specificity	It names the Enfuce domain and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete Enfuce-specific operations, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor; not a 2 because real named actions exist, not a 4 because they lack specifics.	3 / 5
Completeness	It states both what ('Enfuce integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Enfuce data'), but the 'when' clause is somewhat narrow and could be more explicit; matches the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	Relevant keywords like 'Enfuce', 'data', and 'records' appear with an explicit 'Use when the user wants to interact with Enfuce data' trigger, but common variations or synonyms are missing; fits the 'some relevant keywords but missing common variations' anchor rather than the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	The Enfuce-specific name gives it a clear niche with low conflict risk, though the generic 'manage data, records, automate workflows' phrasing could lightly overlap with other data skills; fits 'mostly distinct; minor overlap risk' rather than the fully-niche 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/enfuce/SKILL.md
Commit: f484c82

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