transak

Transak fiat-to-crypto on-ramp for Web3. Buy and sell crypto with 100+ payment methods across 170+ countries.

Quality

56%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/transak/SKILL.md

Quality

Discovery

32%

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 core domain (Transak fiat-to-crypto service) and basic capabilities but lacks explicit trigger guidance for when Claude should use this skill. The scope indicators (100+ payment methods, 170+ countries) are marketing-style claims rather than actionable selection criteria. Without a 'Use when...' clause, Claude may struggle to reliably select this skill from a large skill library.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user wants to buy cryptocurrency with fiat currency, needs to on-ramp funds to Web3, or mentions Transak'

Include more specific trigger terms users would naturally say: 'purchase crypto', 'convert dollars to ETH', 'credit card to crypto', 'on-ramp'

List concrete actions the skill performs: 'initiate fiat purchases', 'check supported currencies', 'verify payment method availability', 'track transaction status'

Dimension	Reasoning	Score
Specificity	Names the domain (fiat-to-crypto on-ramp) and mentions actions (buy and sell crypto), but lacks specific concrete actions like 'initiate purchases', 'check transaction status', or 'configure payment methods'.	2 / 3
Completeness	Describes what (fiat-to-crypto on-ramp, buy/sell crypto) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some natural keywords like 'buy', 'sell', 'crypto', 'fiat', and 'Web3', but missing common variations users might say like 'purchase cryptocurrency', 'convert USD to crypto', 'on-ramp', or specific crypto names.	2 / 3
Distinctiveness Conflict Risk	The Transak brand name and 'fiat-to-crypto on-ramp' provide some distinctiveness, but 'buy and sell crypto' is generic enough to potentially conflict with other crypto-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

79%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted API reference skill with excellent actionability and conciseness. The executable bash examples and comprehensive reference tables make it immediately useful. However, it lacks an explicit end-to-end workflow showing how the pieces fit together (quote → widget → order tracking → webhook verification) with validation checkpoints between steps.

Suggestions

Add a 'Complete Integration Workflow' section showing the full flow: get quote → generate widget → poll order status → handle webhook, with explicit validation steps between each phase

Include a validation checkpoint after webhook verification before fulfilling orders (e.g., 'Only proceed when signature verified AND order status is COMPLETED')

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, using tables for reference data and providing executable code without unnecessary explanations. No concepts are over-explained; it assumes Claude understands APIs, webhooks, and bash scripting.	3 / 3
Actionability	All code examples are fully executable bash commands with proper variable setup. The curl commands, jq parsing, and widget URL construction are copy-paste ready with clear parameter substitution patterns.	3 / 3
Workflow Clarity	While individual API calls are clear, there's no explicit workflow for a complete integration (e.g., get quote → generate widget → poll order status → verify webhook). The safety rules mention verification but don't integrate into a step-by-step process with validation checkpoints.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but everything is in one file. Reference tables (networks, payment methods, status codes) could be split into separate files. External links are provided but internal progressive disclosure is minimal.	2 / 3
	Total	10 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: Demerzels-lab/elsamultiskillagent
Commit: 45f9fac

Reviewed: 27 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.