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

83%

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

71%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, appropriately layered skill body: workflows are clearly sequenced and detailed material is correctly pushed into one-level-deep reference files that all exist. The main weakness is token efficiency — it re-teaches basic technical analysis concepts and carries redundant sections (Example Queries, duplicated reference listings) that could be cut without losing guidance value.

Suggestions

Remove or drastically shorten the "Example Queries" section — it duplicates the description's trigger examples and each workflow's "When to Use" clause — and delete the duplicated inline reference mentions, keeping only the "Reference Files" summary section.

Cut explanations of concepts Claude already knows, e.g., "RSI: Overbought (>70) or oversold (<30)", "Reversal patterns (head and shoulders, double top/bottom)", and "Uptrend, downtrend, or sideways"; the existing references/technical-analysis.md already owns these definitions.

State the shared data-gathering steps once (in "Data Sources") and have each workflow reference them, instead of repeating "Follow data gathering steps" / "Gather data for all stocks" variations across workflows.

DimensionReasoningScore

Conciseness

"RSI: Overbought (>70) or oversold (<30)", "Reversal patterns (head and shoulders, double top/bottom)", and "Uptrend, downtrend, or sideways" explain technical concepts Claude already knows, and the "Example Queries" section largely restates the description's triggers while reference files are listed both inline in workflows and again in "Reference Files". Mostly efficient with a clear structure, but several sections could be trimmed or removed, keeping it at anchor 3 rather than 4.

3 / 5

Actionability

Concrete guidance throughout: specific search examples ("AAPL financial metrics 2024", "AAPL technical analysis"), enumerated data items (P/E, EPS, PEG, EV/EBITDA), named quality sources, and explicit output/report structures. For an instruction-only, search-driven skill the guidance is mostly executable; a few steps remain high-level ("Estimate fair value range", "Present in concise summary format"), so it stops short of anchor 5.

4 / 5

Workflow Clarity

Four analysis workflows plus a comparison workflow, each with an explicit "When to Use" clause and numbered steps, and a data-quality checkpoint ("Always verify data recency"). The sequence is clear with most checkpoints present, but there is no validation/error-recovery loop (e.g., what to do when data cannot be found or conflicts), so anchor 4 rather than 5. No destructive or batch operations exist, so no cap applies.

4 / 5

Progressive Disclosure

All four referenced files (references/fundamental-analysis.md, references/financial-metrics.md, references/technical-analysis.md, references/report-template.md) exist and are one level deep; the "Reference Files" section signals each with when/contains metadata, and detail (metric formulas, report templates, analytical frameworks) is appropriately deferred to those files rather than inlined. This matches the clear-overview, well-signaled reference pattern of anchor 5.

5 / 5

Total

16

/

20

Passed

Description

87%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 that clearly states both capability scope and trigger conditions with concrete example queries. The structure mirrors the exemplar pattern (what + "Use when..." with examples). Only minor headroom exists in trigger synonym coverage and action-level specificity.

DimensionReasoningScore

Specificity

"fundamental analysis (financial metrics, business quality, valuation), technical analysis (indicators, chart patterns, support/resistance), stock comparisons, and investment report generation" lists several specific capabilities with parenthetical detail across all four analysis types. Not 5 because the stated actions are domain-level categories rather than maximally concrete operations; not 3 because coverage spans every capability the skill claims.

4 / 5

Completeness

Explicitly answers what ("Comprehensive US stock analysis including fundamental analysis... technical analysis... stock comparisons, and investment report generation") and when ("Use when user requests analysis of US stock tickers (e.g., 'analyze AAPL'...)") with concrete trigger phrases, exactly matching the anchor-5 pattern. Neither what nor when is vague or merely implied.

5 / 5

Trigger Term Quality

Concrete example phrases like "analyze AAPL", "compare TSLA vs NVDA", "give me a report on Microsoft" plus natural terms ("financial metrics", "technical chart analysis", "investment recommendations") give good keyword coverage. A few common user phrasings ("stock price", "is X overvalued", "should I buy") are missing, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"US stock tickers" and "investment recommendations for American stocks" with ticker examples (AAPL, TSLA vs NVDA, Microsoft) carve a clear niche with distinct triggers and minimal conflict risk against generic document or data skills. Third-person voice is maintained throughout, so no specificity penalty applies.

5 / 5

Total

18

/

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.

Validation — 16 / 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.