portfolio

Track your positions and P&L across prediction markets and futures exchanges

Quality

35%

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/portfolio/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 reasonably specific domain (prediction markets and futures exchanges) but is too brief and lacks explicit trigger guidance. It would benefit from listing more concrete actions and adding a 'Use when...' clause with natural trigger terms users would actually say.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about tracking bets, positions, profit/loss, or portfolio performance on prediction markets or futures exchanges.'

Expand trigger term coverage to include common variations like 'PnL', 'profit and loss', 'Polymarket', 'Kalshi', 'bets', 'contracts', 'portfolio tracking', and 'trading positions'.

List more specific concrete actions such as 'calculate unrealized P&L, aggregate positions across platforms, monitor open contracts, and summarize trading performance'.

Dimension	Reasoning	Score
Specificity	Names the domain (prediction markets and futures exchanges) and mentions two actions (track positions and P&L), but doesn't list more specific concrete actions like calculating unrealized gains, monitoring margin, aggregating across platforms, etc.	2 / 3
Completeness	Describes what the skill does (track positions and P&L) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also fairly thin, warranting a score of 1.	1 / 3
Trigger Term Quality	Includes some relevant natural keywords like 'positions', 'P&L', 'prediction markets', and 'futures exchanges', but misses common variations users might say such as 'portfolio', 'profit and loss', 'PnL', 'Polymarket', 'Kalshi', 'bets', 'contracts', or 'trading'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'prediction markets' and 'futures exchanges' provides some distinctiveness, but 'track positions and P&L' is generic enough to overlap with general portfolio tracking or trading skills. The niche is somewhat clear but not sharply delineated.	2 / 3
	Total	7 / 12 Passed

Implementation

37%

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

This skill reads more like a product feature list or README than an actionable skill for Claude. It effectively communicates what commands exist and what output looks like, but lacks implementation details, workflow sequencing, and validation steps. The content would benefit from being restructured around concrete workflows rather than feature enumeration.

Suggestions

Add a clear workflow sequence: configure credentials → sync positions → view portfolio, with validation steps for credential verification and sync success/failure handling.

Include concrete implementation guidance or code for how positions are actually fetched from each platform's API, rather than just listing supported platforms.

Add error handling guidance: what to do when API keys are invalid, sync fails, or a platform is unreachable.

Move detailed platform-specific configuration (API keys, auth methods) and advanced features (whale tracking, risk analytics) to separate referenced files to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some sections that feel like feature documentation rather than actionable instructions (e.g., listing all supported platforms with auth methods, the Features section reads like a product spec). The whale tracking and crypto whale monitoring sections add bulk without clear implementation guidance.	2 / 3
Actionability	Commands are clearly listed and the output format example is helpful, but there's no executable code, no implementation details for how positions are actually fetched or synced, and the 'Examples' section shows intent→response mappings without concrete steps. It describes what should happen rather than how to make it happen.	2 / 3
Workflow Clarity	There is no clear multi-step workflow defined. The skill lists commands and features but doesn't explain the sequence of operations (e.g., configure API keys → sync → view positions), has no validation checkpoints, and no error handling guidance for failed syncs or invalid credentials.	1 / 3
Progressive Disclosure	The content is organized into logical sections with clear headers, which is good. However, it's a fairly long monolithic document with no references to external files for detailed topics like API configuration, risk analytics methodology, or whale tracking setup that could benefit from separate documentation.	2 / 3
	Total	7 / 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: e71a5f6

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