CtrlK
BlogDocsLog inGet started
Tessl Logo

prediction-market-risk-review

Review prediction-market, basket, oracle, and trading-agent workflows for compliance, safety, data-quality, privacy, and execution risk. Use before any workflow handles venue auth, user portfolio data, API keys, or trade planning.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tight, well-structured review checklist: concrete directives, clear gate-to-output sequencing, and a human-approval checkpoint for execution steps. It adds only what Claude would not already infer about this domain.

DimensionReasoningScore

Conciseness

Lean gate-based bullet lists with no concept explanation Claude already knows; every line is a directive or output item and nothing is padded, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Concrete directives such as "Remove buy/sell/hold/size recommendations", "Do not request or store private keys, seed phrases, or passwords", "Use read-only scopes by default", and a numbered 5-item output contract give specific, executable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

Structure is clear: review gates are grouped by concern, followed by an explicit output contract, with the checkpoint that any execution-capable step requires a separate implementation plan and explicit user approval.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references; content is organized into well-labeled sections (Advice Boundary, Venue And Regulatory Boundary, Data Quality, Security, Privacy, Output Contract), which scores 3 for a simple skill per the rubric notes.

3 / 3

Total

12

/

12

Passed

Description

100%

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

A strong description: third-person, specific, with an explicit Use-before trigger and a distinct niche. It clearly communicates both capability and activation conditions without verbosity.

DimensionReasoningScore

Specificity

Lists multiple concrete review domains — "compliance, safety, data-quality, privacy, and execution risk" — rather than vague abstractions, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Answers both what ("Review ... workflows for ... risk") and when with an explicit trigger ("Use before any workflow handles venue auth, user portfolio data, API keys, or trade planning."), matching the top anchor.

3 / 3

Trigger Term Quality

Natural domain triggers like "prediction-market", "oracle", "trading-agent", "venue auth", "user portfolio data", "API keys", and "trade planning" give good coverage of terms a user in this niche would actually say.

3 / 3

Distinctiveness Conflict Risk

The prediction-market/oracle/trading-agent niche with venue-auth and trade-planning triggers is a clear, narrow domain unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.