Name: finerio-connect
Rating: 55.2 (1 reviews)
Author: membranedev

finerio-connect

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

Quality

62%

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/finerio-connect/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 body is actionable and well-structured with concrete Membrane CLI commands and a clear connection-state workflow. The main weaknesses are some introductory padding and slightly thin error-recovery detail for failed connection states.

Suggestions

Trim the introductory paragraph about what Finerio Connect is and the 'focus on integration logic rather than auth plumbing' commentary to assume Claude's existing knowledge.

Add an explicit validation/retry loop for CONFIGURATION_ERROR and SETUP_FAILED states (inspect error, remediate, re-run connection ensure) to push workflow clarity toward level 5.

Standardize invocation (always `membrane` or always `npx @membranehq/cli`) to remove a minor actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Finerio Connect is and phrasing like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need, matching the level-3 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	It provides numerous concrete, executable commands (npm install, membrane login, connection ensure, action run, request) with flag tables and JSON examples; minor gaps like inconsistent membrane vs npx invocation and placeholder tokens keep it just below level 5.	4 / 5
Workflow Clarity	The install -> login -> ensure connection -> poll state -> search actions -> run/proxy sequence is clear, with an explicit state-feedback loop (BUILDING/READY/CLIENT_ACTION_REQUIRED) for re-authentication; it stops short of level 5 because error-recovery guidance for CONFIGURATION_ERROR is only 'check the error field' without a retry loop.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections (Overview, Working with, Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references and only a single external docs link; since no bundle files exist, structure alone places it at level 4 rather than 5 which expects well-signaled one-level-deep file references.	4 / 5
	Total	15 / 20 Passed

Description

57%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 the Finerio Connect niche and includes an explicit 'Use when' trigger, but its capability list is generic ('manage data, records, automate workflows') rather than concrete. Tightening the action verbs to specific operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Query users, accounts, and transactions; manage credit cards, loans, investments, and insurance via the Finerio Connect API'.

Expand the trigger phrase to name natural user intents and entity terms, e.g. 'Use when the user wants to query or update Finerio Connect financial data such as accounts, transactions, or credit cards'.

Add a file/extension or endpoint cue (e.g. '.json API responses' or 'REST endpoints') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('Finerio Connect integration') but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete capabilities; not the level-3 anchor which requires 1-2 concrete actions like 'extracts content'.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Finerio Connect data'); the 'when' is explicit but the 'what' is generic, so it does not reach the level-5 concrete-trigger standard.	4 / 5
Trigger Term Quality	It surfaces the relevant proper noun ('Finerio Connect') plus 'data', 'records', and 'workflows', but misses common variations/synonyms and file or endpoint references, matching the level-3 anchor of 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Finerio Connect' niche is specific with a distinct trigger, giving low conflict risk, but the generic 'Manage data, records, and automate workflows' phrasing leaves minor overlap with general data-management skills, fitting the level-4 'mostly distinct' anchor.	4 / 5
	Total	13 / 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/finerio-connect/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.