CtrlK
BlogDocsLog inGet started
Tessl Logo

nasdaq-data-link

Nasdaq Data Link integration. Manage Datasets. Use when the user wants to interact with Nasdaq Data Link data.

55

Quality

62%

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 ./skills/nasdaq-data-link/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 well-organized, executable CLI guide with a sound connection-readiness workflow and feedback loop. Its main weaknesses are mild verbosity in introductory/explanatory prose, the absence of a concrete end-to-end data query example, and slightly inconsistent step numbering.

Suggestions

Cut conceptual padding: remove the introductory paragraph about who uses Nasdaq Data Link and the "When to use which actions" filler line.

Add one fully concrete worked example, e.g. `membrane action run <actionId> --connectionId=... --input '{"table":"WIKI/AAPL"}' --json`, so Claude sees a real data query.

Fix the step numbering (label Step 1 explicitly, or renumber the "1b"/"Step 2" references) so the workflow reads as a coherent sequence.

DimensionReasoningScore

Conciseness

Most of the body is concrete commands, but it includes unnecessary padding such as the introductory paragraph on what Nasdaq Data Link is, the filler line "When to use which actions: Use action names and parameters as needed.", and "so you can focus on the integration logic rather than auth plumbing."

3 / 5

Actionability

It provides copy-paste-ready commands for install, auth, connection, search, run, and proxy plus a flags table, but every example is templated with CONNECTION_ID/<actionId> and no concrete worked data query (e.g., fetching a real table) is shown.

4 / 5

Workflow Clarity

There is a clear install -> auth -> connect -> poll-for-ready -> search -> run sequence with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but step numbering is inconsistent ("skip to Step 2" with no labeled Step 1, a lone "1b").

4 / 5

Progressive Disclosure

No bundle files exist, so the skill is a single well-sectioned SKILL.md with clear headers covering each phase; structure is good, though some bulk (the clientAction field breakdown, the proxy flags table) is inlined rather than split into reference files.

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 correctly pairs a what and a when clause and leverages a distinctive product name, but its capability list is thin ("Manage Datasets") and its triggers lack natural synonyms. It is solid but not exemplary.

Suggestions

Replace the generic "Manage Datasets" with 2-3 concrete actions (e.g., "Query time-series tables, list datasets, fetch bulk data").

Expand the "Use when..." clause with natural trigger terms users actually say (financial data, economic data, stock prices, .csv exports).

Add file-format or data-type keywords (e.g., time series, tables, .csv) to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Manage Datasets" is a single generic action that names the domain (Nasdaq Data Link) but offers minimal, non-specific capability description, matching the anchor whose actions are minimal or generic.

2 / 5

Completeness

Both a "what" ("Nasdaq Data Link integration. Manage Datasets.") and an explicit "when" ("Use when the user wants to interact with Nasdaq Data Link data.") are present, but the when clause only restates the product name rather than giving concrete, varied triggers.

4 / 5

Trigger Term Quality

It surfaces relevant keywords ("Nasdaq Data Link", "Datasets", "data") but misses common natural synonyms a user might say (financial data, economic data, stock data, time series).

3 / 5

Distinctiveness Conflict Risk

Naming a specific product ("Nasdaq Data Link") gives it a clear niche with minor overlap risk against other financial-data skills, though the trigger language is narrow and product-name-only.

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.

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