claude/skills/yfin/SKILL.md
Small Yahoo Finance CLI for ticker info + N-year stock returns. Use when the user asks about: stock price, market cap, sector/industry classification, dividend yield, P/E ratio, beta, 52-week range, N-year stock return, company description for a public company. Triggers: 'yfinance', 'yfin', 'stock price', 'market cap of', 'how much has X stock returned', 'sector for ticker', 'industry classification'. Pairs with the levels-fyi skill for cross-checking public/private status (levels gives ticker, yfin returns live data).
npx skillsauth add kendreaditya/.config yfinInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Small wrapper around the yfinance Python package. Wraps Ticker.info and Ticker.history into a clean JSON CLI.
yfin info <ticker> [--full] — curated company info (sector, industry, market cap, description, HQ, employees, P/E, beta, 52w range)yfin returns <ticker> [--years 1 2 3 4] — N-year stock returns as percent changeyfin all <ticker> [--years 1 2 3 4] — info + returns combined (the most useful call for ranking pipelines)yfin info META # Curated info
yfin info META --full # All ~150+ yfinance fields
yfin returns META --years 1 2 3 5 # Custom year windows
yfin all GOOGL # info + returns
yfin all META | jq '.sector, .returns."2y_return_pct"'
ticker field → enrich with live data.1y_return_pct, 2y_return_pct, etc.levels company-overview for those.Ticker.info exposes (use --full first; if missing, query SEC EDGAR directly).JSON to stdout, indented. Pipe through jq for further filtering.
ticker from levels company-overview <slug>, then pass to yfin all <ticker> for live data.yfin = numbers, blind = stories).yfinance installed in ~/workspace/.venv (already done; reinstall via ~/workspace/.venv/bin/pip install yfinance).info dicts; check before parsing.auto_adjust=True and ~252 trading days per year (not exact).testing
Reviews test coverage and suggests missing test cases for error paths, edge cases, and business logic. Activates when users write tests or implement new features.
development
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.
tools
Comprehensive security scanning and vulnerability detection. Includes input validation, path traversal prevention, CVE detection, and secure coding pattern enforcement. Use when: authentication implementation, authorization logic, payment processing, user data handling, API endpoint creation, file upload handling, database queries, external API integration. Skip when: read-only operations on public data, internal development tooling, static documentation, styling changes.
development
Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.