CtrlK
BlogDocsLog inGet started
Tessl Logo

tatum

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

49

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/tatum/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 highly actionable with concrete Membrane CLI commands and a clear connection-setup workflow, but it is let down by inlined reference material, some promotional padding, and a lack of validation guidance for destructive blockchain operations.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive actions, e.g. 'Before running send/transfer/burn actions, confirm the recipient address and amount with the user and inspect the action inputSchema.'

Move the full 'Tatum Overview' action catalog into a references file (e.g. ACTIONS.md) and keep only a concise category summary in SKILL.md with a clearly signaled link.

Trim promotional filler ('burn less tokens and make communication more secure', 'focus on the integration logic rather than auth plumbing', 'Use action names and parameters as needed.') to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands throughout, but includes padding such as the promotional 'so you can focus on the integration logic rather than auth plumbing', 'burn less tokens and make communication more secure', and the filler line 'Use action names and parameters as needed.'

3 / 5

Actionability

It provides copy-paste-ready commands for install, login, connection ensure, polling, action search/run, and proxy requests with a flags table; the minor gap is that no concrete Tatum-specific action (e.g. an actual NFT mint with real input) is shown end-to-end.

4 / 5

Workflow Clarity

The connection setup is well sequenced with state-check checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but destructive blockchain operations (send transaction, transfer, burn) lack any validation or user-confirmation step, which caps this dimension at 3.

3 / 5

Progressive Disclosure

Section headers give reasonable navigation, but the ~65-line 'Tatum Overview' action catalog is inlined content that would better live in a separate reference file, and there are no external references or signaled navigation to deeper material.

3 / 5

Total

13

/

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 correctly includes both a 'what' and a 'Use when' clause and names the specific product, but its action language is generic and it omits the concrete blockchain capabilities and natural user trigger phrases that would make it truly distinctive.

Suggestions

Replace generic verbs with concrete Tatum capabilities, e.g. 'Generate blockchain wallets, send and broadcast transactions, deploy and mint NFTs and tokens, manage ledger and virtual accounts.'

Expand the trigger clause with natural user phrases: 'Use when the user wants to interact with Tatum blockchain data — wallets, transactions, NFTs, tokens, or ledger accounts.'

Mention the Web3/blockchain framing in the description so it triggers on blockchain-related requests, not just the literal word 'Tatum'.

DimensionReasoningScore

Specificity

It names the domain ('Tatum integration') but the actions ('Manage data, records, and automate workflows') are generic verbs on generic nouns, with none of the concrete blockchain capabilities (wallet generation, NFT mint, send transaction) stated.

2 / 5

Completeness

Both 'what' ('Tatum integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Tatum data') are present, though the 'when' trigger is generic and could be more specific.

4 / 5

Trigger Term Quality

Only 'Tatum' and the generic 'data' appear as keywords; the natural phrases a user would say ('blockchain wallet', 'mint NFT', 'send transaction', 'ledger') are absent.

2 / 5

Distinctiveness Conflict Risk

The named product 'Tatum' anchors a fairly distinct niche with minimal conflict risk, though the generic 'manage data, records' phrasing slightly dilutes distinctiveness.

4 / 5

Total

12

/

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.