CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

price-handling

Load when comparing, rounding, formatting, or parsing prices, or designing price types.

Quality

81%

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%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.

An exemplary patterns skill: decision-oriented prose with fully executable Rust covering comparison, tick rounding, display formatting, symbol metadata, and feed normalization. Every sequence that exists carries explicit validation guidance, and nothing wastes a token.

DimensionReasoningScore

Conciseness

Lean throughout: "IEEE 754 double precision. No fixed-point, no decimal types." states decisions without explaining known concepts, and every section is dense rules plus minimal code with no padded or over-explained passages.

5 / 5

Actionability

All code is complete, executable Rust (prices_equal with epsilon/ulps margins, round_to_tick, validate_tick_alignment, the SymbolSpec impl, and three typed ingest functions), and the boundary table plus per-feed ingest examples cover the common cases copy-paste ready.

5 / 5

Workflow Clarity

The one multi-step flow is explicitly sequenced with a validation checkpoint and error direction ("round to tick, validate alignment (on failure return an error, never re-round), then format for the broker API"), and the symbol-table lifecycle and ingest boundaries are unambiguous. No destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed: the compact pattern content sits appropriately in a single well-sectioned file with clear headers, no monolithic reference material, and nothing buried. Navigation is trivial.

5 / 5

Total

20

/

20

Passed

Description

57%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.

A trigger-focused description with good specificity and natural keywords, but it omits any statement of what the skill provides — the 'what' lives only in the untriggered summary field. It reads as a pure load-trigger clause rather than a complete description, capping completeness at the anchor for 'when'-only descriptions.

Suggestions

Add an explicit 'what' statement before the trigger clause, e.g. "f64 price-handling patterns for trading systems: epsilon-based comparison, tick rounding, display formatting, and feed parsing. Load when..." so the description answers both what and when.

Pull the domain nouns from the summary (tick size, market data feeds, broker APIs) into the description so users searching those terms can find the skill.

Include common trigger synonyms such as "tick size", "price precision", or "float comparison" to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Lists five concrete actions — "comparing, rounding, formatting, or parsing prices, or designing price types" — but stops short of naming the concrete artifacts the skill actually covers (tick size, market feeds, broker APIs), leaving minor gaps in coverage.

4 / 5

Completeness

Only the 'when' is present ("Load when comparing, rounding, formatting, or parsing prices, or designing price types") with no explicit statement of what the skill provides — structurally matching the "Use when working with documents" anchor. The 'what' (f64 price patterns, tick rounding, feed parsing) exists only in the separate summary field, not the description.

2 / 5

Trigger Term Quality

Natural phrases like "comparing", "rounding", "parsing prices", and "price types" are present, but common variations a user would say — "tick size", "price precision", "float comparison", "decimal" — are missing.

4 / 5

Distinctiveness Conflict Risk

"prices" and "price types" scope it to a clear niche, but the bare terms "rounding" and "formatting" could still trigger a generic number-formatting or float-comparison skill, so minor overlap risk with closely related skills remains.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

skills/price-handling/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.