CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

whale-tracking

Monitor whale trades on Polymarket and crypto chains (Solana, ETH, Polygon, ARB, Base, OP)

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/whale-tracking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 a highly actionable, executable API reference with lean, comment-driven code and no fluff, but it is monolithic: everything lives inline in SKILL.md with no progressive disclosure to reference files, and no explicit workflow sequence or validation checkpoints. Splitting the API reference into separate files and adding a quick-start workflow with API-key/connection validation would raise the weaker dimensions.

Suggestions

Move the full TypeScript API reference and command catalog into separate files (e.g. references/api.md, references/commands.md) and keep a concise quick-start in SKILL.md with clearly signaled one-level-deep links.

Add an explicit usage sequence (create tracker → set thresholds → start → handle events → stop) with a validation step for API keys before starting, since the gates env vars are only listed in frontmatter.

Include error-recovery guidance for dropped WebSocket connections or rate limits so the monitoring workflow has feedback loops.

DimensionReasoningScore

Conciseness

The body is a lean reference: code examples carry inline comments instead of explanatory prose, and there is no padding or explanation of concepts Claude already knows. It is not 5 because of minor trimmable redundancy, e.g. the duplicated watch/track and unwatch/untrack command pairs ('same as track') and a long inline API catalog.

4 / 5

Actionability

The TypeScript examples are complete and copy-paste ready — imports ('clodds/feeds/polymarket/whale-tracker'), tracker creation with real option values, event handlers, start/stop lifecycle, wallet tracking, alerts, and CSV/JSON export — and the chat commands cover the common cases with arguments. This matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases.'

5 / 5

Workflow Clarity

There is no explicitly sequenced workflow; the create → attach handlers → start → stop lifecycle is only implicit in the code, and validation checkpoints (e.g. verifying API keys exist before start, handling dropped WebSocket connections) are absent. It is not 2 because the code examples do convey a coherent rough sequence.

3 / 5

Progressive Disclosure

The ~280-line body has clear section headers, but the entire TypeScript API reference, command catalog, alert configuration, and export docs are inlined with no bundle files (no references/, scripts/, or assets/ exist) to split the detail into. This matches 'content that should be separate is inline'; it is not 2 because the section structure itself is good, and not 4 because nothing is offloaded to separate files.

3 / 5

Total

15

/

20

Passed

Description

61%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 has a clear, concrete 'what' with strong platform enumeration and good natural keywords, but it lists only one action and completely lacks a 'when to use' clause. Adding an explicit trigger clause and mentioning the wallet-tracking/alerting capabilities would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions whale activity, whale wallets, large on-chain transfers, or asks about big Polymarket traders.'

Enumerate more concrete capabilities: tracking specific wallets, real-time alerts, whale positions/P&L, and top/profitable trader leaderboards.

Include common user phrasings like 'whale alert', 'smart money', and 'on-chain whales' to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

"Monitor whale trades" is a single concrete action, and while the platforms are enumerated in detail ("Polymarket and crypto chains (Solana, ETH, Polygon, ARB, Base, OP)"), the description never mentions the skill's other capabilities such as wallet tracking, alerts, positions, or data export. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which requires several specific actions.

3 / 5

Completeness

The 'what' is clear ("Monitor whale trades on Polymarket and crypto chains") but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

"Whale trades", "Polymarket", and the chain names/tickers ("Solana, ETH, Polygon, ARB, Base, OP") are natural terms a user would say when needing this skill. It falls short of 5 because common variations like "whale alerts", "track whale wallets", "on-chain", or "large transactions" are missing.

4 / 5

Distinctiveness Conflict Risk

"Whale trades on Polymarket and crypto chains" carves out a fairly distinct niche unlikely to trigger for unrelated skills. It is not 5 because a general Polymarket-trading or crypto-monitoring skill would have minor overlap risk since the description lacks distinct trigger phrases like 'when the user mentions whale activity'.

4 / 5

Total

14

/

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.

Validation — 15 / 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

Path

src/skills/bundled/whale-tracking/SKILL.md

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.