fundamentals

Get fundamental financial data including financials, earnings, and key metrics. Use when user asks about financials, earnings, revenue, profit, balance sheet, income statement, or company fundamentals.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

67%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 with executable commands and real bundle scripts. The main weakness is mild verbosity from restating the Piotroski concept and a 'Use Cases' section that could be trimmed.

Suggestions

Remove or merge the 'What is Piotroski F-Score?' paragraph since the intro line and the 9-criteria list already convey the same information.

Trim the 'Use Cases' bullet list, which duplicates trigger guidance already present in the description frontmatter.

Add one worked example with a real ticker symbol to lift actionability from concrete-but-templated to fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes redundant explanation: the 'What is Piotroski F-Score?' paragraph restates the intro and the 9-criteria list, and the 'Use Cases' section adds mild padding.	3 / 5
Actionability	Provides concrete, executable commands ('uv run python scripts/fundamentals.py SYMBOL [--type TYPE]') with documented arguments and output schema; minor gap is the absence of a worked example with a real symbol.	4 / 5
Workflow Clarity	Each capability is a single unambiguous command with a clear post-step ('Present key metrics clearly'), and the uv fallback note is helpful; no validation checkpoints, but operations are read-only so the destructive-cap does not apply.	4 / 5
Progressive Disclosure	Well-organized into labeled sections with script references (scripts/fundamentals.py, scripts/piotroski.py) that resolve to real bundle files; all reference content is inline with no separate reference docs, which is acceptable for this size but leaves minor organization headroom.	4 / 5
	Total	15 / 20 Passed

Description

95%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, third-person description that clearly states capabilities and provides a rich set of natural trigger terms. Minor specificity gap in that it describes data categories rather than a range of distinct actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('fundamental financial data') and lists several concrete data categories ('financials, earnings, and key metrics'), though it is a single 'Get' action rather than a breadth of distinct operations.	4 / 5
Completeness	Explicitly answers both what ('Get fundamental financial data including financials, earnings, and key metrics') and when ('Use when user asks about...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms: 'financials, earnings, revenue, profit, balance sheet, income statement, or company fundamentals' are phrases users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear fundamentals niche with specific trigger terms (balance sheet, income statement, Piotroski-relevant metrics) giving minimal overlap risk with non-fundamental skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/fundamentals/SKILL.md
Commit: 9a1bf57

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.