CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qrcoin

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

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/qrcoin/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

A clean, concise, actionable command-oriented skill, but it lacks validation/verification checkpoints for irreversible financial operations, which caps workflow clarity. Adding explicit pre/post-transaction checks would meaningfully improve safety.

Suggestions

Add a validation step before bidding: check auction status/end time and confirm USDC allowance is sufficient, then verify the bid transaction landed on-chain.

Sequence the bidding workflow explicitly (status → approve → bid → confirm) rather than presenting commands as ungrouped tables.

Clarify how approve and bid relate (e.g. approve once up to a cap, then bid/contribute draws from it) and note failure modes like insufficient balance or auction already ended.

DimensionReasoningScore

Conciseness

The body is lean — a contracts table, terse facts, command tables, and setup — with no padding or explanations of concepts Claude already knows; the only minor redundancy is the Examples section restating commands already shown in Commands.

4 / 5

Actionability

Concrete slash commands with arguments ("/qr bid <url> <name>", "/qr approve <amount>"), real contract addresses, and approximate costs give mostly executable guidance; minor gaps include no error-handling notes and no explanation of how approve interacts with bid.

4 / 5

Workflow Clarity

This is a destructive/financial skill (spending real USDC in irreversible on-chain bids) yet the body lists no validation checkpoints (e.g. verify allowance, confirm bid landed, check auction end time before bidding), so workflow clarity is capped at 3 per the destructive-operation rule.

3 / 5

Progressive Disclosure

The skill is ~51 lines, single-purpose, and self-contained with no bundle files; sections (Contracts, How It Works, Commands, Examples, Setup) are well-organized and there is nothing that needs offloading to references.

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 specific and clearly niche but omits any "Use when..." trigger guidance, leaving Claude without an explicit activation signal. Adding a use-when clause with natural trigger terms would raise completeness and trigger quality.

Suggestions

Append a "Use when..." clause, e.g. "Use when the user wants to bid in QR Coin auctions, display a URL on a QR code, or check auction status on Base."

Broaden trigger terms with synonyms users might say ("win a QR ad", "advertise on a QR code", "QR coin bid").

Mention the supporting actions (approve USDC, contribute to a bid) so the capability set reads as comprehensive.

DimensionReasoningScore

Specificity

Names the domain ("QR Coin auctions on Base") and one concrete action ("bid to display URLs on QR codes"), but coverage is not comprehensive — contributing, approving, and reserves are absent from the description.

3 / 5

Completeness

Provides a clear "what" (participate in QR Coin auctions / bid to display URLs) but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ("auctions", "bid", "QR codes", "URLs", "Base") but misses common variations or synonyms a user might say (e.g. "win", "advertise", "QR code ad").

3 / 5

Distinctiveness Conflict Risk

"QR Coin auctions on Base — bid to display URLs on QR codes" is a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.

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

Reviewed

Table of Contents

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.