CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

alpha-vantage

Alpha Vantage integration. Manage data, records, and automate workflows. Use when the user wants to interact with Alpha Vantage data.

Quality

69%

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/alpha-vantage/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is a strong, command-driven integration guide with genuinely good state-handling and error-recovery guidance for the connection workflow. Its main weaknesses are redundant catalog content (endpoint overview vs. actions table), a generic placeholder example for running actions, and broken step numbering.

Suggestions

Replace the placeholder run example with a real invocation, e.g. `membrane action run get-stock-quote --connectionId=CONNECTION_ID --input '{"symbol": "AAPL", "datatype": "json"}' --json`, so the full connection-to-output path is copy-paste runnable.

Merge or trim the duplicated catalogs: the "Alpha Vantage Overview" endpoint list largely restates the Popular actions table — keep one, and if the skill grows, move the full action catalog to a reference file.

Fix the step numbering (label the connect section as Step 1, "1b" as "1a" or Step 2, and define where "Step 2" actually is) so the cross-references resolve.

DimensionReasoningScore

Conciseness

The body is mostly command-focused and efficient, but the intro ("Alpha Vantage provides real-time and historical stock market data and analytics. It's used by developers and financial analysts...") explains what Claude already knows, and the 17-line endpoint overview duplicates the popular-actions table. Fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, since two sections could be trimmed or merged.

3 / 5

Actionability

Concrete, executable commands throughout — `npm install -g @membranehq/cli@latest`, `membrane connection ensure "http://alphavantage.co" --json`, the proxy flags table — covering the common workflow. It misses 5 because there is no worked end-to-end example: the run example uses placeholders (`--input '{"key": "value"}'`) and never demonstrates running one of the listed actions with a real key like get-stock-quote and a real input.

4 / 5

Workflow Clarity

The install → login → connection → action-search → run → proxy sequence is clear, with explicit checkpoint branching on connection state (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and re-poll feedback loops. Minor gap: the step numbering is broken — "skip to **Step 2**" references a Step 2 that is never labeled, and section "1b" has no "1a" — so it sits at 'clear sequence with most checkpoints; minor validation gaps' rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well-sectioned with clear headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) making navigation easy. The inline endpoint catalog plus the 15-row actions table is catalog content that could be consolidated or split out, which keeps it at 'good structure; most content appropriately placed; minor organization gaps' rather than 5.

4 / 5

Total

15

/

20

Passed

Description

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

The description names a specific niche and includes an explicit 'Use when' clause, but the capability statement is pure buzzword filler. Almost all of its discriminative power comes from the 'Alpha Vantage' name itself rather than from concrete actions or natural trigger synonyms.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete capabilities, e.g. "Fetch stock quotes, daily/intraday time series, technical indicators (EMA, RSI, SMA), earnings data, forex and crypto exchange rates, and market news sentiment via the Alpha Vantage API."

Expand the 'when' clause with natural trigger phrases users actually say, e.g. "Use when the user mentions stock prices, market data, tickers, technical indicators, forex or crypto rates, or wants financial/earnings data."

Drop the circular "interact with Alpha Vantage data" phrasing — it only fires when the user already said the skill's name, adding no trigger coverage.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" are generic actions with no concrete Alpha Vantage capabilities (e.g. fetching stock quotes, technical indicators, or exchange rates), matching the anchor 'names the domain but actions are minimal or generic'. It does not reach 3 because no concrete action is tied to what the API actually offers.

2 / 5

Completeness

Both parts are explicitly present: what ("Alpha Vantage integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Alpha Vantage data"). The 'when' clause is explicit so it clears the 3-cap, but the 'what' is vague and the 'when' is circular (triggers only when the user already names Alpha Vantage), so it falls short of 5's concrete trigger phrases.

4 / 5

Trigger Term Quality

"Alpha Vantage", "data", and "records" are relevant keywords, but common natural phrases users would say — "stock quotes", "market data", "ticker", "forex", "crypto prices" — are missing. This fits 'some relevant keywords but missing common variations or synonyms' rather than 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

"Alpha Vantage integration" carves out a clear niche with minimal conflict risk against unrelated skills, but the generic tail "Manage data, records, and automate workflows" creates minor overlap with any data-management or automation skill. This is 'mostly distinct; minor overlap risk' rather than 5's clear niche with distinct triggers.

4 / 5

Total

13

/

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

membranedev/application-skills

Path

skills/alpha-vantage/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.