history

Trade history tracking, sync, and performance analytics

Quality

56%

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.

This description provides a basic overview of the skill's domain but lacks the specificity and explicit trigger guidance needed for effective skill selection. It names high-level capabilities without concrete actions and completely omits 'when to use' guidance, making it difficult for Claude to confidently select this skill over alternatives.

Suggestions

Add a 'Use when...' clause with trigger terms like 'trades', 'portfolio performance', 'broker sync', 'P&L', 'investment returns'

Replace abstract terms with concrete actions such as 'import trades from brokers', 'calculate realized/unrealized gains', 'generate performance reports'

Include common user phrases and file types like 'CSV import', 'brokerage statements', 'trading history'

Dimension	Reasoning	Score
Specificity	Names the domain (trade history) and lists some actions (tracking, sync, performance analytics), but these are somewhat abstract rather than concrete specific actions like 'calculate P&L', 'import from broker', or 'generate reports'.	2 / 3
Completeness	Only addresses 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this description lacks even implied 'when' context.	1 / 3
Trigger Term Quality	Contains relevant keywords like 'trade history', 'sync', and 'performance analytics', but missing common variations users might say such as 'portfolio', 'trades', 'returns', 'P&L', 'broker', or 'investment tracking'.	2 / 3
Distinctiveness Conflict Risk	'Trade history' provides some specificity to financial/trading domain, but 'performance analytics' is generic enough to potentially conflict with other analytics or finance-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

79%

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

This is a well-structured API reference with excellent actionability and conciseness. The code examples are complete and executable, and the chat commands are clearly documented. However, it lacks validation/error handling guidance for the sync workflow and could benefit from splitting into multiple files for better progressive disclosure.

Suggestions

Add explicit error handling and validation steps for the fetch/sync workflow (e.g., what to do if API returns errors, how to verify sync completed successfully)

Consider splitting into SKILL.md (overview + quick start), API.md (TypeScript reference), and SCHEMA.md (database details) with clear navigation links

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, presenting commands and code without unnecessary explanation. It assumes Claude understands trading concepts, APIs, and database schemas without verbose introductions.	3 / 3
Actionability	Provides fully executable TypeScript code examples, complete SQL schema, and copy-paste ready chat commands. All examples are concrete with realistic parameters and output formatting.	3 / 3
Workflow Clarity	While individual operations are clear, the skill lacks explicit validation checkpoints for the sync workflow. There's no guidance on error handling if API fetches fail or database sync encounters issues.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic document (~200 lines) that could benefit from splitting API reference, database schema, and examples into separate files with clear navigation.	2 / 3
	Total	10 / 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: 2a8c94e

Reviewed: 29 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.