market-index

Search, discover, and browse indexed markets across all platforms

Quality

22%

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

17%

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 is too vague and jargon-heavy to effectively guide skill selection. It lacks a 'Use when...' clause, uses overlapping generic verbs, and fails to specify what kind of markets or platforms are involved. A user looking for market-related functionality would struggle to know if this skill fits their need.

Suggestions

Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about prediction markets, wants to find or browse markets on Polymarket, Manifold, or similar platforms.'

Specify the type of markets (prediction markets, financial markets, etc.) and name the platforms to replace the vague 'all platforms' phrasing.

Replace the overlapping verbs 'search, discover, and browse' with more distinct concrete actions, e.g., 'Search for prediction markets by keyword, list trending markets, retrieve market details and odds.'

Dimension	Reasoning	Score
Specificity	Names a domain ('indexed markets') and lists some actions ('search, discover, and browse'), but the actions are somewhat overlapping and vague. 'All platforms' is unspecific and doesn't clarify what kind of markets or what concrete outputs are produced.	2 / 3
Completeness	The description addresses 'what' at a surface level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	The terms 'indexed markets' and 'all platforms' are jargon-heavy and not natural phrases a user would say. Users might say 'find markets', 'prediction markets', 'betting markets', or name specific platforms, none of which are included.	1 / 3
Distinctiveness Conflict Risk	The mention of 'indexed markets' provides some niche specificity, but 'search, discover, and browse' are generic verbs that could overlap with many search-related skills. Without specifying the type of markets (prediction, financial, etc.), conflict risk remains moderate.	2 / 3
	Total	6 / 12 Passed

Implementation

27%

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

The skill is an exhaustive API reference dump rather than a focused, actionable skill document. While it provides concrete code examples, it suffers from significant verbosity (redundant console.log patterns, obvious category descriptions, generic best practices) and poor progressive disclosure by inlining everything into one large file. The lack of workflow sequencing and validation steps for multi-step operations further weakens its utility.

Suggestions

Split the TypeScript API reference, categories table, and search syntax into separate referenced files, keeping SKILL.md as a concise overview with quick-start examples

Remove all the console.log output formatting lines — Claude knows how to print results; focus on the API calls and their parameters

Add a workflow showing the typical sequence: create index → update → search → handle results, with error handling for failed updates

Remove the categories description column (self-evident) and the generic 'Best Practices' section that tells Claude things it already knows

Dimension	Reasoning	Score
Conciseness	The content is extremely verbose at ~180 lines, with extensive console.log examples that add no instructional value, a categories table with obvious descriptions ('politics' = 'Elections, policy, government'), and a 'Best Practices' section of generic advice Claude already knows. Much of this could be cut by 60%+ without losing actionable information.	1 / 3
Actionability	The code examples are concrete and appear executable with specific API calls and parameters, but they reference a 'clodds/market-index' package that may not exist, and the chat commands (/index search) lack context on what system they run in. The examples are detailed but their real-world executability is uncertain.	2 / 3
Workflow Clarity	The skill presents individual API operations clearly but lacks any sequenced workflow showing how to combine steps (e.g., create index → update → search → act on results). There are no validation checkpoints or error handling guidance for operations like index updates that could fail.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with everything inlined — the full API reference, categories table, search syntax, sorting options, and best practices are all in one file. The TypeScript API reference and search syntax tables should be in separate referenced files, with SKILL.md serving as a concise overview.	1 / 3
	Total	6 / 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.