bankr

AI-powered crypto trading via natural language through Bankr API

Quality

30%

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 brief and vague to effectively guide skill selection. It relies on buzzwords ('AI-powered', 'natural language') without specifying concrete actions the skill performs, and completely lacks a 'Use when...' clause to help Claude know when to select it. The mention of 'Bankr API' provides some distinctiveness but the overall description needs significant improvement.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Place buy/sell orders, check portfolio balances, swap tokens, view price charts, set limit orders for cryptocurrencies through the Bankr API.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to trade crypto, buy/sell tokens, check crypto prices, manage a crypto portfolio, or mentions Bankr.'

Remove the buzzword 'AI-powered via natural language' as it adds no useful selection information, and replace with specific supported exchanges, tokens, or trading features.

Dimension	Reasoning	Score
Specificity	The description says 'AI-powered crypto trading via natural language' which is vague about what concrete actions the skill performs. It doesn't list specific capabilities like placing orders, checking balances, analyzing portfolios, or setting stop-losses.	1 / 3
Completeness	The description partially addresses 'what' (crypto trading via Bankr API) but is vague about specifics, and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'crypto trading', 'Bankr API', and 'natural language', but misses common user terms like 'buy', 'sell', 'swap', 'token', 'Bitcoin', 'Ethereum', 'portfolio', 'wallet', or specific crypto-related actions users would naturally say.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Bankr API' and 'crypto trading' provides some distinctiveness, but 'AI-powered' and 'natural language' are generic buzzwords that don't help differentiate. It could overlap with other crypto or trading skills.	2 / 3
	Total	6 / 12 Passed

Implementation

37%

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

The skill provides a broad catalog of example commands for crypto trading via Bankr, but critically lacks implementation details (how does Claude actually make API calls?), workflow safety measures for financial operations, and error handling guidance. The examples are illustrative but the skill reads more like user-facing documentation than an actionable guide for Claude to execute trades programmatically.

Suggestions

Add executable code showing how Claude should make HTTP requests to the Bankr API (endpoint URL, request format, authentication header, response parsing) rather than just listing slash commands.

Add a critical workflow with validation checkpoints for trades: check balance → preview trade → confirm → execute → verify status → handle errors. Financial operations without confirmation/validation steps are dangerous.

Clarify the execution model: are these slash commands for a specific MCP tool, CLI commands, or API calls? Claude needs to know the exact mechanism to use.

Move the extensive example categories (NFTs, Polymarket, Leverage, Token Deployment, etc.) to a separate reference file and keep only 3-4 representative examples in the main skill.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some content that could be tightened. The supported chains table and tips section add marginal value, and the sheer number of examples is somewhat redundant—Claude could infer many of these patterns from a few representative examples.	2 / 3
Actionability	The skill provides concrete command examples but lacks the actual API implementation details—there's no executable code showing how the /bankr command works under the hood (HTTP requests, response handling, job polling). It's unclear whether these are slash commands in a specific tool, CLI commands, or natural language prompts to an API endpoint.	2 / 3
Workflow Clarity	For a trading skill involving real financial transactions (destructive/irreversible operations), there are no validation checkpoints, confirmation steps, error handling, or feedback loops. The status/cancel commands are mentioned but not integrated into a workflow showing how to verify a trade before it executes or handle failures.	1 / 3
Progressive Disclosure	The content is organized into clear sections with headers, which is good. However, the extensive list of examples across 10+ categories makes this somewhat monolithic—the many example categories could be split into a separate EXAMPLES.md or COMMANDS.md reference file, keeping the main skill leaner.	2 / 3
	Total	7 / 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: e71a5f6

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