Participate in QR Coin auctions on Base - bid to display URLs on QR codes
67
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/qrcoin/SKILL.mdQuality
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 specific niche (QR Coin auctions on Base) which provides good distinctiveness, but lacks explicit trigger guidance for when Claude should select this skill. The capabilities mentioned are somewhat specific but could be more comprehensive, and the trigger terms could include more natural variations users might use.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions QR Coin, Base auctions, bidding on QR codes, or wants to display URLs via blockchain auctions'
Expand trigger terms to include variations like 'crypto auction', 'Base network', 'blockchain bidding', or 'QR code NFT'
List additional specific actions if available, such as 'check auction status', 'view bid history', or 'manage winning bids'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (QR Coin auctions on Base) and mentions specific actions (bid, display URLs on QR codes), but lacks comprehensive detail about what other actions are possible (e.g., checking auction status, withdrawing bids, viewing history). | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no trigger guidance at all. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'QR Coin', 'auctions', 'Base', 'bid', and 'QR codes', but misses common variations users might say such as 'blockchain auction', 'NFT', 'crypto bidding', or 'Base network'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche - QR Coin auctions on Base is a distinct product/platform combination that is unlikely to conflict with other skills. The combination of 'QR Coin', 'Base', and 'auctions' creates clear differentiation. | 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 skill is concise and well-structured for its scope, with clear contract addresses and command syntax. However, it lacks executable code showing actual contract interactions and misses validation steps for the approve-then-bid workflow, which involves real money transactions.
Suggestions
Add explicit workflow sequence: 1) Check USDC balance, 2) Approve USDC, 3) Verify approval, 4) Submit bid, 5) Confirm bid registered
Include executable code examples showing how the slash commands interact with the contracts (e.g., ethers.js or similar), or clarify that these are bot commands with the bot handling contract calls
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of blockchain concepts, USDC, or how auctions work. Every line provides actionable information Claude needs. | 3 / 3 |
Actionability | Commands are clearly listed with syntax, but they appear to be slash commands without showing the underlying implementation. No executable code showing how to interact with the contracts directly (e.g., web3/ethers.js calls). | 2 / 3 |
Workflow Clarity | The 'How It Works' section explains the auction flow, but there's no validation checkpoint for checking if USDC approval succeeded before bidding, or verifying bid submission. The workflow for a complete bid (approve -> bid) lacks explicit sequencing. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose 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%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 | |
2a8c94e
Table of Contents
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.