CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

card-set-import

Import and verify a card set into the project's card data (cardsets/). Use when the maintainer asks to import a set, build or rebuild card set data, update a set's cards (for example after new promos or art), re-import a set, verify imported cards, or work through a card-set import report. Takes a TCGdex set id ("me06") or a decklist code ("DLR"), or every set.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary operational skill body: lean, domain-specific, fully executable, with a clearly sequenced workflow that includes an explicit re-run loop, validation commands with exit-code semantics, and failure-mode handling for every report kind. The only structural observation is that all reference-grade material lives in the single file rather than being split into bundle files, which is defensible for a workflow where every section is needed on each run.

DimensionReasoningScore

Conciseness

Every line is task-specific and non-derivable: the rules, the report-driven loop ("The report is your only to-do list. Keep no list of your own."), and domain facts Claude cannot know ("TCGdex adds images weeks after release; a re-import picks them up"). Nothing explains concepts Claude already knows and no padding was found, so it cannot be the anchor-4 case of "minor instances of over-explanation".

5 / 5

Actionability

Fully executable throughout: copy-paste commands ("go build -o bin/tcgreplay ./cmd/tcgreplay", "bin/tcgreplay sets import <set>", "bin/tcgreplay sets check <id>", "go test ./internal/cardset/"), a concrete corrections JSON example with real paths, exact image-URL construction ("append `/high.png`"), and a table resolving each of the nine report kinds with exact JSON Pointer fields. This matches the anchor-5 "copy-paste ready, covers the common cases" profile.

5 / 5

Workflow Clarity

Seven clearly numbered steps with an explicit feedback loop ("Repeat steps 2 to 5 until the summary line says `0 open`") and an explicit validation checkpoint ("Both must pass. `sets check` lists any open item and exits 1."), plus error-recovery guidance (undefined paths fail with a message naming them; systemic cosmetic differences escalate to the maintainer). The batch-operation cap does not apply because validation is present, and this exceeds anchor 4 by including the retry loop and failure-mode handling.

5 / 5

Progressive Disclosure

The body is well organized (## Rules, ## Steps 1–7, a kind-resolution table) and no bundle files exist or are strictly required, so nothing is buried or nested. Not 5 because at ~135 lines, reference-grade material (the nine-row kind table, URL-construction rules) is fully inlined with no progressive-disclosure layering, which falls short of the anchor-5 overview-plus-references pattern; not 3 because structure is clear and no content that clearly belongs in a separate file is crammed inline.

4 / 5

Total

19

/

20

Passed

Description

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

A strong description in declarative voice: it states what the skill does, exactly what inputs it takes, and an explicit, well-enumerated "Use when" clause with natural maintainer phrasing and concrete id examples. The only gap is that the core action list (import/verify) undersells the correction-recording judgement work the body is mostly about.

DimensionReasoningScore

Specificity

The what-statement gives two concrete actions ("Import and verify a card set into the project's card data (cardsets/)") with precisely specified inputs ("Takes a TCGdex set id (\"me06\") or a decklist code (\"DLR\"), or every set"), and the when-clause enumerates several more task variants (build/rebuild, update cards, re-import, verify). Not 5 because the core capability list stops at import/verify and omits the skill's central judgement work (recording corrections and acknowledgements); not 3 because inputs and task variants are far more concrete than the anchor-3 example.

4 / 5

Completeness

Explicitly answers both questions: the what ("Import and verify a card set into the project's card data (cardsets/)") and an explicit "Use when" clause with concrete enumerated trigger phrases. Clear anchor-5 match; anchor 4 would require a vaguer or less specific when-clause.

5 / 5

Trigger Term Quality

Natural phrases a maintainer would actually say are comprehensively covered with synonyms: "import a set", "build or rebuild card set data", "update a set's cards", "re-import a set", "verify imported cards", "card-set import report", plus concrete id examples ("me06", "DLR") that function like file extensions. No common variation is obviously missing, so it matches the anchor-5 example rather than anchor 4.

5 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers — TCG card set importing into cardsets/ keyed by "TCGdex set id" and "decklist code" — that no generic skill would plausibly collide with. Minimal conflict risk, matching the anchor-5 example's profile.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nicholasjackson/tcgreplay

Path

skills/card-set-import/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.