CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

strategy

Build and manage custom trading strategies with natural language

52

Quality

66%

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/strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 action-oriented and token-efficient with strong executable examples, but it lacks an explicit validation feedback loop for live-trading workflows and inlines a full API reference that should be split into referenced files.

Suggestions

Add an explicit numbered workflow with validation checkpoints (e.g. create -> validate -> if errors fix and re-validate -> dry-run -> only then activate live) to provide a clear feedback loop.

Move the bulk of the TypeScript API reference and condition-type catalog into separate referenced files (e.g. API.md, CONDITIONS.md), keeping only a quick-start example inline in SKILL.md.

Document the createStrategyBuilder config options exhaustively or point to a reference, since several options are shown without a complete list.

DimensionReasoningScore

Conciseness

The body is dense and code-heavy with minimal concept padding; only minor redundancy between the chat-command and TypeScript-API sections keeps it from a 5.

4 / 5

Actionability

Provides mostly executable, copy-paste-ready TypeScript and slash-command examples covering the common create/validate/activate/monitor cases, with only minor gaps in config-option coverage.

4 / 5

Workflow Clarity

A loose sequence exists (dry-run, start small, monitor, iterate) and dry-run-first is emphasized, but there is no explicit validate-then-fix feedback loop; for a live-trading skill this caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Section structure is clear, but the entire TypeScript API reference and condition-type catalog are inlined into SKILL.md with no references to deeper files; content that belongs in separate files is inline.

3 / 5

Total

14

/

20

Passed

Description

53%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 concise and domain-specific with clear actions, but it omits any 'Use when...' trigger guidance and has limited keyword breadth. Adding explicit trigger phrases and synonyms would raise both completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when the user wants to create, test, or deploy automated trading strategies.'

Broaden trigger terms with synonyms and concrete formats users say, such as 'algorithmic trading', 'strategy builder', 'backtesting', or 'deploy strategy'.

Expand the action list slightly (e.g. 'create, backtest, deploy, and monitor') to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the trading-strategy domain with two concrete actions ('Build' and 'manage') plus a natural-language qualifier, but coverage is not comprehensive — only 1-2 actions named.

3 / 5

Completeness

The 'what' is clear (build and manage custom trading strategies) but there is no 'Use when...' or equivalent 'when' clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ('trading strategies', 'build and manage', 'natural language') but lacks synonyms, common variations, or file extensions, matching the 'some relevant keywords' anchor.

3 / 5

Distinctiveness Conflict Risk

'Custom trading strategies with natural language' targets a clear niche with minimal overlap risk; only minor overlap with other trading-related skills keeps it from a 5.

4 / 5

Total

13

/

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/strategy/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