Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

triggers

Conditional orders that auto-execute when price thresholds are met

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/triggers/SKILL.md

Quality

Content

72%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 body is a strong, executable API reference: complete code samples, concrete chat commands, and dense platform tables with essentially zero filler. Its weaknesses are structural rather than substantive — no validation guidance for destructive auto-executing operations, and a monolithic single-file layout where the TypeScript API reference and platform tables belong in one-level-deep reference files.

Suggestions

Add an explicit validation loop for the risky path: after triggers.start(), show how to verify a trigger fired and filled correctly (e.g. listen for 'failed' events, confirm result.fillPrice against triggerPrice, and re-check triggers.list({status: 'triggered'})) — this also applies to cancelAll batch operations.

Split the TypeScript API Reference and platform/price-source tables into references/API.md, moving only a quick-start snippet and the chat commands into SKILL.md, so the main file is an overview with clearly signaled one-level-deep references.

Cut the Examples section (its strategies are restatements of snippets already shown) or fold it into the relevant API sections to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is code-dense with no explanation of concepts Claude already knows, and tables (Supported Platforms, Trigger Types, Price Sources) are maximally token-efficient. It is not 5 because the Examples section largely re-demonstrates patterns already shown (buy-the-dip/sell-the-rip, DCA levels) and could be trimmed.	4 / 5
Actionability	Every section gives copy-paste-ready material: complete TypeScript calls (create, createOCO, setStopLoss, setTrailingStop, list, cancel, event handlers) and concrete chat-command syntax with real arguments ("/trigger buy poly 'Trump 2028' YES below 0.40 size 100"). These cover the common cases across all three asset classes.	5 / 5
Workflow Clarity	Triggers auto-execute real-money trades and "cancel all" is a batch operation, yet no validation or verification checkpoints are documented; per the judging guidelines this caps workflow clarity at 3. The setup sequence (createTriggerService -> start -> create -> listen) is present but implicit, and Best Practice #3 ("Monitor execution — Check fill prices") gestures at validation without showing how.	3 / 5
Progressive Disclosure	There are no bundle files at all, and the entire multi-platform API reference (~430 lines) is inlined in SKILL.md — content that clearly belongs in separate reference files. It sits above anchor 2 because section headers (Chat Commands, TypeScript API Reference, Supported Platforms) provide real structure, matching anchor 3's "content that should be separate is inline".	3 / 5
	Total	15 / 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 states a clear, concrete capability but is minimal: it omits any "when to use" guidance and skips the natural vocabulary (stop-loss, take-profit, trigger) that users and Claude would match on. It is serviceable but under-sells the skill's actual scope (SL/TP, OCO, trailing stops, management commands).

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants orders to fire automatically at a price, or mentions stop-loss, take-profit, trailing stops, or price alerts."

Enumerate the concrete capabilities in the description itself: creating entry/exit triggers, stop-loss/take-profit, trailing stops, OCO pairs, and cancelling triggers across prediction markets, futures, and crypto spot.

Include the natural synonyms users say ("trigger order", "buy the dip", "auto-execute at price") so the description matches real phrasing instead of only the technical term "conditional orders".

Dimension	Reasoning	Score
Specificity	"Conditional orders that auto-execute when price thresholds are met" names the domain plus one concrete action, matching the anchor for 1-2 concrete actions without comprehensive coverage (no mention of stop-loss, take-profit, listing, or cancelling). It is above anchor 2 because the stated action is concrete rather than generic, but below anchor 4 because only a single action is listed.	3 / 5
Completeness	The "what" is clear (conditional orders that auto-execute at price thresholds), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because "when" is entirely absent rather than merely under-specified.	3 / 5
Trigger Term Quality	Keywords like "conditional orders", "auto-execute", and "price thresholds" are relevant, but common natural terms are missing: "stop-loss", "take-profit", "trailing stop", "price alert", and even "trigger" despite the skill being named triggers. Some relevant keywords without the common variations matches anchor 3.	3 / 5
Distinctiveness Conflict Risk	"Conditional orders" is a specific order type occupying a clear niche, with only minor overlap risk against a broader order-placement or trading skill. Not 5 because the description lacks explicit trigger phrases that would fully disambiguate it from sibling trading skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/triggers/SKILL.md
Revision: c930628

Reviewed: 24 days ago

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.

triggers

Table of Contents

Is this your skill?