history

Trade history tracking, sync, and performance analytics

Quality

30%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/history/SKILL.md

Quality

Discovery

32%

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 too brief and high-level, providing only a general sense of the domain without concrete actions or explicit trigger guidance. It lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. The terms used are somewhat relevant but miss many natural user phrases related to trading and portfolio management.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about trade history, portfolio performance, P&L calculations, or syncing brokerage accounts.'

List specific concrete actions such as 'Import trades from brokers, calculate profit/loss, track portfolio returns, generate performance reports.'

Include natural user terms like 'portfolio', 'P&L', 'returns', 'brokerage', 'investment', 'stocks', 'trades' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (trade history) and lists some actions (tracking, sync, performance analytics), but these are fairly high-level and not concrete enough to understand specific capabilities like calculating P&L, importing from brokers, or generating reports.	2 / 3
Completeness	Describes what the skill does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also weak enough to warrant a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'trade history', 'sync', and 'performance analytics', but misses common user terms like 'portfolio', 'P&L', 'returns', 'trades', 'brokerage', or 'investment performance'.	2 / 3
Distinctiveness Conflict Risk	The term 'trade history' provides some specificity to a financial trading domain, but 'performance analytics' and 'tracking' are generic enough to potentially overlap with other analytics or portfolio-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

27%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is an overly verbose API reference dump that includes extensive console.log formatting code, redundant examples, and explanatory patterns that don't add value for Claude. It lacks workflow sequencing, validation checkpoints, error handling guidance, and progressive disclosure. The content would benefit significantly from being condensed to essential patterns and split across referenced files.

Suggestions

Cut the verbose console.log examples (especially stats and daily P&L visualization) down to just the API call signatures and return types — Claude can format output on its own.

Add an explicit workflow section at the top: fetch → sync → validate data → query/analyze → export, with error handling for failed API calls or sync issues.

Split into SKILL.md (overview + quick start + workflow) and separate reference files for the full TypeScript API, chat commands, and database schema.

Remove the 'Best Practices' section of generic advice (sync regularly, review weekly) which is not actionable guidance for Claude executing tasks.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive console.log formatting examples that Claude doesn't need. The statistics section alone has ~20 lines of console.log that add no instructional value. The daily P&L visualization code with bar charts is unnecessary padding. Much of this could be condensed to type signatures and brief usage patterns.	1 / 3
Actionability	Provides concrete TypeScript code and SQL schema, but it's unclear if these are real APIs from an actual 'clodds/history' package or aspirational pseudocode. The chat commands lack context on what system they run in. Code appears executable but completeness/correctness is unverifiable.	2 / 3
Workflow Clarity	The implicit workflow is fetch → sync → query/analyze → export, but this sequence is never explicitly stated as a workflow with validation checkpoints. There's no error handling guidance, no validation steps after sync, and no feedback loops for failed API fetches or database sync issues.	2 / 3
Progressive Disclosure	This is a monolithic wall of text at ~200 lines with no references to external files. The chat commands, TypeScript API, database schema, and best practices are all inlined when the API reference and schema could easily be separate files. No navigation structure or cross-references.	1 / 3
	Total	6 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: alsk1992/CloddsBot
Commit: e71a5f6

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.