CtrlK
BlogDocsLog inGet started
Tessl Logo

dca

Dollar-cost averaging across all platforms

55

Quality

63%

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/dca/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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, well-structured, and provides fully executable commands, but it presents only a command menu with no workflow sequence or validation checkpoints for what is inherently a batch/recurring operation. Adding guidance on verifying orders and handling failures would materially improve it.

Suggestions

Add a short workflow section: create an order, confirm it via '/dca list' or '/dca info <id>', then verify fills/balances before walking away.

Include validation/error-recovery guidance (e.g., what to check when an order fails or a platform rejects a recurring buy), since DCA is a batch operation that runs unattended.

Document how intervals and per-order sizes interact with the total budget so users can sanity-check a schedule before starting.

DimensionReasoningScore

Conciseness

The body is a lean one-sentence intro plus a command table with no over-explanation of what DCA is or how the platforms work, matching the score-5 anchor "Lean and efficient; assumes Claude's competence; every token earns its place."

5 / 5

Actionability

Commands are fully executable and copy-paste ready with explicit placeholders (e.g. '/dca poly <token-id> <total-$> --per <$> --every <interval>'), matching the score-5 anchor for concrete, executable guidance.

5 / 5

Workflow Clarity

DCA places recurring orders (a batch operation), but the body is only a command menu with no sequenced workflow and no validation/verification checkpoints; the rubric caps batch skills without validation at 3, and the near-total absence of any step sequence fits the score-2 anchor.

2 / 5

Progressive Disclosure

The skill is under 50 lines with a clear intro and a single well-organized Commands section and needs no external references, qualifying for the score-5 simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

45%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 names the skill's domain concisely but lacks a use-when trigger clause and any concrete actions beyond the strategy name, leaving it vague on when Claude should invoke it. It is distinct enough as a niche yet generic enough to risk overlap.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to spread buys/orders over time across trading or prediction platforms.'

Include concrete actions and synonyms such as 'schedule recurring orders' and the abbreviation 'DCA' for better trigger term coverage.

Narrow 'across all platforms' or list representative platforms to reduce overlap risk with general trading skills.

DimensionReasoningScore

Specificity

The description names the domain ("Dollar-cost averaging") but the only action is the strategy name itself, with "across all platforms" adding no concrete action — matching the score-2 anchor "Names the domain but actions are minimal or generic."

2 / 5

Completeness

It gives a clear "what" (dollar-cost averaging across platforms) but no "Use when..." trigger guidance, so per the rubric completeness is capped at 3 — "Has a clear 'what' but 'when' is missing or only weakly implied."

3 / 5

Trigger Term Quality

"Dollar-cost averaging" is a natural term users would say, but the description misses common variations/synonyms (e.g., "DCA", "recurring buys", "recurring orders") and the rest is generic, fitting the score-3 anchor.

3 / 5

Distinctiveness Conflict Risk

DCA is a recognizable niche, but the bare phrase "across all platforms" is broad enough to overlap with other trading/ordering skills, fitting the score-3 anchor "Somewhat specific but could still overlap with similar skills."

3 / 5

Total

11

/

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.