analytics

Performance attribution, trade analytics, and strategy optimization

Quality

56%

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/analytics/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 identifies a specialized financial domain but remains too high-level and abstract. It lacks concrete actions, explicit trigger conditions, and natural user language variations. The absence of a 'Use when...' clause significantly limits Claude's ability to correctly select this skill from a larger skill set.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when analyzing trading performance, calculating attribution, backtesting strategies, or when user mentions P&L, returns, or portfolio metrics'

Replace abstract categories with concrete actions such as 'Calculate risk-adjusted returns, decompose P&L by factor, analyze trade execution quality, backtest trading strategies'

Include natural user terms and file types: 'trade logs', 'portfolio data', 'returns analysis', '.csv trade files', 'Sharpe ratio', 'drawdown'

Dimension	Reasoning	Score
Specificity	Names the domain (trading/finance) and lists three action areas (performance attribution, trade analytics, strategy optimization), but these are high-level categories rather than concrete specific actions like 'calculate Sharpe ratios' or 'analyze P&L breakdowns'.	2 / 3
Completeness	Only addresses 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. Missing any indication of when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('performance attribution', 'trade analytics', 'strategy optimization') but misses common user variations like 'trading performance', 'portfolio analysis', 'backtest', 'returns', 'P&L', or 'risk metrics'.	2 / 3
Distinctiveness Conflict Risk	'Trade analytics' and 'strategy optimization' could overlap with general data analytics or financial analysis skills. 'Performance attribution' is more specific to this domain but the overall description lacks clear boundaries.	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 TypeScript examples are executable and comprehensive, covering the full analytics surface area. However, it reads more as documentation than a skill - it lacks workflow guidance for common analytics tasks and could benefit from splitting the detailed API reference into a separate file.

Suggestions

Add a 'Common Workflows' section showing how to sequence analytics calls for typical use cases (e.g., 'Weekly Review Workflow: 1. Get summary, 2. Check attribution, 3. Review edge decay, 4. Export report')

Split the detailed TypeScript API reference into a separate REFERENCE.md file, keeping only quick-start examples in the main skill

Add error handling patterns and validation guidance for report generation and data export operations

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, presenting API references and commands without unnecessary explanation. It assumes Claude understands TypeScript, trading concepts, and API patterns without over-explaining.	3 / 3
Actionability	Provides fully executable TypeScript code examples that are copy-paste ready, with concrete method calls, parameter structures, and output formatting. Chat commands are specific and immediately usable.	3 / 3
Workflow Clarity	This is primarily an API reference rather than a multi-step workflow. While individual API calls are clear, there's no guidance on sequencing analytics tasks, no validation steps for report generation, and no error handling patterns shown.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections (Chat Commands, TypeScript API, Categories, Metrics, Best Practices), but it's a monolithic file. The extensive API reference could be split into separate files with SKILL.md providing an overview and links.	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: 28 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.