analytics

Performance attribution, trade analytics, and strategy optimization

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/analytics/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

The body is highly actionable with executable TypeScript covering the analytics surface area, but it is a monolithic inline API reference that belongs in a separate reference file and lacks an explicit workflow with validation checkpoints.

Suggestions

Move the bulk TypeScript API reference into a references/ file (e.g. references/API.md) and keep SKILL.md as a concise overview with one-level-deep links, lifting progressive disclosure.

Add a short numbered workflow (create service -> query period -> review attribution -> export) so the intended usage sequence is explicit rather than implied.

Trim the repeated console.log output blocks to one representative example per method to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete code with little conceptual padding, but it repeats a console.log example-output pattern for every method and inlines a full API reference that could be tightened, fitting the score-3 'mostly efficient but could be tightened' anchor rather than the lean score-4.	3 / 5
Actionability	Copy-paste-ready TypeScript examples with real method calls, arguments, and expected output cover the common cases across summary, attribution, time, edge, liquidity, execution, platform, and export, matching the score-5 'fully executable' anchor.	5 / 5
Workflow Clarity	An implicit create-service -> query -> export flow exists but steps are not explicitly sequenced and there are no checkpoints; the read-only nature avoids the destructive cap, placing it at the score-3 'sequence present but checkpoints implicit' anchor rather than 4.	3 / 5
Progressive Disclosure	No bundle files exist and the entire API reference is inlined in SKILL.md with only section headers, matching the score-2 anchor of 'content that clearly belongs in separate files is inlined'; it is above 1 only because headers provide some structure.	2 / 5
	Total	13 / 20 Passed

Description

41%Weight 40%Scale 1-5

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 names a clear domain and capability set but is a terse noun phrase with no 'Use when...' trigger guidance and only jargon-level keywords. It is moderately specific and distinct but incomplete as activation guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when analyzing trading performance, attributing P&L by edge source or platform, or optimizing strategy timing.'

Reframe the capability list as concrete verbs ('Attribute P&L, analyze trade performance, optimize strategies') rather than abstract nouns to lift specificity.

Include natural synonyms or file/keyword cues users would actually say (e.g. 'win rate', 'Sharpe', 'slippage', 'edge decay') to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	The phrase names the domain ('Performance attribution, trade analytics, and strategy optimization') but uses abstract noun phrases rather than concrete verbs, mirroring the score-2 anchor 'Processes PDF files'. It does not reach score 3 because no concrete actions are stated.	2 / 5
Completeness	A clear 'what' is present (lists capability areas) but there is no 'when' / 'Use when...' clause, so per the judging guidelines completeness is capped at 3, matching the anchor 'Extract text and tables from PDF files, fill forms, merge documents'.	3 / 5
Trigger Term Quality	Only domain jargon ('attribution', 'trade analytics', 'strategy optimization') appears with no natural trigger phrasing or synonyms a user would say, matching the score-2 anchor of generic keywords missing the natural phrases users say.	2 / 5
Distinctiveness Conflict Risk	The trading-analytics framing is a fairly distinct niche with only minor overlap risk against adjacent trading skills, fitting the score-4 'mostly distinct' anchor; it is not a 5 because trigger phrasing is absent.	4 / 5
	Total	11 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/analytics/SKILL.md
Commit: 715fd4a

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