CtrlK
BlogDocsLog inGet started
Tessl Logo

twelvedata-api

Twelve Data financial API for stocks, forex, crypto, ETFs, and 100+ technical indicators. Use when fetching time series data, technical analysis, fundamentals, or real-time streaming quotes.

60

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/twelvedata-api/SKILL.md

The canonical home for this skill is twelvedata-api in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 is highly actionable with broad, mostly executable Python examples and good section structure, but it fails at progressive disclosure: both bundle files are orphaned, and the inline endpoint tables duplicate references/ENDPOINTS.md. Batch workflows lack validation loops, and time-sensitive pricing is inlined without framing.

Suggestions

Replace the inline 'API Endpoints Reference' tables with a one-line pointer to references/ENDPOINTS.md (e.g., '**Full endpoint reference**: See [ENDPOINTS.md](references/ENDPOINTS.md)) and link the client script under a 'Ready-made client' section so both bundle files are discoverable.

Fold the Error Handling validation pattern (status-code check, credit headers, retry) into the batch request task so batch workflows include an explicit validate-then-fix feedback loop, and note per-symbol error handling for multi-symbol responses.

Move the rate-limit and pricing tables into references/ENDPOINTS.md or a 'deprecated/plans may change' framing so time-sensitive dollar amounts don't sit unqualified in the main body, and trim Free vs Premium to the few distinctions that change code behavior.

DimensionReasoningScore

Conciseness

The prose and code are mostly lean, but the inline "API Endpoints Reference" tables (~35 lines) duplicate the 318-line references/ENDPOINTS.md, and the rate-limit/pricing tables ("Grow ($29)", "Pro ($99)", "Enterprise ($329)") are time-sensitive information presented without any deprecated-section framing. This is 'mostly efficient but includes some unnecessary content that could be tightened' rather than noticeably padded with explanations of known concepts.

3 / 5

Actionability

Code is concrete and largely executable across auth, quotes, time series, chained indicators, batch, fundamentals, forex, crypto, symbol search, WebSocket, and error handling. It is not fully copy-paste ready: several task snippets depend on globals (API_KEY, td, BASE_URL) defined only in earlier sections, and the ready-made scripts/twelvedata_client.py is never leveraged — minor gaps consistent with the score-4 anchor.

4 / 5

Workflow Clarity

The Quick Start (auth → basic usage → SDK) is clearly sequenced and an Error Handling section demonstrates status-code and credit validation, but the batch workflow ("Up to 120 symbols per request") has no validation or feedback loop of its own. Per the rubric, missing validation in batch operations caps workflow clarity at 3 even though sequencing is present.

3 / 5

Progressive Disclosure

The bundle contains references/ENDPOINTS.md (318 lines) and scripts/twelvedata_client.py (436 lines), yet the body never links to or mentions either file; instead it inlines its own endpoint tables that duplicate ENDPOINTS.md. Content that clearly belongs in the separate reference file is inlined while the actual reference and script are orphaned and undiscoverable, matching the score-2 anchor.

2 / 5

Total

12

/

20

Passed

Description

88%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: concise, third-person, with an explicit 'Use when...' clause and concrete capability and asset-class coverage. The only weaknesses are a few missing natural synonyms and mild overlap risk with other financial-data skills on generic trigger phrases.

DimensionReasoningScore

Specificity

"Twelve Data financial API for stocks, forex, crypto, ETFs, and 100+ technical indicators. Use when fetching time series data, technical analysis, fundamentals, or real-time streaming quotes" names the domain plus four concrete capability areas across five asset classes. This matches the comprehensive-coverage anchor rather than the score-4 anchor, which reserves 'minor gaps' for descriptions missing one of the main functions.

5 / 5

Completeness

It explicitly answers "what" (financial API for stocks, forex, crypto, ETFs, 100+ indicators) and "when" ("Use when fetching time series data, technical analysis, fundamentals, or real-time streaming quotes") with concrete trigger phrases, matching the top anchor. It is not the score-4 anchor because the "when" clause is already specific, not merely present.

5 / 5

Trigger Term Quality

Natural terms present include "stocks", "forex", "crypto", "ETFs", "time series data", "fundamentals", and "real-time streaming quotes". A few common user phrasings are missing (e.g., "market data", "historical prices", "quotes" standalone), which is the good-but-incomplete keyword coverage anchor rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Naming the vendor "Twelve Data" gives a distinct trigger, but generic finance triggers like "fetching time series data" and "technical analysis" overlap closely with sibling skills (finnhub-api, alphavantage-api, fmp-api). This is the 'mostly distinct; minor overlap risk with closely related skills' anchor rather than minimal conflict risk.

4 / 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
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.