Name: findity
Rating: 60 (1 reviews)
Author: membranedev

findity

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

Quality

70%

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/findity/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 highly actionable with executable commands and a well-validated connection workflow, and is reasonably well-structured for a single-file skill. It loses points mainly on minor verbosity and a couple of organizational rough edges rather than on substance.

Suggestions

Remove filler phrases ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') to tighten token usage.

De-duplicate the action-discovery instructions: keep one canonical `membrane action list` example instead of restating it in both 'Searching for actions' and 'Popular actions'.

Fix the step numbering in the connection flow (give it a proper 'Step 1' header and renumber '1b') so the sequence reads cleanly.

Fill or remove the empty 'Findity Overview' placeholder bullets under that heading.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and tables, but includes some padding that could be trimmed ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and repeats the `action list` command across 'Searching for actions' and 'Popular actions'.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands for every stage — install, login, connection ensure/get with --wait, action list/run, and request — plus a complete flag table, covering the common cases the rubric's level-5 anchor requires.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit validation via state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-until-ready feedback loop, but the step numbering is slightly jumbled ('Step 2', '1b' without a matching 'Step 1' header), a minor organizational gap.	4 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md is scored on its own structure; it has clear, well-ordered sections (Install, Authentication, Connecting, Searching, Proxy, Best practices), with minor gaps like the empty 'Findity Overview' placeholder bullets and the duplicated action-discovery sections.	4 / 5
	Total	16 / 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 is structurally complete with an explicit 'Use when' clause and a distinct named-app trigger, but its capability language is generic and its trigger vocabulary is thin beyond the product name. Tightening the action list and adding concrete user-facing trigger phrases would lift it toward the top anchors.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Findity operations such as 'submit and approve expense reports, extract receipt data, export records'.

Expand the trigger clause with natural phrasings users actually say, e.g. 'Use when the user wants to submit expenses, track receipts, or query Findity records'.

Add file-format or object synonyms (e.g. 'expense reports, receipts') so the trigger fires on common variations.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Findity domain plus a couple of actions, but those actions are generic ('manage data', 'manage records') rather than the specific concrete operations the rubric's level-4/5 anchors require.	3 / 5
Completeness	It states a clear 'what' (Findity integration managing data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Findity data'), but the 'when' is fairly generic and could name concrete trigger phrases, fitting the 'has both what and when; when could be more specific' anchor.	4 / 5
Trigger Term Quality	The only genuinely natural keyword is 'Findity' (in 'interact with Findity data'); the description misses common variations or synonyms a user might say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Findity' gives it a clear niche with a distinct trigger and minimal overlap risk with other skills.	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/findity/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.