CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mm

Market making - two-sided quoting with inventory management

54

Quality

68%

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

Quality

Content

68%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 well-structured and actionable with concrete commands and examples, but the market-making workflow lacks explicit validation/checkpoint feedback loops appropriate to a batch order-placement operation. Tightening the API example and adding a verify step would raise the top dimensions.

Suggestions

Add an explicit validation/recovery step to the workflow, e.g. after each requote cycle confirm orders are live and positions within limits, and halt-and-retry guidance if placement fails.

Move the full TypeScript API usage block into a separate reference file and keep only a minimal inline snippet, improving progressive disclosure.

Note that the API example imports project-internal modules; clarify the import paths or mark the example as illustrative so it isn't mistaken for standalone-runnable code.

DimensionReasoningScore

Conciseness

The body is efficient: compact flag tables, terse command blocks, and a 6-step 'How It Works' list with no over-explanation of concepts Claude already knows, though a few inline sections could be trimmed slightly.

4 / 5

Actionability

Concrete chat commands, a flag table with defaults, copy-paste examples, and a TypeScript config block give mostly executable guidance; the API example depends on project-internal modules ('../trading/market-making', 'botManager') that aren't standalone-runnable, leaving a minor gap.

4 / 5

Workflow Clarity

The 'How It Works' section gives a clear 6-step sequence, but market making is a batch/order-placement operation and the body lacks an explicit validate-then-proceed feedback loop; per the rubric this caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Content is well organized into clearly headed sections (Lifecycle, Monitoring, Configuration, Start Flags, Examples, How It Works, API Usage) with no nested references; with no bundle files present everything is appropriately inline, though the API usage block could arguably live in a separate reference file.

4 / 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 is specific and distinct but lacks a 'when to use' trigger clause and natural user-facing keywords for the platforms it targets. Adding a 'Use when...' sentence naming Polymarket/Kalshi would lift completeness and trigger term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when market making on Polymarket or Kalshi, or when the user asks for two-sided quotes on prediction markets.'

Include natural trigger terms users actually say, such as 'Polymarket', 'Kalshi', 'prediction markets', and 'orderbook quoting'.

Mention the supported platforms inline in the description to broaden keyword coverage and reinforce distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('Market making') and two concrete actions ('two-sided quoting', 'inventory management'), matching the anchor for 1-2 concrete actions but not comprehensive coverage.

3 / 5

Completeness

Provides a clear 'what' (two-sided quoting with inventory management) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes relevant keywords like 'market making' and 'two-sided quoting' but omits natural user-facing terms such as 'Polymarket', 'Kalshi', 'prediction markets', or 'orderbook' that a user would actually say.

3 / 5

Distinctiveness Conflict Risk

'Market making - two-sided quoting with inventory management' occupies a clear niche unlikely to conflict with unrelated skills, though it is one trigger phrase short of the maximally distinctive anchor.

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/mm/SKILL.md

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.