meteora-dbc

Launch tokens on Meteora dynamic bonding curves

Quality

35%

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 is highly distinctive due to its niche focus on Meteora dynamic bonding curves, but it is too terse. It lacks a 'Use when...' clause, provides only a single action, and misses common trigger term variations that users might employ when requesting this functionality.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user wants to launch or deploy a token on Meteora, create a dynamic bonding curve, or set up a token sale on Solana via Meteora.'

List additional concrete actions beyond 'launch tokens', such as 'configure bonding curve parameters, set initial liquidity, deploy token contracts on Meteora.'

Include natural keyword variations users might say, such as 'token launch', 'DBC', 'Solana token', 'Meteora pool', or 'bonding curve deployment'.

Dimension	Reasoning	Score
Specificity	Names a specific domain (Meteora dynamic bonding curves) and one action (launch tokens), but does not list multiple concrete actions or elaborate on what launching entails.	2 / 3
Completeness	Describes what it does (launch tokens on Meteora dynamic bonding curves) but completely lacks any 'Use when...' clause or explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also quite thin, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'tokens', 'Meteora', and 'bonding curves' that a knowledgeable user might say, but misses common variations such as 'token launch', 'DBC', 'Solana', 'liquidity pool', or 'create token'.	2 / 3
Distinctiveness Conflict Risk	The description targets a very specific niche—Meteora dynamic bonding curves—which is unlikely to conflict with other skills. The combination of 'Meteora' and 'dynamic bonding curves' is highly distinctive.	3 / 3
	Total	8 / 12 Passed

Implementation

29%

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

This skill is extremely minimal—essentially just a command reference table with no actionable detail. While it's concise, it sacrifices all actionability, workflow guidance, and structural organization. For a skill involving financial operations (token launches, buying/selling on bonding curves), the complete absence of parameter documentation, examples, validation steps, and error handling is a critical gap.

Suggestions

Add concrete examples for key commands, especially `/dbc launch` with all required and optional parameters shown with realistic values

Document a typical workflow sequence (e.g., launch → verify status → buy → check migration) with validation checkpoints after each step

Explain the [options] for launch (anti-sniper fee config, market cap settings, migration parameters) with specific flag names and acceptable values

Add error handling guidance and safety warnings for financial operations (e.g., confirming transactions, checking pool status before selling)

Dimension	Reasoning	Score
Conciseness	Very lean and efficient. The one-line description adds context about anti-sniper fees and DAMM migration that Claude wouldn't inherently know. No unnecessary explanations of what bonding curves or Meteora are.	3 / 3
Actionability	Only lists command signatures with no executable code, no examples of actual usage, no parameter details, no option flags explained, and no concrete workflows. A user or Claude cannot act on '/dbc launch <name> <symbol> <desc> [options]' without knowing what [options] are or how to actually invoke these.	1 / 3
Workflow Clarity	No workflow sequencing at all. Launching a token on a bonding curve is a multi-step process (launch → verify → buy/sell → migrate) involving financial operations, yet there are no steps, no validation checkpoints, and no error handling guidance.	1 / 3
Progressive Disclosure	The content is a flat list of commands with no structure beyond a single 'Commands' section. There are no references to detailed documentation, no sections for quick start vs advanced usage, and no links to parameter references or examples.	1 / 3
	Total	6 / 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: e71a5f6

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