CtrlK
BlogDocsLog inGet started
Tessl Logo

stock-liquidity

Analyze stock liquidity using bid-ask spreads, volume profiles, order book depth, market impact estimates, and turnover ratios via Yahoo Finance data. Use this skill whenever the user asks about liquidity, trading costs, bid-ask spread, market depth, volume analysis, slippage, market impact, turnover ratio, or how easy/hard it is to trade a stock without moving the price. Triggers: "how liquid is AAPL", "bid-ask spread", "volume analysis", "order book depth", "market impact of a large order", "turnover ratio", "slippage estimate", "can I trade 100k shares without moving the price", "liquidity comparison", "spread analysis", "ADTV", "Amihud illiquidity", "dollar volume", "execution cost estimate", "liquidity score", penny stocks, small caps, or thinly traded securities.

72

Quality

89%

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

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

A well-structured, actionable skill body organized around a routing table and six sub-skills, with executable code and an appropriately used one-level-deep reference file. It is slightly held back by a few unnecessary conceptual explanations and by two sub-skills that defer their code to the reference rather than inlining it.

Suggestions

Trim the conceptual preamble ("Liquidity matters because..." and the Almgren-Chriss framework aside) — Claude already understands these; keep only the operational note.

Inline at least a minimal executable snippet for Sub-Skill B (Spread Analysis) and Sub-Skill D (Order Book Depth) so every route has copy-paste-ready code, reserving the reference for the extended template only.

Add an explicit validation checkpoint after data fetch (e.g. confirm non-empty history and present quote fields before computing) to make the read-only workflow's error handling overt.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable code, but a few passages over-explain concepts Claude already knows ("Liquidity matters because it determines the real cost of trading..." and the Almgren-Chriss background note), which could be trimmed.

4 / 5

Actionability

Sub-skills A, C, E, and F ship copy-paste-ready Python functions with a defaults table, but Sub-Skills B and D defer their core code templates to the reference file rather than providing them inline, leaving minor gaps.

4 / 5

Workflow Clarity

A clear three-step flow (dependencies -> route-to-sub-skill -> respond) with a routing table and empty-data guards sequences the work well; it stops just short of explicit validation checkpoints, which is acceptable since the operations are read-only rather than destructive or batch.

4 / 5

Progressive Disclosure

The body is a clear overview of six sub-skills that pushes detailed formulas, extended templates, and academic background into a single one-level-deep reference file, signaled with explicit section pointers (e.g. "§ Options Spread Analysis") that resolve to real headings.

5 / 5

Total

17

/

20

Passed

Description

100%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 highly specific, well-triggered description that concretely states what the skill does and when to use it, with a rich set of natural trigger phrases and a clear niche. It uses third-person voice throughout and avoids fluff.

DimensionReasoningScore

Specificity

"Analyze stock liquidity using bid-ask spreads, volume profiles, order book depth, market impact estimates, and turnover ratios via Yahoo Finance data" lists multiple specific concrete analysis actions with comprehensive coverage of the liquidity domain.

5 / 5

Completeness

It explicitly answers both what ("Analyze stock liquidity using...") and when ("Use this skill whenever the user asks about...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The description packs in natural user phrases ("how liquid is AAPL", "bid-ask spread", "slippage estimate", "execution cost estimate") plus synonyms and technical variants (ADTV, Amihud illiquidity, dollar volume), giving comprehensive keyword coverage.

5 / 5

Distinctiveness Conflict Risk

The niche is clearly scoped to stock-liquidity analysis via Yahoo Finance with distinct metric-specific triggers, minimizing overlap risk with unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
himself65/finance-skills
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.