Name: fintechos
Rating: 62.4 (1 reviews)
Author: membranedev

fintechos

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

Quality

74%

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

Quality

Content

82%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 executable commands throughout and a well-sequenced connection workflow including state checkpoints and a retry loop. It is mildly held back by a few padded prose lines and a couple of inline reference-like dumps that could be tightened or split out.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, command-driven content with a flags table, but the opening platform description and phrases like 'so you can focus on the integration logic rather than auth plumbing' are minor over-explanation that could be trimmed, matching the 4-anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, poll, action list/run, request proxy) plus a flags table, fully matching the 'executable; copy-paste ready' 5-anchor.	5 / 5
Workflow Clarity	There is a clear sequence (install -> authenticate -> connect -> poll for READY -> handle clientAction -> search/run) with state-based checkpoints and a feedback loop (poll again after user action), but 'Step 2' is referenced without a labeled heading and steps are spread across prose sections, fitting anchor 4 rather than a fully explicit checklist.	4 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and is organized into clear sections (Overview, Working with FintechOS, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices); minor gaps such as the inline clientAction schema dump and entity list keep it at 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

66%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 with an explicit 'Use when...' clause and is highly distinctive thanks to the named FintechOS platform. It is held back from the top by generic action verbs and limited trigger-term coverage beyond the product name.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Create and update records, query accounts and contracts, and automate FintechOS workflows.'

Broaden the 'when' clause to match the stated capabilities, e.g. 'Use when the user wants to query, create, or update FintechOS data, records, or automate workflows.'

Add a couple of natural synonyms users might say (e.g. 'FintechOS accounts', 'FintechOS contracts', 'FintechOS processes') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the FintechOS domain and a couple of actions ('Manage data, records, and automate workflows'), but the verbs are generic and coverage is not comprehensive, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It states a clear 'what' ('FintechOS integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with FintechOS data.'), but the 'when' only references 'data' and could be more specific, matching anchor 4 rather than the fully-concrete 5.	4 / 5
Trigger Term Quality	The product name 'FintechOS' is a strong natural trigger and 'data', 'records', 'workflows' add some coverage, but common variations/synonyms are missing, fitting the 'some relevant keywords but missing variations' anchor rather than the 4-anchor's fuller coverage.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named platform 'FintechOS' gives it a clear niche with distinct triggers and minimal conflict risk, matching the 5-anchor.	5 / 5
	Total	15 / 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/fintechos/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.