meteora-dbc

Launch tokens on Meteora dynamic bonding curves

Quality

46%

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 ./src/skills/bundled/meteora-dbc/SKILL.md

Quality

Discovery

40%

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 a clear, specific niche (Meteora dynamic bonding curves) which makes it distinctive, but it's too terse to be effective for skill selection. It lacks explicit trigger guidance and only mentions a single action, making it difficult for Claude to know when to select this skill over others in a large skill library.

Suggestions

Add a 'Use when...' clause with trigger terms like 'launch token', 'create token on Meteora', 'bonding curve', 'Solana token launch', or 'DBC'

Expand the capabilities list to include related actions such as 'configure bonding curve parameters', 'set token metadata', or 'deploy to Solana'

Include common user phrasings and variations like 'token creation', 'fair launch', or 'liquidity bootstrapping'

Dimension	Reasoning	Score
Specificity	Names a specific domain (Meteora dynamic bonding curves) and one action (launch tokens), but doesn't list multiple concrete actions or capabilities beyond the single launch operation.	2 / 3
Completeness	Only describes what (launch tokens on Meteora) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant technical terms like 'tokens', 'Meteora', and 'bonding curves' that users familiar with the platform would use, but misses common variations like 'token launch', 'create token', 'DBC', or 'Solana'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche targeting Meteora's dynamic bonding curves specifically - unlikely to conflict with other skills due to the precise platform and mechanism mentioned.	3 / 3
	Total	8 / 12 Passed

Implementation

52%

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

This skill is admirably concise and provides a clean command reference, but sacrifices too much actionability and workflow guidance. For a complex multi-step process like token launches with migration, users need to understand the sequence of operations and what options are available. The command list alone doesn't teach Claude how to actually guide someone through a successful token launch.

Suggestions

Add a brief workflow section showing the typical sequence: launch -> monitor status -> migrate, with validation checkpoints (e.g., 'Check status shows X before migrating')

Expand the launch command with a concrete example showing common options: `/dbc launch "MyToken" "MTK" "A test token" --marketCap 100 --fee 2`

Document what the '[options]' for launch actually are, or reference a separate OPTIONS.md file

Add expected output examples for status and quote commands so Claude knows what success looks like

Dimension	Reasoning	Score
Conciseness	Extremely lean - provides only the essential command reference without explaining what bonding curves are, how Meteora works, or other concepts Claude already knows. Every line serves a purpose.	3 / 3
Actionability	Commands are listed with clear syntax and brief descriptions, but lacks executable examples showing actual usage with real parameters, expected outputs, or common option flags for the launch command.	2 / 3
Workflow Clarity	No workflow guidance for the multi-step token launch process. Missing sequence for launch -> monitor -> migrate flow, no validation checkpoints, and no guidance on when to use which commands in relation to each other.	1 / 3
Progressive Disclosure	Content is appropriately brief for a SKILL.md overview, but the '[options]' placeholder and nested commands like 'migrate <command> [args]' suggest additional documentation should exist but isn't referenced.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

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