Name: token-metrics
Rating: 56.8 (1 reviews)
Author: membranedev

token-metrics

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/token-metrics/SKILL.md

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-structured, mostly executable guide to driving Token Metrics through the Membrane CLI, with a strong connection-state workflow. Its main weaknesses are an unnecessary background paragraph and a thin Popular Actions section that tells rather than shows.

Suggestions

Cut the opening background paragraph ("Token Metrics is a cryptocurrency research platform...") and the marketing phrase about auth plumbing; assume Claude knows what a crypto analytics platform is.

Populate the "Popular actions" section with 3-5 concrete example actions (e.g. query portfolio, run screener, add watchlist asset, set alert) with sample `membrane action run` invocations instead of only a discovery command.

Add a brief validation note after `action run` (e.g. check the `output` field and error states) to close the workflow-clarity gap for action execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it opens with an unnecessary background paragraph ("Token Metrics is a cryptocurrency research platform...") and contains light marketing prose ("so you can focus on the integration logic rather than auth plumbing") that could be trimmed, matching the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	It provides copy-paste-ready CLI commands (install, login, connection ensure, action run, request) plus a flags table, but the "Popular actions" section only tells the reader to discover actions rather than listing concrete examples, leaving a minor gap below the fully-comprehensive level.	4 / 5
Workflow Clarity	The connection setup is a clear state machine with polling and a CLIENT_ACTION_REQUIRED feedback loop (re-poll after the user acts), but action execution lacks explicit result-validation checkpoints, so it sits just below the full feedback-loop anchor of 5.	4 / 5
Progressive Disclosure	As a single self-contained file with no bundle files present, it is well organized into clear sections (Overview, Install, Auth, Connecting, Searching, Running actions, Proxy, Best practices) with content appropriately inline for this scope, matching the good-structure anchor with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

62%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/when structure and leverages a named product for distinctiveness, but its capability list is generic and trigger coverage is limited to the single product name. It is solid but not exemplary.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with 2-4 concrete capabilities the integration actually exposes (e.g. query portfolio assets, screen coins, manage watchlists, set price alerts).

Expand the trigger phrase with natural synonyms users say, e.g. "Use when the user wants crypto analytics, Token Metrics portfolio data, coin screener results, or watchlist/alert management."

Use third-person action verbs consistently and avoid padding words to keep the description lean.

Dimension	Reasoning	Score
Specificity	Names the domain ("Token Metrics integration") and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete capabilities, fitting the anchor for naming the domain with 1-2 minimal actions.	3 / 5
Completeness	Both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Token Metrics data") are present, but the what is generic so it does not reach the fully concrete trigger-phrase level of 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Token Metrics data" provides the natural product keyword but lacks synonyms or variations beyond the single product name, matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named Token Metrics product gives it a clear niche with minimal conflict risk, though the generic verbs ("manage data, records") leave minor overlap with other data-integration skills rather than the fully distinct niche of 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/token-metrics/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.