CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

whale-hunting

Detect institutional whale activity in options for a given underlying. Use when the user asks about unusual options activity, large block trades, whale trades, or institutional options flow for a specific symbol.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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-built, action-oriented skill body: concrete runnable command, complete argument and output documentation, and unusually precise presentation guidance. The main defects are a documented-but-unimplemented `--sigma` flag (which breaks one example command) and a missing description of the script's error-output path.

Suggestions

Remove the `--sigma` argument from the Arguments section and the `SPY --sigma 2.0` example (or implement the flag in scripts/whale_hunting.py) — as documented, running that example fails with an argparse 'unrecognized arguments' error.

Document the error path: scripts/whale_hunting.py prints JSON containing an `error` field and exits 1 on data failures (e.g. WhaleDataError); a short note in Output telling the agent to relay the error and stop would close the workflow's validation gap.

Fold the Timezone section's script-facing requirements ('All JSON output must include generated_at and data_delay fields') into a one-line note that these are already handled by the script, keeping the section purely about interpreting NY-time timestamps.

DimensionReasoningScore

Conciseness

The body is lean — a concrete command, arg list, output schema, examples, and reporting spec with zero explanation of known concepts. It falls short of anchor 5 only because of minor redundancy: the Timezone section's "All JSON output must include `generated_at` and `data_delay` fields" is a script-implementation requirement the script already satisfies, not guidance for the agent running it.

4 / 5

Actionability

The skill provides a fully concrete command with path, documented arguments, four copy-paste examples, and an explicit output schema — mostly executable. It misses anchor 5 because `--sigma` ("Std-deviation multiplier for crude outlier threshold", used in the example `SPY --sigma 2.0`) is not implemented in scripts/whale_hunting.py's argparse, so that documented flag and example command fail with an unrecognized-arguments error.

4 / 5

Workflow Clarity

The single-action workflow is unambiguous — run the script, then present results per a very specific reporting format (header line template, table columns, sort by `total_invested` descending, interpretation guidance). It misses anchor 5 because the script's failure path (JSON output with an `error` field and exit code 1) is undocumented, leaving a minor validation gap for error recovery.

4 / 5

Progressive Disclosure

Content is well-organized into tight sections (Instructions, Arguments, Output, Examples, Reporting, Requirements, Timezone) and the only bundle material is correctly delegated to scripts/whale_hunting.py, whose path matches the command. Nothing that belongs in a separate file is inlined and the reference is one level deep, matching the top anchor for a well-structured single-script skill.

5 / 5

Total

17

/

20

Passed

Description

90%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 strong description: it clearly states a single concrete capability and pairs it with an explicit, well-phrased 'Use when' clause full of natural trigger synonyms. The only weakness is modest action breadth — it names one action (detect) rather than enumerating what detection covers (scan chains, flag anomalous trades, aggregate call/put flow).

DimensionReasoningScore

Specificity

"Detect institutional whale activity in options for a given underlying" names the domain and one concrete action but does not list several distinct actions, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It stays above anchor 2 because it specifies what is detected, in what instrument class, and at what scope.

3 / 5

Completeness

It explicitly answers both what ("Detect institutional whale activity in options for a given underlying") and when ("Use when the user asks about unusual options activity, large block trades, whale trades, or institutional options flow for a specific symbol") with concrete trigger phrases — an exact match for the top anchor. The when-clause is fully explicit, not merely implied, so anchor 4 does not apply.

5 / 5

Trigger Term Quality

"unusual options activity, large block trades, whale trades, or institutional options flow" gives comprehensive natural-language coverage with synonyms for this domain — exactly the phrases a user would say. No natural trigger term for this niche is missing (file extensions do not apply here), so it does not fall to anchor 4.

5 / 5

Distinctiveness Conflict Risk

"institutional whale activity in options ... for a specific symbol" carves out a clear niche with distinct triggers (whale trades, block trades, options flow), presenting minimal conflict risk with other skills. There is no meaningful overlap that would push it down to anchor 4.

5 / 5

Total

18

/

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

staskh/trading_skills

Path

.claude/skills/whale-hunting/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.