Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

history

Trade history tracking, sync, and performance analytics

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

65%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 content is highly actionable with executable code and commands across all common operations, but it is an inlined monolithic API reference that would benefit from being split into reference files, and it lacks validation checkpoints around the batch sync workflow.

Suggestions

Move the full TypeScript API reference and database schema into a separate reference file (e.g. references/API.md) and keep SKILL.md as a concise overview with a one-level-deep link.

Add an explicit validation step after database sync (e.g. verify row count or query a recent trade) to satisfy the batch-operation feedback-loop requirement.

Trim the verbose console.log output examples to the minimal lines that demonstrate each API method's return shape.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code and commands with no concept-explanation fluff, but the verbose console.log output examples (the 15-line stats block, the daily-P&L bar-chart rendering, the by-market loop) are illustrative padding that could be tightened, fitting 'mostly efficient but could be tightened'.	3 / 5
Actionability	Concrete executable TypeScript and copy-paste chat commands cover the common cases (fetch, sync, getTrades, stats, daily P&L, by-market, export) with a real import path and specific options, matching 'fully executable; copy-paste ready'.	5 / 5
Workflow Clarity	Commands are grouped into a loose fetch→sync→view→stats sequence, but there are no validation checkpoints and the batch database-sync operation lacks verification; per the rubric's destructive/batch cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Section headers provide structure, but ~200 lines of TypeScript API reference and a SQL schema are inlined in SKILL.md with no external reference files (none exist in references/scripts/assets); this matches 'some structure; content that should be separate is inline' rather than the well-split score-4/5 anchors.	3 / 5
	Total	14 / 20 Passed

Description

62%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 concisely states what the skill does with three concrete actions and natural keywords, but it lacks any explicit 'when to use' trigger guidance and does not name the prediction-market platforms that would make it distinctive.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when the user wants to review, sync, or analyze their Polymarket or Kalshi trade history, P&L, or trade logs.'

Mention the platforms (Polymarket, Kalshi) in the description to improve distinctiveness and reduce conflict with generic trading skills.

Include common trader synonyms such as P&L, profit and loss, or trade journal to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Trade history tracking, sync, and performance analytics" names the domain plus three concrete actions (tracking, sync, analytics); it lists several specific actions with only minor genericness in 'tracking', fitting the score-4 anchor better than the 1-2 actions of score 3.	4 / 5
Completeness	The 'what' is clear (tracking, sync, analytics) but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural phrases a user would say are present ("trade history", "sync", "performance analytics"), giving good keyword coverage; it misses common trader synonyms like P&L, trade log, or profit-and-loss, so it stops short of comprehensive score-5 coverage.	4 / 5
Distinctiveness Conflict Risk	"Trade history" is a recognizable niche but the description omits the defining platforms (Polymarket/Kalshi) named in the body, leaving overlap risk with generic trading-analytics skills; this fits 'somewhat specific but could still overlap' better than the more tightly scoped score 4.	3 / 5
	Total	14 / 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/history/SKILL.md
Revision: c930628

Reviewed: 1 month ago

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.

history

Table of Contents

Is this your skill?