predictfun

Predict.fun prediction market trading (BNB Chain)

Quality

43%

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

Quality

Discovery

22%

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 terse and lacks both concrete action descriptions and explicit trigger guidance. While it identifies a specific platform (Predict.fun) and chain (BNB Chain), it fails to explain what actions the skill performs or when Claude should invoke it. It reads more like a title than a functional description.

Suggestions

Add specific actions the skill performs, e.g., 'Places bets on prediction markets, checks market odds, manages positions, and withdraws winnings on Predict.fun.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks about prediction markets, betting on outcomes, Predict.fun, or BNB Chain trading.'

Include natural user-facing keywords like 'bet', 'wager', 'odds', 'outcomes', 'predictions' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names a domain ('prediction market trading') and a platform ('Predict.fun', 'BNB Chain') but does not describe any concrete actions like placing bets, checking odds, creating markets, or withdrawing funds.	1 / 3
Completeness	The description weakly addresses 'what' (prediction market trading) but completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'Predict.fun', 'prediction market', 'trading', and 'BNB Chain' that users might naturally mention, but misses common variations like 'bet', 'wager', 'odds', 'outcome', or 'polymarket-style'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Predict.fun' and 'BNB Chain' provides some distinctiveness from generic trading or crypto skills, but 'prediction market trading' could overlap with other prediction market or DeFi trading skills.	2 / 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 well-structured, concise reference for a prediction market trading integration. Its main strengths are token efficiency and clear command documentation with examples. However, it lacks validation workflows critical for financial operations (checking balances before trading, confirming order execution) and doesn't provide enough guidance for error handling or multi-step trading scenarios.

Suggestions

Add a common trading workflow with explicit validation steps (e.g., check balance → search market → review orderbook → place order → verify order in open orders list → check position)

Include error handling guidance for common failure modes: insufficient balance, invalid market ID, failed transaction, order rejection

Add a validation checkpoint after order placement (e.g., 'After placing an order, run /pf orders to confirm it appears in open orders')

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It avoids explaining what prediction markets are, what BNB Chain is, or how blockchain transactions work. Every section delivers specific, actionable information without padding.	3 / 3
Actionability	The commands are clearly documented with examples, but they reference slash commands (/pf) that are presumably handled by an external tool (clodds) rather than providing executable code. The skill tells Claude what commands to invoke but doesn't show the underlying API calls or SDK usage, making it dependent on an external CLI tool.	2 / 3
Workflow Clarity	While individual commands are clear, there's no explicit workflow for common multi-step trading scenarios (e.g., search market → check book → place order → verify position). For a trading skill involving real money, there are no validation checkpoints or error recovery steps (e.g., confirming order placement, checking transaction success, handling insufficient balance).	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and tables, but everything is in a single file. The Features and Trading Notes sections could be expanded or linked to separate docs. The external resource links are minimal and don't point to detailed internal documentation for advanced topics like order signing or fee structures.	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: 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.