CtrlK
BlogDocsLog inGet started
Tessl Logo

bankr

AI-powered crypto trading via natural language through Bankr API

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/bankr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 lean and highly actionable, packed with concrete commands and copy-paste example prompts across many use cases with no unnecessary concept explanations. Its main weakness is the absence of validation/verification checkpoints for destructive financial operations, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints before destructive actions, e.g. confirm recipient address and amount before transfers, and require balance checks before large trades.

Show the underlying Bankr API request (a curl or SDK example) so Claude can fall back to direct calls when the slash command is unavailable.

Condense the example categories or move less-common ones (Polymarket, Avantis leverage, raw transactions) behind a one-level-deep reference file.

DimensionReasoningScore

Conciseness

The body is almost entirely dense, copy-paste-ready examples with no padding or explanation of concepts Claude already knows; the only minor trim opportunity is the breadth of example categories, fitting 'Efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

Concrete commands (`/bankr <prompt>`, `/bankr status <jobId>`, `/bankr cancel <jobId>`) and many copy-paste example prompts are provided with an exact env-var setup, but the underlying API request mechanism is not shown, leaving a minor gap.

4 / 5

Workflow Clarity

A rough sequence exists (set key, run command, check job status) but destructive financial operations (trading, transfers, raw transactions, leverage) lack validation/verification checkpoints, so workflow clarity is capped at 3 per the destructive-operations rule.

3 / 5

Progressive Disclosure

Content is self-contained with clear section headers (Setup, Commands, Examples, Supported Chains, Tips) and no nested references; it is well-organized though slightly long, fitting 'Good structure; most content is appropriately placed'.

4 / 5

Total

15

/

20

Passed

Description

48%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 names a distinct niche (Bankr API for natural-language crypto trading), but it lacks concrete capability actions and any explicit 'Use when' trigger guidance. Adding specific operations and a trigger clause would lift the completeness and specificity scores.

Suggestions

Add 2-3 concrete actions, e.g. 'Buy, swap, bridge, and transfer crypto across chains via natural language'.

Append a 'Use when...' clause such as 'Use when the user wants to trade, swap, or transfer crypto through Bankr'.

Include natural trigger terms users actually say (buy ETH, swap tokens, DeFi, portfolio) to broaden keyword coverage.

DimensionReasoningScore

Specificity

The phrase "crypto trading via natural language" names the domain but the action is generic; no concrete operations (buy, swap, bridge, transfer) are listed, matching the anchor 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

It clearly states what the skill does (AI-powered crypto trading via Bankr API) but has no 'Use when...' trigger guidance, so per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"crypto trading" is a relevant natural keyword but common variations users say (buy ETH, swap tokens, DeFi, Bitcoin) are absent, fitting 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

Naming the specific "Bankr API" gives it a clear niche with low conflict risk, though the broad crypto-trading framing keeps minor overlap with generic trading skills, fitting 'Mostly distinct; minor overlap risk'.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alsk1992/CloddsBot
Reviewed

Table of Contents

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.