Name: finmei
Rating: 58.4 (1 reviews)
Author: membranedev

finmei

Finmei integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Finmei data.

Quality

67%

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

Quality

Content

61%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.

A well-structured, actionable CLI integration guide with strong connection-setup sequencing, but it is padded in places, inlines bulk reference content, and lacks validation steps for the destructive create/update/delete actions it exposes.

Suggestions

Add an explicit validation/verification step to the 'Running actions' workflow for destructive operations (e.g., confirm before delete, check the `output` and error fields after create/update/delete) so the feedback loop is complete.

Trim filler phrases such as "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", and "Use action names and parameters as needed." to improve token efficiency.

Move the 20-row 'Popular actions' table into a separate reference file (e.g. references/actions.md) and link to it from the body, keeping only a few representative examples inline.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it carries several padded phrases ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", "Use action names and parameters as needed.") and an inline 20-row actions table that could be tightened.	3 / 5
Actionability	Concrete, executable commands cover the common cases (install, login, connect, wait, action list/run, proxy) with options tables, but placeholders like CONNECTION_ID and <actionId> require substitution and there is no fully-worked end-to-end example with real values.	4 / 5
Workflow Clarity	The connection setup is well-sequenced with explicit state checkpoints and a poll-again feedback loop, but the Create/Update/Delete actions are destructive/batch operations with no validation or verification step, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist; the single ~178-line file is organized into clear, navigable sections, with the main gap being the inline 20-row Popular actions reference table that could be split into a separate file.	4 / 5
	Total	14 / 20 Passed

Description

73%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.

A solid, third-person description that explicitly pairs a "what" with a "Use when" trigger and stakes out a distinct brand niche. Its main weakness is the single generic verb "Manage" applied to many entities, which limits the specificity of the named capabilities.

Dimension	Reasoning	Score
Specificity	The description names five entities (Organizations, Pipelines, Users, Goals, Filters) but relies on a single generic verb ("Manage") repeated across all of them, so the action repertoire is minimal rather than a set of distinct concrete actions.	3 / 5
Completeness	Both "what" ("Manage Organizations, Pipelines, Users, Goals, Filters") and an explicit "when" ("Use when the user wants to interact with Finmei data") are present, but the trigger phrase is somewhat generic rather than listing concrete entity-level triggers.	4 / 5
Trigger Term Quality	Natural brand keyword "Finmei" and "Finmei data" are present, plus entity terms (Organizations, Pipelines, Users, Goals, Filters) users would plausibly say, giving good coverage with only minor variations missing.	4 / 5
Distinctiveness Conflict Risk	"Finmei integration" carves out a clear brand niche with a distinct trigger ("Finmei"), leaving minimal risk of activating for an unrelated skill.	5 / 5
	Total	16 / 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/finmei/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.