Name: token
Rating: 50.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

token

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

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

61%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 content is mostly actionable with executable membrane CLI commands and a coherent connection workflow, but it is undermined by a stray refusal sentence, a hollow placeholder overview, a broken "Step 2" reference, and missing verification steps for potentially destructive Token operations. Cleaning up the noise and adding validation checkpoints would materially raise the score.

Suggestions

Remove the stray refusal line ("I don't have enough information to do that. Can you tell me more about the app?") and the empty "Token Overview" placeholder, or replace them with real Token-specific actions and parameters.

Fix the broken "skip to Step 2" reference by labeling the post-connection section as Step 2, and remove or relabel the orphaned "1b" heading.

Add a validation/verification checkpoint after running actions (e.g. inspect the `output` field and confirm the expected state) since transfers and transactions are destructive/irreversible Token operations.

Dimension	Reasoning	Score
Conciseness	The bulk of CLI commands is reasonably lean, but the body opens with a stray refusal sentence ("I don't have enough information to do that") and includes a hollow "Token Overview" placeholder ("Use action names and parameters as needed") that add noise without value.	3 / 5
Actionability	It provides concrete, executable membrane CLI commands (install, login, connection ensure, action run) plus a proxy flag table, with only minor gaps such as unresolved placeholders (<actionId>) and no Token-specific action examples.	4 / 5
Workflow Clarity	A connect-to-poll-to-READY sequence is present with state branching, but it references an undefined "Step 2" and provides no validation/verification step after running actions that can mutate Token data (transfers/transactions), which caps this dimension at 3.	3 / 5
Progressive Disclosure	As a single-file skill with no bundle files, it is organized into clear sections (Overview, Working with Token, Popular actions, Best practices) with most content appropriately placed, though some reference-like material (proxy flags, connection states) is inlined.	4 / 5
	Total	14 / 20 Passed

Description

50%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 identifies the app and includes an explicit "Use when" clause, but its actions are generic ("manage data, records, automate workflows") and the trigger phrasing is vague, so it lands at the midpoint across most dimensions. Concrete Token-specific verbs (transfer funds, list wallets, fetch transactions) would lift specificity, trigger quality, and distinctiveness.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Token capabilities such as initiating transfers, reading wallet balances, or listing transactions.

Expand the trigger clause with natural user phrasing and synonyms, e.g. "Use when the user wants to send or check Token transfers, view wallet addresses, or query transaction history."

Tie the "when" to specific verbs/entities (transfers, wallets, transactions) to reduce overlap with other data-management skills.

Dimension	Reasoning	Score
Specificity	It names the Token domain and a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic and abstract rather than concrete Token-specific capabilities.	3 / 5
Completeness	It provides both a "what" (manage data, records, automate workflows) and a "when" ("Use when the user wants to interact with Token data"), but the "what" is vague and the "when" is generic rather than tied to concrete triggers.	3 / 5
Trigger Term Quality	"interact with Token data" is a relevant keyword but common variations or synonyms (transfers, wallets, transactions) that users would naturally say are missing.	3 / 5
Distinctiveness Conflict Risk	The app name "Token" plus broad phrases like "Manage data, records" overlap with many generic data-management skills, leaving moderate conflict risk despite the named app.	3 / 5
	Total	12 / 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/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.