opportunity
Find and execute cross-platform arbitrage opportunities across prediction markets
70
59%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/opportunity/SKILL.mdQuality
Discovery
40%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 niche domain (prediction market arbitrage) which provides good distinctiveness, but suffers from lack of specific actions and completely missing trigger guidance. The description would benefit significantly from listing concrete capabilities and adding explicit 'Use when...' conditions.
Suggestions
Add a 'Use when...' clause with trigger terms like 'arbitrage', 'prediction market odds', 'Polymarket', 'Kalshi', 'betting opportunities', or 'cross-platform betting'.
List specific concrete actions such as 'compare odds across platforms', 'calculate arbitrage spreads', 'identify mispriced contracts', or 'execute hedged positions'.
Include common platform names and user phrases like 'find betting opportunities', 'risk-free profit', or 'odds comparison' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (prediction markets, arbitrage) and a general action (find and execute opportunities), but lacks specific concrete actions like 'compare odds across platforms', 'calculate profit margins', or 'place hedged bets'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'arbitrage', 'prediction markets', and 'cross-platform', but misses common variations users might say such as 'betting', 'odds', 'Polymarket', 'Kalshi', 'sports betting', or 'risk-free profit'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'cross-platform arbitrage' and 'prediction markets' creates a clear, specific niche that is unlikely to conflict with other skills. This is a distinctive domain with unique terminology. | 3 / 3 |
Total | 8 / 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-written, actionable skill with excellent code examples and efficient use of tokens. The main weaknesses are the lack of explicit validation/error-handling workflows for financial operations (which are inherently risky) and the monolithic structure that could benefit from splitting detailed API reference into separate files.
Suggestions
Add explicit validation and error-handling workflow for execution: check balances → validate opportunity still exists → execute → verify fills → handle partial fills or failures
Include a feedback loop section for common failure scenarios (insufficient funds, opportunity expired, slippage exceeded) with recovery steps
Split the TypeScript API Reference into a separate REFERENCE.md file, keeping only quick-start examples in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code examples without unnecessary explanation. It assumes Claude understands prediction markets, arbitrage concepts, and TypeScript without over-explaining basics. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready, concrete chat commands with clear syntax, and specific configuration options. Every section includes working code or exact command formats. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the skill lacks explicit validation checkpoints for the execution workflow. There's no feedback loop for handling failed executions, slippage issues, or verification steps before committing to trades involving real money. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic document. The extensive API reference and TypeScript examples could be split into separate files (e.g., API_REFERENCE.md, EXAMPLES.md) with the main skill providing a concise overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
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.