Name: even-financial
Rating: 56.8 (1 reviews)
Author: membranedev

even-financial

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

Quality

65%

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/even-financial/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 a well-structured, highly actionable integration guide anchored in concrete Membrane CLI commands and a robust connection workflow with feedback loops. Its main weaknesses are prose padding and a 'Popular actions' section that names no actual actions.

Suggestions

Trim explanatory prose such as the introductory 'Even Financial is a search, comparison, and recommendation engine...' paragraph and the 'auth plumbing' sentence, keeping only what Claude cannot infer.

Populate the 'Popular actions' section with 2-3 concrete example actions (e.g., list offers, fetch user details, submit application) instead of only restating the discovery command.

Move the proxy flag reference table and the full clientAction state-handling detail into a separate reference file (e.g., references/CONNECTIONS.md) and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes several padded prose sections (the introductory paragraph on what Even Financial is, 'Membrane handles authentication...so you can focus on integration logic rather than auth plumbing', and the filler line 'When to use which actions: Use action names and parameters as needed'), matching the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	It provides copy-paste-ready bash commands for login, connection ensure, polling, action list/run, and a proxy flag table, but the 'Popular actions' section paradoxically lists no actual actions and only repeats the discovery command, leaving a minor gap below the score-5 anchor.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with a polling feedback loop and explicit state handling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but action execution lacks an explicit output-verification checkpoint, keeping it just below the score-5 anchor.	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references and no bundle files present, but reference-worthy detail (the proxy flag table, full clientAction state handling) is inlined in a SKILL.md over 50 lines rather than split into separate files, matching 'good structure with minor organization gaps'.	4 / 5
	Total	15 / 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 correctly identifies a specific niche (Even Financial) and includes both a 'what' and a 'when' clause, but its action verbs are generic and it lacks richer trigger-term variations. It is solid but not exemplary.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Even Financial capabilities (e.g., 'search and compare loan, credit card, and insurance offers, retrieve user and application details').

Expand the trigger phrase to mention natural user cues such as 'financial product offers', 'loan offers', or 'credit card recommendations' rather than only 'Even Financial data'.

Add concrete trigger terms or file/API extensions to lift trigger-term quality toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Even Financial integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	Both 'what' (Even Financial integration; manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Even Financial data') are present, with the 'when' reasonably explicit but not enriched with concrete trigger phrases, matching the score-4 anchor.	4 / 5
Trigger Term Quality	'Even Financial' is a natural proper-noun trigger a user would say, but the description lacks synonyms or common variations beyond the single product name and 'data', matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Even Financial' is a specific named product giving it a clear niche and minimal conflict risk, though the generic 'manage data, records, automate workflows' verbs leave minor overlap risk, so it sits just below the score-5 anchor.	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/even-financial/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.