Name: flinks
Rating: 64 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

flinks

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

Quality

76%

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/flinks/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 a well-organized, highly actionable CLI integration guide with executable commands and a clear connection state machine including validation and a feedback loop. The only meaningful gaps are minor verbosity and the absence of explicit error-recovery guidance for action execution.

Suggestions

Trim editorializing prose such as 'so you can focus on the integration logic rather than auth plumbing' to tighten conciseness.

Add an explicit feedback loop for action execution (e.g. what to do when `membrane action run` returns an error or partial output) to raise workflow clarity.

Consider moving the proxy flag table and action-discovery details into a references file to keep SKILL.md a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is largely command-focused and efficient with copy-paste CLI snippets, but contains a few editorializing lines (e.g. 'so you can focus on the integration logic rather than auth plumbing') that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands covering the common cases — install, login, connection ensure, action list/run with JSON input, and the proxy request with a complete flag table — matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connect → poll → handle-state → search → run sequence is clear with explicit validation via the READY/BUILDING/CLIENT_ACTION_REQUIRED state enum and a poll-again feedback loop, but there is no explicit recovery guidance for action-execution failures, leaving it just short of the score-5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-sectioned (Overview, Auth, Connecting, Searching, Proxy, Best practices) with no nested references, giving good structure; at ~140 lines it is slightly long for one file, so it sits at the score-4 'good structure, minor organization gaps' anchor rather than score 5.	4 / 5
	Total	17 / 20 Passed

Description

70%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 a solid, third-person statement that covers both what the skill does and when to use it, anchored by the distinctive Flinks product name. Its main weakness is generic verb choice ('manage', 'automate') and a trigger clause that lacks concrete financial-data scenarios.

Suggestions

Replace generic verbs with concrete Flinks actions, e.g. 'Connect bank accounts, fetch balances and transactions, and generate income-verification reports' to lift specificity.

Tighten the 'Use when' clause with concrete triggers like 'Use when the user wants to access bank accounts, balances, or transactions via Flinks, or needs income verification or credit-risk data.'

Add domain synonyms (financial data, bank data) to the description so the trigger fires on natural user phrasing beyond the product name.

Dimension	Reasoning	Score
Specificity	Names the Flinks domain and several action areas ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete operations, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor better than the score-2 minimal-action anchor.	3 / 5
Completeness	Both 'what' (Flinks integration managing data/records/workflows) and 'when' (use when interacting with Flinks data) are present, but the trigger clause is somewhat generic rather than tied to concrete scenarios, matching the score-4 anchor rather than the fully explicit score-5 anchor.	4 / 5
Trigger Term Quality	Includes the natural product term 'Flinks' and 'Flinks data' with an explicit trigger ('Use when the user wants to interact with Flinks data'); coverage is good though no synonyms or file extensions exist for this named API, so it stops short of the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	'Flinks' is a distinct proper-noun product giving it a clear niche with low conflict risk, but the surrounding action language ('manage data, records') is generic enough to leave minor overlap risk, placing it at the score-4 anchor rather than the minimal-conflict score-5 anchor.	4 / 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/flinks/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.