Name: fintoio
Rating: 56.8 (1 reviews)
Author: membranedev

fintoio

Finto.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Finto.io 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/fintoio/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 highly actionable with executable CLI commands and a well-structured connection state machine, but loses points to redundant sections, inferable background, and a dangling 'Step 2' reference.

Suggestions

Remove the 'Popular actions' section or fold it into 'Searching for actions' to eliminate the duplicated action-list command.

Delete inferable background ('Finto.io is a financial data aggregation platform...') and padding phrases to tighten token efficiency.

Fix the 'skip to Step 2' reference by labeling the post-connection sections as Step 2, or remove the cross-reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes background Claude could infer ('Finto.io is a financial data aggregation platform...'), padding ('so you can focus on the integration logic rather than auth plumbing'), and a redundant 'Popular actions' section that repeats the earlier action-list command.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests plus a flags table; minor gaps such as no example of parsing JSON output keep it from a 5.	4 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and feedback loops (poll again after user action), but the 'skip to Step 2' reference dangles with no labeled Step 2.	4 / 5
Progressive Disclosure	Single SKILL.md with no bundle files, organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); content is reasonably placed though the connection state-machine detail and proxy table are inline rather than split out.	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 answers both what and when and is anchored to a distinct product, but its action verbs are generic and it lacks the natural trigger-term coverage of stronger examples.

Suggestions

Replace generic verbs ('Manage data, records') with concrete capabilities (e.g., 'query transactions, categorize records, build automation rules').

Expand the trigger phrase to include natural variations users would say (e.g., 'Use when the user wants to query, categorize, or automate Finto.io financial data').

Add file-format or entity keywords (transactions, categories, rules) to improve trigger-term distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the Finto.io domain and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage') rather than concrete like 'extract' or 'create', so coverage is not comprehensive.	3 / 5
Completeness	Both 'what' (Finto.io integration; manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Finto.io data') are present, though the when clause could be more specific.	4 / 5
Trigger Term Quality	Includes the product name 'Finto.io' and a use-when phrase ('interact with Finto.io data'), but lacks common variations, synonyms, or concrete trigger phrases a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named product (Finto.io) giving it a clear niche with minimal conflict risk, though the generic 'manage data' framing leaves minor overlap with other data skills.	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/fintoio/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.