CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

finnhub-api

FinnHub financial data API integration for stocks, forex, crypto, news, and fundamentals. Use when fetching real-time quotes, company profiles, financial statements, insider trading, earnings calendars, or market news.

Quality

79%

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 ./skills/finnhub-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The body delivers executable, well-organized guidance for common FinnHub tasks, but it ignores its own bundle: references/ENDPOINTS.md and scripts/finnhub_client.py are never referenced, while ~60 lines of endpoint tables duplicate the reference file inline. Code snippets are mostly copy-paste ready but a few lack imports and context to run standalone.

Suggestions

Replace the inline 'API Endpoints Reference' tables with a pointer to references/ENDPOINTS.md (e.g., 'See references/ENDPOINTS.md for full endpoint parameters and response fields'), removing the duplicated content.

Reference the existing scripts/finnhub_client.py in the body so Claude knows a ready-made client is available instead of rebuilding request logic from snippets.

Make code snippets self-contained: add 'import time' and the API_KEY/BASE_URL setup to the error-handling example so it runs as-is.

DimensionReasoningScore

Conciseness

The task recipes are lean and assume Claude's competence, but roughly 60 lines of inline endpoint tables ('API Endpoints Reference', 'Free vs Premium Features') duplicate content that already exists in references/ENDPOINTS.md and could be trimmed to pointers.

3 / 5

Actionability

Recipes are concrete and executable across common cases (quotes, candles, news, metrics, WebSocket, auth), but some snippets are not self-contained — safe_api_call uses time.sleep and API_KEY without importing time or defining the key in scope.

4 / 5

Workflow Clarity

The auth → install → task sequence is clear and the error-handling section includes a 429 retry loop, but there are no explicit validation checkpoints; this is acceptable for a read-only data-fetching skill, just short of the top anchor.

4 / 5

Progressive Disclosure

Section headers give the body reasonable structure, but the body inlines a full endpoint reference while the bundle's references/ENDPOINTS.md and scripts/finnhub_client.py are never mentioned anywhere in the body — separate content is inlined and bundle references are not signaled.

3 / 5

Total

14

/

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 explicitly covers what the skill does and when to use it, with a named provider giving it a distinct trigger niche. Trigger-term coverage is good but lacks a few common synonyms users might naturally say.

DimensionReasoningScore

Specificity

The description lists several specific capabilities ('fetching real-time quotes, company profiles, financial statements, insider trading, earnings calendars, or market news'), but relies on a single action verb applied to objects rather than multiple distinct concrete actions, so it falls just short of the comprehensive anchor.

4 / 5

Completeness

It explicitly answers both 'what' ('FinnHub financial data API integration for stocks, forex, crypto, news, and fundamentals') and 'when' with a concrete 'Use when fetching...' trigger clause listing specific use cases, matching the top anchor closely.

5 / 5

Trigger Term Quality

Good coverage of natural user phrases ('real-time quotes', 'company profiles', 'earnings calendars', 'market news', 'stocks', 'forex', 'crypto'), but common variations like 'stock price', 'ticker', or 'analyst ratings' are missing, so it does not reach comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Naming the specific provider (FinnHub) with provider-scoped data categories creates a clear niche with distinct triggers and minimal conflict risk against generic market-data skills.

5 / 5

Total

18

/

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

fernandezbaptiste/Skrillz

Path

skills/finnhub-api/SKILL.md

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.