Dollar-cost averaging across all platforms
40
26%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/dca/SKILL.mdQuality
Discovery
14%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 far too terse and vague. It names a financial concept but fails to specify what actions the skill performs, when it should be selected, or what platforms it covers. It would be nearly impossible for Claude to reliably choose this skill from a list of alternatives.
Suggestions
Add concrete actions the skill performs, e.g., 'Calculates optimal DCA schedules, tracks recurring investments, and compares cost basis across brokerage accounts.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about dollar-cost averaging, DCA strategies, recurring investments, or periodic buying schedules.'
Replace 'all platforms' with specific platform types or names to improve distinctiveness and reduce conflict risk with other finance-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a financial concept ('dollar-cost averaging') but does not describe any concrete actions the skill performs—no verbs like 'calculates', 'schedules', 'tracks', or 'analyzes'. | 1 / 3 |
Completeness | The description barely addresses 'what' (only names a concept, not what the skill does) and completely lacks a 'when' clause or any explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | 'Dollar-cost averaging' is a relevant keyword a user might say, but there are no variations or related terms (e.g., 'DCA', 'recurring investment', 'periodic buying', 'investment strategy'). 'All platforms' is vague and adds no useful trigger terms. | 2 / 3 |
Distinctiveness Conflict Risk | 'Across all platforms' is extremely generic and could overlap with any investment, finance, or trading skill. There is no clear niche or distinct trigger to differentiate it. | 1 / 3 |
Total | 5 / 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.
This skill is essentially a command cheat-sheet with no implementation guidance, no workflow for executing DCA strategies, and no safety/validation steps for financial operations. While it's admirably concise, it lacks the actionable content needed to actually teach Claude how to perform dollar-cost averaging — it only lists command signatures without explaining what happens behind them or how to handle errors, rate limits, or partial fills.
Suggestions
Add at least one complete executable example showing a full DCA workflow from order creation through monitoring and completion, including expected outputs at each step.
Include validation and safety checkpoints: balance verification before placing orders, confirmation steps for large amounts, error handling for failed transactions, and rate-limit awareness per platform.
Add a workflow section describing the lifecycle of a DCA order: creation → execution of individual tranches → monitoring → completion/cancellation, with explicit feedback loops for failed tranches.
Reference platform-specific documentation files (e.g., POLYMARKET.md, KALSHI.md) for authentication setup, API details, and platform-specific constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean — no unnecessary explanations, no padding. Every line serves a purpose: a brief description and a command reference table. Assumes Claude knows what DCA is and how these platforms work. | 3 / 3 |
Actionability | The skill only lists command signatures with no executable code, no implementation details, no examples of actual usage or expected outputs. It describes a CLI interface but provides no guidance on how to actually implement or execute any of these commands. | 1 / 3 |
Workflow Clarity | There is no workflow described — no sequencing of steps, no validation checkpoints, no error handling. For a financial operation that involves spreading orders over time across multiple platforms, the absence of any process guidance or safety checks is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is well-organized with a clear command reference section, but there are no references to detailed documentation for individual platforms, configuration, or advanced usage. The structure is clean but incomplete. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%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 | |
e71a5f6
Table of Contents
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.