ledger

Trade decision audit trail and statistics

Quality

37%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

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 too terse and abstract to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient detail to distinguish it from other analytics or logging skills. The description needs substantial expansion to explain what specific capabilities it provides and when it should be invoked.

Suggestions

Add specific concrete actions like 'Logs trade executions, tracks profit/loss, generates performance reports, records entry/exit points'

Include an explicit 'Use when...' clause with trigger terms like 'trade history', 'trading performance', 'P&L tracking', 'trade journal'

Specify the types of statistics provided (e.g., win rate, average return, drawdown analysis) to improve distinctiveness

Dimension	Reasoning	Score
Specificity	The description uses vague language with no concrete actions specified. 'Audit trail and statistics' are abstract concepts without explaining what specific operations are performed (e.g., logging trades, generating reports, calculating metrics).	1 / 3
Completeness	The description only vaguely hints at 'what' (audit trail and statistics) without any detail, and completely lacks a 'when' clause or explicit trigger guidance for when Claude should use this skill.	1 / 3
Trigger Term Quality	Contains some relevant domain keywords ('trade', 'audit trail', 'statistics') that users might mention, but lacks common variations and natural phrases users would say like 'trading history', 'trade log', 'performance metrics', or 'trade analysis'.	2 / 3
Distinctiveness Conflict Risk	The 'trade' domain provides some specificity, but 'audit trail' and 'statistics' are generic enough to potentially overlap with other logging, analytics, or financial 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 extremely concise but lacks actionability and workflow context. It reads more like a help menu than a skill that teaches Claude how to effectively use the ledger system. The command syntax is clear, but without examples of outputs or guidance on when/why to use each command, Claude would struggle to leverage this tool effectively in trading scenarios.

Suggestions

Add example outputs for key commands (e.g., what does `/ledger stats 7d` return? What does a decision record look like?)

Include brief workflow guidance: when should Claude check the ledger during trading decisions? How does calibration analysis inform future confidence levels?

Add at least one concrete usage example showing a command and its expected output format

Dimension	Reasoning	Score
Conciseness	Extremely lean - just a title, one-line description, and command reference. No unnecessary explanation of what a ledger is or how audit trails work. Every token serves a purpose.	3 / 3
Actionability	Commands are listed with parameters and brief descriptions, but there are no concrete examples of usage, expected outputs, or what the returned data looks like. Users know what commands exist but not exactly how to use them effectively.	2 / 3
Workflow Clarity	No workflow guidance provided. For a ledger/audit system, there's no indication of when to use which command, how decisions flow into the ledger, or how to interpret the statistics. The commands are listed in isolation without context.	1 / 3
Progressive Disclosure	Content is appropriately brief for a command reference, but there are no references to additional documentation for detailed usage, output formats, or integration with other trading components that would likely exist.	2 / 3
	Total	8 / 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.