Name: fintechblocks
Rating: 59.2 (1 reviews)
Author: membranedev

fintechblocks

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

Quality

68%

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

Quality

Content

75%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 strong, action-oriented guide with executable commands and a well-validated connection workflow. Its main weakness is an unnecessary marketing intro and the absence of validation guidance for destructive action/proxy calls.

Suggestions

Cut the introductory 'FintechBlocks is a platform...' paragraph and the 'Fintech companies and traditional businesses...' sentence; keep only the docs URL.

Add a brief validation/confirmation step before running mutating actions or proxy POST/PUT/PATCH/DELETE requests (e.g., confirm the action's effect on data/records before executing).

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but the opening paragraph ('FintechBlocks is a platform that provides pre-built UI blocks and APIs... Fintech companies and traditional businesses entering the fintech space use it.') is background/marketing fluff Claude doesn't need to use the skill, matching 'mostly efficient but includes some unnecessary explanation'; not a 4 because that padding is more than minor.	3 / 5
Actionability	Provides copy-paste-ready commands for the full workflow (install, login, connection ensure, action list/run with JSON input, proxy with a detailed flags table), covering common cases with concrete examples; matches 'fully executable; copy-paste ready'.	5 / 5
Workflow Clarity	Clear sequence (install → auth → connect → poll for READY → search → run) with explicit state validation (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a retry feedback loop when polling, matching 'clear sequence with most checkpoints'; not a 5 because there is no validation/confirmation guidance before running potentially destructive actions or proxy mutations.	4 / 5
Progressive Disclosure	Well-organized with clear section headers (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no nested references; matches 'good structure; most content appropriately placed'; not a 5 because the proxy flags table and detail could arguably live in a separate reference, though inline is defensible.	4 / 5
	Total	16 / 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 names a specific platform and includes a usable Use-when clause, giving it decent completeness and distinctiveness, but the capabilities are generic and trigger-term coverage is thin. Tightening the action verbs and adding concrete trigger phrases would raise it.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete FintechBlocks actions (e.g., 'list transactions, manage API keys, query users, automate workflows').

Expand the Use-when clause with concrete trigger phrases users would say (e.g., 'Use when the user mentions FintechBlocks, fintech blocks, payments, KYC, or banking integrations').

Dimension	Reasoning	Score
Specificity	Names the FintechBlocks domain and a few actions ('Manage data, records, and automate workflows'), but these are generic rather than concrete capabilities, matching the '1-2 concrete actions, not comprehensive' anchor; not a 4 because the actions lack specifics like the PDF example's 'extract, fill, merge'.	3 / 5
Completeness	States what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with FintechBlocks data'), matching 'has both what and when; when could be more explicit'; not a 5 because the when-clause trigger is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The only trigger keyword is 'FintechBlocks data' with no natural synonyms or variations, matching 'some relevant keywords but missing common variations'; not a 4 because coverage is thin with no alternative phrasings.	3 / 5
Distinctiveness Conflict Risk	The named FintechBlocks platform gives it a clear niche with low conflict risk, matching 'mostly distinct; minor overlap risk'; not a 5 because the generic action verbs ('manage data, records') could overlap with adjacent 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/fintechblocks/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.