CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dexpaprika-api

Access DeFi data from DexPaprika: token prices, liquidity pools, OHLCV, transactions across 34+ blockchains and 30M+ pools. Free, no API key needed. Install MCP: add https://mcp.dexpaprika.com/sse as SSE server, or install plugin: /plugin marketplace add coinpaprika/claude-marketplace

Quality

80%

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

Quality

Content

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

A lean, well-structured body that is immediately usable: executable setup, a complete tool catalog, and practical quick-reference facts. The only improvement space is showing one or two example tool invocations with real arguments so first use requires no guesswork.

DimensionReasoningScore

Conciseness

Every line earns its place: copy-paste setup config, one-line tool descriptions, a compact network-ID line, and rate-limit facts, with no explanation of concepts Claude already knows.

5 / 5

Actionability

Setup is fully executable (JSON config block and plugin commands) and all 14 tools are named, but no example invocations with arguments (e.g. getPoolOHLCV with a pool address and interval) are shown, leaving minor gaps.

4 / 5

Workflow Clarity

Two clearly sequenced setup paths followed by an unambiguous tool inventory and common network IDs; a short example task flow (e.g. search -> getPoolDetails -> getPoolOHLCV) would close the remaining gap.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references; content is cleanly organized into well-labeled sections (Setup, Tools, Networks, Rate Limits) with no inlined material that belongs in separate files.

5 / 5

Total

18

/

20

Passed

Description

66%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 delivers a concrete, quantified "what" with mostly natural trigger vocabulary, but it never tells Claude when to reach for the skill, and it is phrased around installation mechanics rather than use cases. Adding an explicit trigger clause and a few more user-side synonyms would move it to the top of the scale.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks about token prices, liquidity pools, DEX trading activity, or historical candles (OHLCV) on any blockchain.'

Include common synonyms users say, such as 'crypto prices', 'DEX', 'swaps', or 'trading volume', to strengthen trigger-term coverage.

Lead with the use case rather than installation: move the MCP/plugin install instructions to the end of the description so the capability statement and triggers come first.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("token prices, liquidity pools, OHLCV, transactions across 34+ blockchains and 30M+ pools") with quantified scope, but omits capabilities the body covers (search, DEX-level pools, platform stats), leaving minor coverage gaps.

4 / 5

Completeness

The "what" is clear (access DeFi data of the listed types), but there is no "Use when..." clause or equivalent trigger guidance, which caps this dimension at 3.

3 / 5

Trigger Term Quality

"DeFi", "token prices", "liquidity pools", "OHLCV", "transactions" are terms users would naturally say; common variations like "crypto prices", "DEX", "swaps", or "TVL" are missing.

4 / 5

Distinctiveness Conflict Risk

Names a specific service ("DexPaprika") and a distinct niche (on-chain DeFi/pool data), with only minor overlap risk against closely related crypto-price or market-data skills.

4 / 5

Total

15

/

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

davepoon/buildwithclaude

Path

plugins/all-skills/skills/dexpaprika-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.