CtrlK
BlogDocsLog inGet started
Tessl Logo

ito-trade-planner

Build a non-advisory prediction-market trade planning worksheet for Itô or venue workflows. Use to inspect venues, underliers, constraints, order prerequisites, and manual execution steps without placing trades or recommending positions.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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 instruction skill: concrete worksheet fields, explicit guardrails, a gated workflow with a validation checkpoint, and a copy-paste output contract, all with no unnecessary padding.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every section (Guardrails, Workflow, Allowed Language, Output Contract) earns its tokens.

3 / 3

Actionability

Concrete, specific guidance throughout — a numbered workflow with explicit worksheet fields, a named prerequisite skill to invoke, exact phrases to use/avoid, and a copy-paste output contract. No code is expected for this instruction-only skill, so its absence is not penalized.

3 / 3

Workflow Clarity

A clear 5-step sequence with an explicit gating checkpoint (run prediction-market-risk-review before automation) and an approval gate before execution-capable tooling, satisfying the validation-checkpoint requirement.

3 / 3

Progressive Disclosure

A short (under 50 lines), single-purpose skill with no external bundle files, organized into well-signaled sections; per the simple-skills note this merits a 3 without external references.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific, well-scoped description with concrete actions and a clear niche, but it uses "Use to" capability phrasing instead of an explicit "Use when..." trigger and includes domain jargon that limits natural trigger-term coverage.

Suggestions

Add an explicit "Use when..." clause naming user-facing scenarios (e.g., "Use when the user wants to plan or compare prediction-market trades, adjust a basket, or lay out manual execution steps").

Soften jargon ("Itô or venue workflows", "underliers", "order prerequisites") or pair each with a natural-language equivalent so common user phrasings map to the skill.

Keep the non-advisory framing but consider leading with the user-recognizable goal ("Plan and compare prediction-market trades") before the constraint list.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "inspect venues, underliers, constraints, order prerequisites, and manual execution steps" — rather than vague language, matching the multi-action anchor.

3 / 3

Completeness

The "what" is clear, but the trigger is given as "Use to inspect..." (capability language) rather than an explicit "Use when..." clause naming user scenarios, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes some natural terms ("prediction-market trade planning worksheet", "venues") but leans on jargon ("Itô or venue workflows", "underliers", "order prerequisites") and misses common user phrasings, so it is not full coverage.

2 / 3

Distinctiveness Conflict Risk

The niche is clearly defined — non-advisory prediction-market trade planning for Itô/venue workflows — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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.