qrcoin

Participate in QR Coin auctions on Base - bid to display URLs on QR codes

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 ./src/skills/bundled/qrcoin/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 and distinctive niche (QR Coin auctions on Base), which minimizes conflict risk. However, it lacks an explicit 'Use when...' clause and could benefit from listing more concrete actions and natural trigger terms to help Claude reliably select this skill.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about QR Coin, bidding on QR code auctions, or displaying URLs on QR codes on the Base blockchain.'

List more specific actions such as 'place bids, check auction status, view current QR code displays, withdraw bids' to improve specificity.

Include natural keyword variations users might say, such as 'Base chain', 'QR code NFT', 'auction bid', or 'onchain QR code'.

Dimension	Reasoning	Score
Specificity	Names the domain (QR Coin auctions on Base) and a couple of actions (bid, display URLs on QR codes), but doesn't list multiple concrete actions comprehensively—e.g., no mention of checking auction status, withdrawing bids, or viewing current displays.	2 / 3
Completeness	It describes what the skill does (participate in QR Coin auctions, bid to display URLs) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also somewhat thin, placing this closer to 1.	1 / 3
Trigger Term Quality	Includes some natural keywords like 'QR Coin', 'auctions', 'Base', 'bid', 'QR codes', and 'URLs', but misses common variations a user might say such as 'place a bid', 'blockchain auction', 'QR code NFT', or 'Base chain'.	2 / 3
Distinctiveness Conflict Risk	The description targets a very specific niche—QR Coin auctions on Base blockchain—making it highly unlikely to conflict with other skills. The combination of 'QR Coin', 'auctions', and 'Base' is distinctive.	3 / 3
	Total	8 / 12 Passed

Implementation

72%

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

This is a concise, well-structured skill that clearly communicates the QR Coin auction concept and available commands. Its main weakness is the gap between listing commands and providing truly actionable guidance—there's no underlying implementation shown, and the bidding workflow lacks validation checkpoints (e.g., confirming approval succeeded before bidding, verifying transaction confirmation).

Suggestions

Add a step-by-step bidding workflow with explicit validation: check balance → approve USDC → verify approval → place bid → confirm transaction hash

Include executable code or script references showing how the /qr commands interact with the contract (e.g., ethers.js snippets or a reference to the CLI tool being used)

Dimension	Reasoning	Score
Conciseness	Very lean and efficient. No unnecessary explanations of blockchain concepts, USDC, or how auctions work in general. Every line provides specific, useful information.	3 / 3
Actionability	Commands are clearly listed with syntax, but there's no executable code showing how these commands are implemented—no contract ABI snippets, no actual transaction code, no script to run. The '/qr' commands imply a CLI tool but don't show how it's built or invoked beyond the command syntax.	2 / 3
Workflow Clarity	The 'How It Works' section provides a reasonable overview of the auction flow, and commands are categorized. However, there's no explicit workflow for the bidding process (e.g., check status → approve USDC → place bid → verify), and no validation steps for confirming transactions succeeded or handling failures.	2 / 3
Progressive Disclosure	For a simple, focused skill under 50 lines, the content is well-organized with clear sections (Contracts, How It Works, Commands, Examples, Setup). No need for external references given the scope.	3 / 3
	Total	10 / 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.