CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meteora-dbc

Launch tokens on Meteora dynamic bonding curves

56

Quality

71%

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

Quality

Content

73%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 exceptionally concise and well-structured as a command reference, but it provides no sequenced workflow or validation checkpoints for destructive on-chain operations like token launch and DAMM migration, and command options remain unspecified.

Suggestions

Add a sequenced launch workflow with validation checkpoints (e.g., 1. configure params, 2. launch, 3. verify pool with /dbc status, 4. monitor migration) since these operations are irreversible.

Expand the [options] for launch and document buy/sell/quote argument details (or point to a reference file) to make commands fully copy-paste ready.

Include at least one worked example with realistic values for the launch and buy commands to cover the common case.

DimensionReasoningScore

Conciseness

The body is lean: a one-line intro that adds new detail (anti-sniper fees, market caps, DAMM migration) plus a compact command table, with no padding or explanation of concepts Claude already knows, matching the anchor for lean and efficient content where every token earns its place.

5 / 5

Actionability

Concrete executable command syntax is provided (e.g., "/dbc launch <name> <symbol> <desc> [options]"), but the unspecified [options], lack of worked examples with real values, and missing detail on buy/sell amounts leave minor gaps, fitting the anchor for mostly executable guidance with minor gaps rather than fully copy-paste ready coverage.

4 / 5

Workflow Clarity

Only a flat command menu is presented with no sequenced workflow for the launch-to-migration lifecycle and no validation/verification checkpoints for irreversible on-chain operations; because the skill performs destructive operations with no validation, workflow clarity cannot exceed 3, and the absence of any sequence places it at the rough/gappy anchor rather than 3.

2 / 5

Progressive Disclosure

The body is under 50 lines with no external bundle files and is organized into a clear intro plus a Commands section; per the simple-skill exception, well-organized sections with no need for external references score 5.

5 / 5

Total

16

/

20

Passed

Description

57%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 is concise and names a distinct, specific niche with a concrete primary action, but it omits any "Use when..." trigger guidance and lacks keyword synonyms, capping completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause naming natural user triggers (e.g., "Use when launching a token on Meteora, creating a bonding curve, or migrating a pool to DAMM").

Include common synonyms and the command token like "DBC", "Solana token launch", and "bonding curve" to improve trigger-term coverage.

List 1-2 more concrete capabilities (e.g., buy/sell on curve, claim fees) to raise specificity beyond a single action.

DimensionReasoningScore

Specificity

"Launch tokens on Meteora dynamic bonding curves" names a specific domain and one concrete action (launch), matching the anchor that names a domain plus 1-2 concrete actions but is not comprehensive; it is above score 2 because "Launch tokens" is a concrete action rather than generic, but below 4 because only a single action is listed.

3 / 5

Completeness

It clearly states what the skill does ("Launch tokens on Meteora dynamic bonding curves") but provides no "Use when..." clause or equivalent trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3, and it is not a 2 because the "what" is clear and concrete.

3 / 5

Trigger Term Quality

Keywords like "Meteora", "tokens", "bonding curves", and "launch" are relevant natural terms a user might say, but common variations/synonyms ("DBC", "Solana token launch", "bonding curve") are missing, fitting the anchor for some relevant keywords with missing variations.

3 / 5

Distinctiveness Conflict Risk

"Meteora dynamic bonding curves" names a highly specific niche with distinct triggers and minimal conflict risk with other skills, matching the anchor for a clear niche with minimal conflict.

5 / 5

Total

14

/

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.

Validation — 15 / 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

alsk1992/CloddsBot

Path

src/skills/bundled/meteora-dbc/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill