market-index

Search, discover, and browse indexed markets across all platforms

Quality

44%

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/market-index/SKILL.md

Quality

Discovery

25%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague and lacks critical context. It fails to specify what type of markets (financial, prediction, e-commerce?), what 'indexed' means in this context, and provides no guidance on when Claude should use this skill. The generic terminology creates high conflict risk with other potential skills.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about prediction markets, wants to find betting odds, or mentions platforms like Polymarket or Kalshi'

Clarify what type of markets this covers (prediction markets, financial markets, NFT marketplaces, etc.) to reduce ambiguity and conflict risk

Include natural user terms and specific platform names that would trigger this skill, such as 'odds', 'predictions', 'betting', or specific market platform names

Dimension	Reasoning	Score
Specificity	Names the domain (markets/platforms) and lists some actions (search, discover, browse), but lacks concrete details about what 'indexed markets' means or what specific operations can be performed.	2 / 3
Completeness	Describes what it does (search/discover/browse markets) 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 some relevant terms like 'search', 'discover', 'browse', and 'markets', but 'indexed markets' and 'all platforms' are vague. Missing natural user terms like specific market types, trading, stocks, crypto, or platform names.	2 / 3
Distinctiveness Conflict Risk	'Markets' and 'platforms' are extremely generic terms that could conflict with e-commerce, stock trading, prediction markets, or marketplace skills. No clear niche is established.	1 / 3
	Total	6 / 12 Passed

Implementation

64%

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

This is a solid API reference with excellent actionable code examples that are immediately executable. The main weaknesses are the monolithic structure that could benefit from splitting into overview + reference files, and the lack of workflow guidance for common multi-step discovery patterns. Some generic content like 'Best Practices' adds little value for Claude.

Suggestions

Split the TypeScript API Reference into a separate REFERENCE.md file, keeping only a quick-start example in the main skill

Add a workflow section showing common multi-step patterns like 'discover trending -> filter by criteria -> get details -> track'

Remove or condense the 'Best Practices' section - these are generic tips Claude already understands

Add error handling examples for common failure cases like network errors or invalid market IDs

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good code examples, but includes some unnecessary elements like the 'Best Practices' section with generic advice Claude already knows, and the categories table with obvious descriptions like 'Elections, policy, government' for politics.	2 / 3
Actionability	Excellent executable code examples throughout - both chat commands and TypeScript API calls are copy-paste ready with realistic parameters and complete syntax. The examples show actual usage patterns with output formatting.	3 / 3
Workflow Clarity	The skill presents individual operations clearly but lacks workflow sequencing for common multi-step tasks like 'discover market -> analyze -> track'. No validation checkpoints for index updates or error handling guidance for failed searches.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but everything is in one monolithic file. The API reference section could be split into a separate REFERENCE.md, and the categories/syntax tables could be in an APPENDIX.md for a cleaner overview.	2 / 3
	Total	9 / 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: 2a8c94e

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