CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

predictfun

Predict.fun prediction market trading (BNB Chain)

53

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/predictfun/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%Weight 40%Scale 1-5

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

The content is concise and actionable, with clean command tables and worked examples, but it lacks sequenced workflows and validation checkpoints for destructive trading operations, which caps workflow clarity. As a single self-contained file it is well structured, though it could split detailed API/command reference into separate files.

Suggestions

Add a sequenced trading workflow with explicit validation checkpoints (e.g. check balance -> inspect book -> place order -> verify order status) to lift workflow_clarity above the destructive-operation cap.

For batch/destructive commands like `/pf cancelall` and `/pf buy`, include confirm/verify steps so errors are caught before or after execution.

Consider moving the full command/API reference into a separate REFERENCE.md with one-level-deep links from SKILL.md to improve progressive_disclosure.

DimensionReasoningScore

Conciseness

The body is efficient: command tables and concise code examples deliver most information with little padding, and it does not explain concepts Claude already knows. It sits above the 3 anchor (mostly efficient, some unnecessary explanation) and below the 5 anchor (every token earns its place) because the Features and Trading Notes sections restate some information already implied by the command tables.

4 / 5

Actionability

Concrete slash commands with explicit arguments and worked examples (e.g. `/pf buy market-123 YES 0.55 100`) give mostly executable, copy-paste-ready guidance. It is below the 5 anchor because there is no underlying SDK/API code and some operational details (fee handling, exact merge mechanics) are only described, not shown.

4 / 5

Workflow Clarity

Trading operations such as `/pf buy`, `/pf sell`, `/pf cancelall`, and `/pf redeem` are destructive or batch operations, and the body provides no validation or verification checkpoints (e.g. confirm balance, verify order book before placing, check order status after). Per the guidelines, missing validation for destructive/batch operations caps workflow_clarity at 3, and since the content is a command menu rather than a sequenced workflow, it fits the 2 anchor (rough sequence/gaps, validation absent).

2 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clearly signaled sections (Quick Start, Commands, Configuration, Features, Trading Notes, Resources) and no bundle files are provided, so content is appropriately self-contained. It matches the 4 anchor (good structure, mostly well placed) rather than the 5 anchor (explicit one-level-deep references) because there are no separate reference files for the larger command/API detail.

4 / 5

Total

14

/

20

Passed

Description

58%Weight 40%Scale 1-5

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 specific and distinct, naming a concrete platform and chain, but it lacks an explicit "Use when..." trigger clause and broad natural-term synonyms, which limits its trigger and completeness scores. It is a solid, concise description that would benefit from explicit usage triggers.

Suggestions

Add an explicit "Use when..." clause listing natural triggers (e.g. prediction markets, trading YES/NO outcomes, betting on event outcomes) to raise completeness above 3.

Include common synonyms and user-facing terms beyond "prediction market trading" and "BNB Chain" (e.g. betting markets, event markets) to improve trigger-term quality.

Optionally enumerate a couple more concrete actions (place orders, redeem positions, merge tokens) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ("prediction market trading") and a concrete action category (trading) tied to a specific chain (BNB Chain), but does not enumerate multiple distinct actions like order placement, merging, or redemption. It sits above the 3 anchor (one concrete action) but below the 5 anchor (comprehensive coverage of several specific actions).

4 / 5

Completeness

The "what" is clear (Predict.fun prediction market trading on BNB Chain) but there is no "Use when..." clause or equivalent trigger guidance. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3, which fits the 3 anchor (clear "what", "when" missing or only weakly implied).

3 / 5

Trigger Term Quality

"prediction market trading" is a natural phrase a user might say, but "BNB Chain" is technical jargon and common synonyms (e.g. betting, prediction markets, polymarket-style) are absent. It matches the 3 anchor (some relevant keywords, missing common variations) rather than the 4 anchor which requires broader natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

"Predict.fun" plus "BNB Chain prediction market" carves a clear, narrow niche that is unlikely to trigger for unrelated skills, with only minor overlap risk against other trading-related skills. It fits the 4 anchor (mostly distinct, minor overlap risk) rather than the 5 anchor (clear niche with minimal conflict).

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/predictfun/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill