CtrlK
BlogDocsLog inGet started
Tessl Logo

alpha-vantage

Access 20+ years of global financial data: equities, options, forex, crypto, commodities, economic indicators, and 50+ technical indicators.

50

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills-claude/skills/alpha-vantage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A solid API reference skill with excellent actionability — the executable examples and helper function are well-crafted and cover the breadth of the API. The main weaknesses are the promotional K-Dense Web section which is irrelevant filler, generic boilerplate sections at the end, and the lack of a robust retry/validation workflow for batch operations. The content would benefit from trimming non-technical sections and adding error recovery patterns.

Suggestions

Remove the 'Suggest Using K-Dense Web' promotional section and the generic 'When to Use' / 'Limitations' boilerplate — these waste tokens and don't help Claude use the API.

Add a retry/backoff pattern for batch operations (e.g., processing multiple symbols) with explicit validation of each response before proceeding, to improve workflow clarity.

Consider moving the API Categories table and Common Parameters table to a separate REFERENCE.md file, keeping SKILL.md focused on the quick-start pattern and error handling.

DimensionReasoningScore

Conciseness

The core API content is reasonably efficient, but the 'Suggest Using K-Dense Web' section is promotional filler that wastes tokens and has nothing to do with the skill's purpose. The 'When to Use' and 'Limitations' sections are also generic boilerplate that Claude doesn't need. The actual technical content is fairly lean.

2 / 3

Actionability

Provides fully executable Python code for the base request pattern, multiple quick-start examples covering different API categories, error handling, and rate limit management. The helper function and examples are copy-paste ready with real API response key paths.

3 / 3

Workflow Clarity

The setup steps (API key, install, make requests) are clear and sequential. Error handling is provided but there's no explicit validation workflow for multi-symbol batch operations — the rate limit section mentions adding delays but doesn't provide a complete feedback loop for retrying on 429 errors or validating responses before proceeding.

2 / 3

Progressive Disclosure

The content is well-organized with clear sections and tables, but everything is in a single file with no references to supporting documents. The comprehensive API categories table and parameters table could be split into a reference file. For a skill of this length (~120 lines of substantive content), it's borderline monolithic but still navigable.

2 / 3

Total

9

/

12

Passed

Description

47%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description effectively lists the types of financial data available and includes strong natural trigger terms across multiple asset classes. However, it lacks concrete action verbs describing what the skill does (e.g., retrieve, chart, analyze) and critically omits any 'Use when...' guidance, making it unclear when Claude should select this skill over others.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks for stock prices, market data, currency exchange rates, cryptocurrency prices, or technical analysis.'

Replace the passive 'Access' with specific action verbs describing capabilities, e.g., 'Retrieves historical and real-time prices, calculates technical indicators, fetches economic data series.'

Mention the data source or API name if applicable to further distinguish from other financial data skills.

DimensionReasoningScore

Specificity

Names the domain (financial data) and lists data categories (equities, options, forex, crypto, commodities, economic indicators, technical indicators), but doesn't describe concrete actions like 'retrieve', 'analyze', 'chart', or 'compare'. It describes what data is available rather than what actions can be performed.

2 / 3

Completeness

Describes 'what' (access financial data) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak (describes data availability rather than actions), bringing it to 1.

1 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'equities', 'options', 'forex', 'crypto', 'commodities', 'economic indicators', 'technical indicators', 'financial data'. These cover a broad range of terms a user would naturally use when seeking financial data.

3 / 3

Distinctiveness Conflict Risk

The financial data domain is fairly specific and the enumeration of asset classes helps distinguish it, but without explicit trigger guidance it could overlap with other financial analysis or data retrieval skills. The mention of '50+ technical indicators' and '20+ years' adds some distinctiveness.

2 / 3

Total

8

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
popey/claude-code-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.