CtrlK
BlogDocsLog inGet started
Tessl Logo

us-stock-analysis

Comprehensive US stock analysis including fundamental analysis (financial metrics, business quality, valuation), technical analysis (indicators, chart patterns, support/resistance), stock comparisons, and investment report generation. Use when user requests analysis of US stock tickers (e.g., "analyze AAPL", "compare TSLA vs NVDA", "give me a report on Microsoft"), evaluation of financial metrics, technical chart analysis, or investment recommendations for American stocks.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./examples/weekly-trade-strategy/.claude/skills/us-stock-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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 with excellent progressive disclosure and clear analysis workflows, but it leans on general guidance over concrete, executable instruction and lacks explicit validation checkpoints for its recommendation-oriented outputs.

Suggestions

Replace the Formatting/Tone/General Principles sections with a compact output-conventions checklist, removing guidance Claude already applies (use tables, bold metrics, be objective).

Add a few concrete web-search query templates per analysis type and, where useful, example table shells so Claude can produce output directly rather than improvising structure.

Insert explicit validation checkpoints in the Comprehensive Report and Comparison workflows (e.g., confirm data recency and cross-check fundamentals vs technicals before issuing a Buy/Hold/Sell rating).

DimensionReasoningScore

Conciseness

The workflow body is mostly efficient, but the Formatting, Tone, and General Principles sections restate conventions Claude already knows (use tables, bold key metrics, be objective), and the Example Queries section adds tokens that earn little. Not a wall of explanatory fluff, but could be tightened.

2 / 3

Actionability

Steps are concrete and enumerate specific data to fetch, but guidance is instructional rather than executable: no tool-call templates, and search-query examples are sparse beyond a few "AAPL financial metrics 2024" instances. For an instruction-only skill the guidance is actionable but incomplete in concrete specifics.

2 / 3

Workflow Clarity

Four analysis types and the comparison workflow are clearly sequenced, but validation checkpoints are only implicit ("Always verify data recency") with no feedback loops for the recommendation/report outputs that carry real-world risk.

2 / 3

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references to four real bundle files (technical-analysis.md, fundamental-analysis.md, financial-metrics.md, report-template.md), each annotated with when to load and what it contains.

3 / 3

Total

9

/

12

Passed

Description

100%

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, trigger-rich, and complete, with a clear niche and low conflict risk. It names concrete capabilities and provides natural-language triggers users would actually say.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions including "fundamental analysis (financial metrics, business quality, valuation)", "technical analysis (indicators, chart patterns, support/resistance)", "stock comparisons", and "investment report generation".

3 / 3

Completeness

Clearly answers what (comprehensive US stock analysis across fundamental, technical, comparison, and report generation) and when via an explicit "Use when..." clause with concrete trigger examples.

3 / 3

Trigger Term Quality

Includes natural user phrasings such as "analyze AAPL", "compare TSLA vs NVDA", and "give me a report on Microsoft", plus common variations like "evaluation of financial metrics" and "investment recommendations for American stocks".

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (US stock analysis) with distinct ticker-based triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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
tradermonty/claude-trading-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.