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

Blog Docs Log in Get started

banked

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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/banked/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 copy-paste CLI commands and a clear state-driven connection workflow including validation and retry loops. It is concise and well-structured, with only minor prose padding and a dangling "Step 2" reference.

Suggestions

Define or relabel the referenced "Step 2" (e.g. add a "## Step 2: Search and run actions" heading) so the cross-reference resolves.

Trim incidental padding such as "so you can focus on the integration logic rather than auth plumbing" to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable commands with only minor over-explanation (e.g. "so you can focus on the integration logic rather than auth plumbing"), fitting the efficient score-4 anchor rather than the padded 2-3 anchors.	4 / 5
Actionability	It provides copy-paste-ready CLI commands for every key operation (login, connection ensure, action list/run, request proxy) plus a flag options table, matching the fully-executable score-5 anchor.	5 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence includes state-based validation checkpoints and a retry-after-action feedback loop, but the referenced "Step 2" is unlabeled, leaving a minor gap below score 5.	4 / 5
Progressive Disclosure	The single self-contained file is well-organized into clearly headed sections with no nested external references, but at ~140 lines with inline reference material it sits just below the ideal score-5 structure.	4 / 5
	Total	17 / 20 Passed

Description

57%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 covers both what the skill does and when to use it with an explicit trigger clause, but the stated capabilities are generic and the trigger phrasing lacks natural synonyms. It is distinct thanks to the named product but could be sharper.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Banked-specific actions such as initiating payments, retrieving transaction history, or managing budgets.

Broaden the trigger clause to include natural user phrasings and synonyms, e.g. "Use when the user wants to pay via bank transfer, check Banked transactions, or manage Banked data."

Dimension	Reasoning	Score
Specificity	Names the domain (Banked) but the actions listed — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete capabilities, matching the score-2 anchor.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when" clause are present, though the "when" is generic rather than specific, fitting the score-4 anchor and not the 5 above.	4 / 5
Trigger Term Quality	The trigger phrase "interact with Banked data" includes the relevant product keyword but lacks common variations or synonyms a user might naturally say, matching the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Banked" gives it a clear niche with minor overlap risk, but the generic trigger phrasing keeps it just below the fully-distinct score-5 anchor.	4 / 5
	Total	13 / 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/banked/SKILL.md
Commit: f484c82

Reviewed: ~1 hour 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.