bags

Bags.fm - Complete Solana token launchpad with creator monetization

Quality

36%

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/bags/SKILL.md

Quality

Discovery

22%

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 essentially a tagline rather than a functional skill description. It names the platform and broad domain but fails to list concrete actions, provide trigger terms users would naturally use, or include any 'Use when...' guidance. It would be very difficult for Claude to reliably select this skill from a large pool.

Suggestions

Add a 'Use when...' clause with explicit trigger terms, e.g., 'Use when the user asks about launching tokens on Solana, Bags.fm, creating a token launchpad, or setting up creator monetization.'

List specific concrete actions the skill performs, such as 'Deploy SPL tokens, configure bonding curves, set creator fees, manage token launches, and track creator earnings.'

Include natural keyword variations users might say, such as 'mint token', 'token sale', 'Solana memecoin', 'launch token', 'bags.fm', and 'creator rewards'.

Dimension	Reasoning	Score
Specificity	The description names a domain ('Solana token launchpad') and a vague concept ('creator monetization') but does not list any concrete actions like 'deploy tokens', 'set pricing', 'manage liquidity', etc.	1 / 3
Completeness	The description provides a very brief 'what' (Solana token launchpad with creator monetization) but completely lacks any 'when' clause or explicit trigger guidance, which per the rubric caps completeness at 2 at best—and the 'what' itself is too vague to merit even a 2.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'Solana', 'token', 'launchpad', and 'Bags.fm' that a user might mention, but misses common variations and related terms such as 'mint', 'deploy token', 'bonding curve', 'SPL token', or 'token launch'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Bags.fm' and 'Solana token launchpad' provides some distinctiveness, but without specific actions or triggers it could overlap with other Solana or crypto-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

50%

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

This skill provides a comprehensive command reference for the Bags.fm platform with good structural organization and clear syntax examples. However, it lacks clarity on the execution context (what tool/interface these commands run in), has no validation or error-handling guidance for financial operations, and includes some redundant content between the command listings, examples, and features sections.

Suggestions

Clarify the execution context: are these CLI commands, MCP tool calls, Discord bot commands, or API endpoints? Show how they're actually invoked.

Add validation checkpoints for financial operations (swaps, launches, fee claiming) - e.g., check balance before swap, confirm transaction after execution, verify fee-config bps sum.

Remove the redundant 'Features' section at the end since all features are already demonstrated by the command listings above.

Show at least one example response/output format so Claude knows what to expect and can parse results.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with its command reference format, but the 'Features' section at the end is largely redundant with information already conveyed by the commands themselves. The introductory sentence explaining what Bags.fm is adds minor value but the creator fee explanation is repeated. The Examples section partially duplicates the command listings above.	2 / 3
Actionability	The commands are clearly listed with syntax, and examples are provided, but these are slash-command references rather than executable code. There's no indication of how these commands are actually invoked (CLI tool? Discord bot? MCP tool?), what the response format looks like, or how to handle errors. The configuration section helps but lacks context on where/how to use the API key.	2 / 3
Workflow Clarity	The Examples section shows some multi-step workflows (launch, check fees, claim fees), but there are no validation checkpoints. For operations involving real money (swaps, launches, fee claiming), there's no guidance on confirming transactions, checking balances first, or handling failures. The fee-config command requires bps summing to 10000 but no validation step is mentioned.	2 / 3
Progressive Disclosure	The content is well-organized into logical sections with clear headers, making it easy to scan. However, it's a fairly long single file that could benefit from splitting detailed API reference or examples into separate files. The API Reference section hints at external resources (dev.bags.fm) but doesn't reference any companion documentation files.	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: 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.