Dollar-cost averaging across all platforms
51
37%
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
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 severely underdeveloped. It names a financial concept (dollar-cost averaging) but fails to specify what actions the skill performs, what platforms it supports, or when Claude should select it. The description would be nearly useless for skill selection among multiple finance-related skills.
Suggestions
Add specific actions the skill performs (e.g., 'Calculates optimal DCA schedules, tracks recurring investments, compares DCA strategies across brokerages').
Include a 'Use when...' clause with trigger terms like 'DCA', 'recurring investment', 'periodic buying', 'investment schedule', or specific platform names.
Specify which platforms are supported or clarify what 'all platforms' means to improve distinctiveness from other investment-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language with no concrete actions specified. 'Dollar-cost averaging' names a concept but doesn't describe what the skill actually does (calculate, track, recommend, automate?). | 1 / 3 |
Completeness | The description only vaguely hints at 'what' (something about DCA) and completely lacks any 'when' guidance. There's no 'Use when...' clause or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | 'Dollar-cost averaging' is a relevant financial term users might say, but it lacks common variations like 'DCA', 'recurring investment', 'periodic buying', or platform-specific terms. | 2 / 3 |
Distinctiveness Conflict Risk | 'Dollar-cost averaging' provides some domain specificity to investing/finance, but 'across all platforms' is generic and could overlap with other investment or trading skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is admirably concise and provides a clear command reference, but critically lacks actionability and workflow safety for financial operations. DCA involves real money across multiple platforms - the absence of validation steps, error handling, example outputs, and verification workflows is a significant gap for operations that could result in financial loss.
Suggestions
Add concrete examples with real values and expected output (e.g., '/dca poly abc123 1000 --per 100 --every 1h' → shows confirmation message and order ID)
Include validation/verification workflow: how to confirm orders are executing, what success/failure looks like, how to verify funds were transferred
Add error handling guidance: what happens if a platform is down, insufficient funds, or rate limits are hit
Consider linking to platform-specific documentation for authentication setup and API requirements
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean - just a brief description and command reference. No unnecessary explanations of what DCA is or how trading platforms work. Every line serves a purpose. | 3 / 3 |
Actionability | Commands are clearly listed with parameter placeholders, but lacks concrete examples with actual values, expected outputs, or what happens after execution. No executable code or real usage examples. | 2 / 3 |
Workflow Clarity | No workflow guidance for multi-step DCA operations. Missing: how to verify orders executed, what to do if an order fails, how to monitor progress, no validation checkpoints for financial operations that could lose money. | 1 / 3 |
Progressive Disclosure | Well-organized command reference in a single file, but for a skill spanning 14+ platforms with financial implications, there should be references to platform-specific details, error handling, or configuration guides. | 2 / 3 |
Total | 8 / 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 | |
2a8c94e
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.