CtrlK
BlogDocsLog inGet started
Tessl Logo

research-stocks

Read current stock research, technical backtests, saved analyses or saved backtests. Use for a named ticker or watchlist research history; preserve source dates, model limitations and risk factors.

68

Quality

85%

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

86%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 tight, highly actionable skill body: precise operation tables, argument defaults and ranges, response-shape and error-handling guidance, and good section organization with no filler. The only notable improvement would be one concrete example invocation and sample response to make usage fully copy-paste ready.

Suggestions

Add a short example tool invocation (e.g. get_stock_research with operation 'history' and symbols ["AAPL", "MSFT"]) and a trimmed sample response so usage is fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense operational guidance — an operations table with defaults and ranges, response shape, auth header, and error handling — with no explanations of concepts Claude already knows and no padding; every token carries skill-specific information.

5 / 5

Actionability

Highly concrete guidance: named tool 'get_stock_research' on a specified MCP server, per-operation arguments with exact defaults and ranges ('Default 10 trading days, range 3..30'), response shape '{operation, data}', REST routes, and the 'X-WorldMonitor-Key' header. The minor gap is the absence of a literal example invocation or sample response, keeping it just below copy-paste-ready.

4 / 5

Workflow Clarity

The flow is clear (choose operation, construct args, read 'available' before numerical results, retain metadata, report with provenance) with explicit batch handling ('Never silently drop requested tickers; narrow the batch or use jmespath') and error checkpoints ('Respect billing denials, rate limits and Retry-After'). It is not a 5 because the sequence is implied rather than enumerated and there are no explicit validate-then-proceed loops.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed, and its content is well organized into clearly headed sections (Connected plugin, REST and authentication, Errors, Content safety), which per the rubric's simple-skill guidance earns the top anchor.

5 / 5

Total

18

/

20

Passed

Description

80%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 concise, concrete description that names its operations explicitly and includes a clear 'Use when' clause. Its main weaknesses are the narrow trigger clause (history-focused only) and a few missing natural synonyms users might say.

Suggestions

Broaden the 'Use when' clause to cover all four operations, e.g. 'Use when the user asks to research a stock or ticker, run or inspect a technical backtest, or review saved research for a watchlist.'

Add a few natural trigger synonyms such as 'stock analysis' or 'symbol' to improve keyword coverage for users who phrase requests differently.

DimensionReasoningScore

Specificity

The description lists four concrete, distinct operations ('Read current stock research, technical backtests, saved analyses or saved backtests') plus concrete behaviors ('preserve source dates, model limitations and risk factors'), comprehensively covering the skill's operation set with no real gaps, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

It has a clear 'what' (the four read operations) and an explicit 'Use for a named ticker or watchlist research history' trigger, but the 'when' clause only covers history lookup and omits triggers for current analysis or running a backtest, so the 'when' could be more explicit and broader.

4 / 5

Trigger Term Quality

Natural trigger phrases are present ('stock research', 'technical backtests', 'ticker', 'watchlist research history'), but a few natural terms users would say are missing, such as 'stock analysis', 'quotes', 'equities', or 'symbol', placing it between good coverage (4) and comprehensive coverage (5).

4 / 5

Distinctiveness Conflict Risk

Distinctive terms like 'technical backtests', 'ticker', and 'watchlist research history' carve a clear niche, but 'stock research' has minor overlap risk with general web-research or market-quote skills, matching 'mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

17

/

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
koala73/worldmonitor
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.