portfolio
Track your positions and P&L across prediction markets and futures exchanges
Overall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%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 clear domain (prediction markets and futures) but is too brief and lacks explicit trigger guidance. It would benefit from a 'Use when...' clause and more specific capability details to help Claude distinguish it from general trading or portfolio skills.
Suggestions
Add a 'Use when...' clause with trigger terms like 'prediction market', 'Polymarket', 'Kalshi', 'futures position', 'trading P&L', or 'bet tracking'
Expand specific capabilities beyond just 'track' - e.g., 'calculate unrealized gains, monitor open positions, aggregate P&L across platforms'
Include common user phrasings like 'portfolio', 'bets', 'profit and loss', and specific platform names users might mention
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (prediction markets, futures exchanges) and mentions two actions (track positions, track P&L), but lacks comprehensive detail about specific capabilities like alerts, reporting, or analysis features. | 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. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'positions', 'P&L', 'prediction markets', and 'futures exchanges', but misses common variations users might say like 'portfolio', 'trades', 'bets', 'Polymarket', 'Kalshi', or 'profit and loss'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'prediction markets' and 'futures exchanges' provides some distinctiveness, but 'track positions and P&L' could overlap with general trading or portfolio management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive command reference for portfolio tracking with good structure and efficient token usage. However, it reads more like feature documentation than actionable implementation guidance - it tells Claude what commands exist but not how to build or execute the underlying functionality. The lack of setup workflows and error handling guidance limits its practical utility.
Suggestions
Add executable code examples showing how to implement at least one command (e.g., fetching positions from Polymarket API)
Include a setup workflow with validation steps for configuring API keys and verifying connectivity
Add error handling guidance for common failure scenarios (invalid API keys, rate limits, network errors)
Consider splitting platform-specific setup instructions into separate referenced files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting commands, features, and examples without explaining concepts Claude already knows. No unnecessary padding or verbose explanations of what prediction markets or futures are. | 3 / 3 |
Actionability | Commands are clearly listed and the output format example is helpful, but there's no executable code showing how to actually implement these features. The skill describes what commands do rather than providing implementation details or API integration code. | 2 / 3 |
Workflow Clarity | Commands are listed but there's no clear workflow for multi-step processes like initial setup, syncing, or error handling. No validation checkpoints for operations involving API keys or financial data synchronization. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file with no references to detailed documentation for complex features like risk analytics or platform-specific setup guides that would benefit from separate files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%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 | |
- Reviewed
Table of Contents
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.