bankr

AI-powered crypto trading via natural language through Bankr API

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/bankr/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague and lacks the specificity needed for Claude to reliably select it. It fails to list concrete actions (what trading operations are supported), omits trigger guidance entirely, and relies on buzzwords like 'AI-powered' without substance.

Suggestions

Add specific concrete actions like 'Execute buy/sell orders, check portfolio balances, view price charts, set limit orders'

Include a 'Use when...' clause with natural trigger terms like 'Use when the user wants to trade cryptocurrency, buy/sell Bitcoin, check crypto prices, or manage their Bankr portfolio'

Add common keyword variations users would say: 'cryptocurrency', 'bitcoin', 'ethereum', 'buy crypto', 'sell crypto', 'crypto portfolio'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'AI-powered' and 'natural language' without listing any concrete actions. It doesn't specify what trading operations are supported (buy, sell, analyze, portfolio management, etc.).	1 / 3
Completeness	The description only vaguely addresses 'what' (crypto trading) and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('crypto trading', 'Bankr API') that users might mention, but misses common variations like 'cryptocurrency', 'bitcoin', 'trade', 'buy crypto', 'sell crypto', or specific coin names.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Bankr API' provides some distinctiveness, but 'crypto trading' is broad enough to potentially conflict with other cryptocurrency or trading-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted skill that excels at conciseness and actionability with extensive, concrete examples covering diverse crypto operations. The main weakness is the lack of explicit validation workflows for financial operations - there's no guidance on verifying trades succeeded, handling failures, or recommended confirmation steps before executing high-value transactions.

Suggestions

Add a workflow section showing the recommended pattern: execute trade -> check status -> verify completion, especially for high-value operations

Include guidance on error handling and what to do when a job fails or times out

Add a note about using /bankr status <jobId> after trades to confirm execution before proceeding

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient - no unnecessary explanations of what crypto trading is or how APIs work. Every section provides direct, actionable information without padding.	3 / 3
Actionability	Highly actionable with concrete command syntax and extensive real-world examples covering trading, portfolio, NFTs, leverage, automation, and more. Copy-paste ready commands throughout.	3 / 3
Workflow Clarity	While individual commands are clear, there's no validation workflow for financial operations. Missing guidance on checking job status after trades, no explicit feedback loop for failed transactions, and no verification steps before executing potentially costly operations.	2 / 3
Progressive Disclosure	Well-organized with clear sections (Setup, Commands, Examples by category, Supported Chains, Tips). Appropriate length for a skill file without needing external references. Easy to scan and navigate.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

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