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

Blog Docs Log in Get started

tink

Tink integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tink 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/tink/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 an efficient, actionable guide with concrete Membrane CLI commands and a clear connection-state workflow including a polling feedback loop; its main gaps are a redundant action-list section and no explicit post-action verification step.

Suggestions

Consolidate the duplicate action-list command in 'Searching for actions' and 'Popular actions' into one section to save tokens.

Add a verification step after running actions, e.g. checking the output/error fields and re-polling on transient failures, to strengthen the workflow's feedback loop.

Consider moving the proxy flag reference table and per-action input/output schema details into a separate reference file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and minimal concept-explanation padding; the main redundancy is the repeated action-list command in both 'Searching for actions' and 'Popular actions', which keeps it just below the lean 5 anchor.	4 / 5
Actionability	Provides concrete, copy-pasteable CLI commands with flags (login, connection ensure, action run, request) and a flag table, covering common cases; minor gaps like placeholder CONNECTION_ID keep it at 4 rather than fully executable across all cases at 5.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with a state-polling feedback loop (BUILDING -> READY / CLIENT_ACTION_REQUIRED -> re-poll) and explicit 'skip to Step 2' guidance; it lacks a final verification checkpoint after action execution, so it does not reach the explicit-validation 5 anchor.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and all content at one level with no nested references; since there are no bundle files and the document is well structured, it scores 4 with only minor organization gaps (e.g. the proxy flag table and action schemas could live in reference files).	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 is concise and third-person with an explicit 'Use when' trigger, but its capability list is generic ('manage data, records') rather than concrete Tink-specific actions, and trigger terms lack natural variations.

Suggestions

Replace generic verbs with concrete Tink capabilities, e.g. 'List accounts and transactions, fetch balances, categorize transactions, and retrieve payment data'.

Broaden trigger terms with natural user phrasings like 'Tink accounts', 'bank transactions', 'payment data', or 'financial data'.

Tie the 'Use when' clause to concrete user intents such as 'Use when the user wants to query Tink account/transaction data or automate financial-data workflows'.

Dimension	Reasoning	Score
Specificity	Names the Tink domain plus a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the 'names domain and 1-2 concrete actions' anchor and falling short of the multiple-specific-actions anchor at 5.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Tink data') are present; the trigger could be more specific with concrete phrases, fitting the 4 anchor rather than the fully-explicit 5.	4 / 5
Trigger Term Quality	Includes 'Tink data' and 'Tink integration' as relevant keywords but lacks common synonyms or variations a user would naturally say, matching the 'some relevant keywords but missing common variations' anchor rather than the comprehensive coverage at 5.	3 / 5
Distinctiveness Conflict Risk	'Tink integration' is a clear niche tied to a specific platform with low overlap risk, but the generic 'data' and 'records' wording leaves minor overlap with general data skills, placing it just below the minimal-conflict 5 anchor.	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/tink/SKILL.md
Commit: f484c82

Reviewed: 4 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.