manage-tcg-collection
À propos
Cette compétence aide les développeurs à créer des outils pour organiser, suivre et évaluer les collections de jeux de cartes à collectionner pour Pokémon, Magic : l'Assemblée et d'autres jeux populaires. Elle offre des fonctionnalités de gestion d'inventaire, de conseils de stockage, d'évaluation basée sur la note et d'analyses. Utilisez-la pour cataloguer des collections, déterminer la valeur à des fins d'assurance ou de vente, et identifier les cartes qui méritent une évaluation professionnelle.
Installation rapide
Claude Code
Recommandénpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/manage-tcg-collectionCopiez et collez cette commande dans Claude Code pour installer cette compétence
Documentation
Manage TCG Collection
Organize, inventory, and value a trading card game collection with structured tracking, proper storage, and data-driven valuation.
When to Use
- Starting a new collection and setting up inventory tracking
- Cataloging an existing collection that has grown beyond casual knowledge
- Valuing a collection for insurance, sale, or estate purposes
- Managing want-lists and trade binders for acquiring specific cards
- Deciding which cards to submit for professional grading based on value potential
Inputs
- Required: Card game(s) in the collection (Pokemon, MTG, FaB, Kayou, etc.)
- Required: Collection scope (entire collection, specific sets, or specific cards)
- Optional: Current inventory system (spreadsheet, app, physical binder organization)
- Optional: Collection goal (complete sets, competitive play, investment, nostalgia)
- Optional: Budget for storage and grading supplies
Procedure
Step 1: Establish the Inventory System
Set up a tracking system that matches the collection's size.
- Choose an inventory method based on collection size:
Collection Size Guide:
+-----------+-------+-------------------------------------------+
| Size | Cards | Recommended System |
+-----------+-------+-------------------------------------------+
| Small | <200 | Spreadsheet (Google Sheets, Excel) |
| Medium | 200- | Dedicated app (TCGPlayer, Moxfield, |
| | 2000 | PokeCollector, Collectr) |
| Large | 2000+ | Database + app combo with barcode scanning |
+-----------+-------+-------------------------------------------+
- Define the data fields to track per card:
- Identity: Set, card number, name, variant (holo, reverse, full art)
- Condition: Raw grade estimate (NM, LP, MP, HP, DMG) or numeric grade
- Quantity: Copies owned
- Location: Where the card is stored (binder page, box label, graded slab)
- Acquisition: Date, price paid, source (pack, purchase, trade)
- Value: Current market value at condition, last updated date
- Set up the chosen system with these fields
- Establish an update cadence (weekly for active collectors, monthly for stable collections)
Got: A functional inventory system with defined fields, ready for data entry. The system matches the collection's scale — not over-engineered for a small collection, not under-powered for a large one.
If fail: If the ideal app is not available for your game/platform, use a spreadsheet. Format matters less than consistency. A spreadsheet updated regularly beats a sophisticated app abandoned after a week.
Step 2: Catalog the Collection
Enter existing cards into the system.
- Sort cards physically before entering digitally:
- By set (all cards from one set together)
- Within set, by card number (ascending)
- Variants grouped with their base card
- Enter cards into the system:
- Use bulk entry where available (barcode scanning, set checklists)
- Record condition honestly — over-grading own cards causes valuation errors
- Note any cards with special provenance (signed, first edition, tournament prizes)
- For large collections, work in sessions:
- Process one set or one storage box per session
- Mark progress clearly (which boxes/binders are done)
- Verify a random sample from each session for accuracy
- Cross-reference set checklists to identify completion percentages
Got: Every card in the collection entered with accurate condition and location data. Completion percentages known for each set being collected.
If fail: If the collection is too large for manual entry, prioritize: enter all rare/valuable cards first, then bulk-enter commons by set with estimated quantities. An 80% accurate inventory beats no inventory.
Step 3: Organize Physical Storage
Store cards appropriately for their value and use.
- Apply the storage tier system:
Storage Tiers:
+----------+---------------+----------------------------------------------+
| Tier | Card Value | Storage Method |
+----------+---------------+----------------------------------------------+
| Premium | >$50 | Top-loader + team bag, or penny sleeve in |
| | | magnetic case. Stored upright in a box. |
| Standard | $5-$50 | Penny sleeve + top-loader or binder with |
| | | side-loading pages. |
| Bulk | <$5 | Row box (BCW 800-count or similar), sorted |
| | | by set. No individual sleeves needed. |
| Graded | Any (slabbed) | Upright in graded card box. Never stack heavy.|
+----------+---------------+----------------------------------------------+
- Environmental controls:
- Store in a cool, dry, dark location (not attic, not basement)
- Avoid direct sunlight, humidity, and temperature swings
- Use silica gel packets in storage boxes for moisture control
- Label everything:
- Each box labeled with contents (set name, card range, date stored)
- Each binder page corresponds to inventory location codes
- Graded cards labeled with inventory ID matching digital system
- Update the inventory system with storage locations
Got: Every card stored appropriately for its value with location data in the inventory. Premium cards are protected, bulk cards are organized and accessible.
If fail: If premium storage supplies are not available immediately, penny sleeves + top-loaders are the minimum for any card worth >$10. Upgrade storage as supplies become available; the priority is getting valuable cards into some form of protection.
Step 4: Value the Collection
Calculate current market values.
- Choose a pricing source:
- TCGPlayer Market Price: Most common for US market (MTG, Pokemon)
- CardMarket: Standard for European market
- eBay Sold Listings: Best for rare/unique items without standard pricing
- PSA/BGS Price Guide: For graded cards specifically
- Update values for all Standard and Premium tier cards
- For bulk cards, use per-set bulk pricing rather than individual lookups
- Calculate collection summary:
Collection Value Summary:
+------------------+--------+--------+
| Category | Count | Value |
+------------------+--------+--------+
| Graded cards | | $ |
| Premium ungraded | | $ |
| Standard cards | | $ |
| Bulk cards | | $ |
+------------------+--------+--------+
| TOTAL | | $ |
+------------------+--------+--------+
- Identify grading candidates: cards where the grade-premium exceeds grading costs
- Rule of thumb: grade if (expected graded value - raw value) > 2x grading cost
Got: A current valuation of the collection with per-card values for significant cards and aggregate values for bulk. Grading candidates identified.
If fail: If pricing data is stale or unavailable, note the pricing date and source. For rare cards, check multiple sources and use the median. Never rely on a single outlier sale.
Step 5: Maintain and Optimize
Establish ongoing collection management routines.
- Regular updates (match cadence from Step 1):
- Enter new acquisitions immediately
- Update values for Premium tier quarterly, Standard tier semi-annually
- Re-assess storage tier as values change
- Want-list management:
- Maintain a list of desired cards with maximum prices
- Cross-reference want-list against trade binder inventory
- Set price alerts where supported by the inventory app
- Collection analytics:
- Track total value over time (monthly snapshots)
- Monitor set completion percentages
- Identify concentration risk (too much value in one card/set)
- Periodic audit (annually):
- Physical count vs. inventory count for a random sample
- Verify storage conditions (check for humidity, pest damage)
- Review and update grading candidates based on current values
Got: A living collection management system that stays current and supports informed decisions about buying, selling, grading, and trading.
If fail: If maintenance lapses, prioritize: update Premium tier values first, then catch up on new acquisitions. Knowing what your most valuable cards are worth today is the priority.
Validation Checklist
- Inventory system established with appropriate data fields
- All cards cataloged with condition and location data
- Physical storage matches card value tiers
- Environmental controls in place (cool, dry, dark)
- Collection valued with current market prices and dates
- Grading candidates identified with cost/benefit analysis
- Maintenance cadence established and followed
- Want-list maintained for acquisition targets
Pitfalls
- Over-grading own cards: Collectors rate their own cards 1-2 grades higher than reality. Be honest or use
grade-tcg-cardfor structured assessment - Ignoring bulk: Bulk cards accumulate value collectively. A box of 800 commons at $0.10 each is $80 — worth tracking
- Poor storage environment: Humidity and temperature swings damage cards faster than handling. Environment matters more than sleeves
- Stale valuations: Card markets move. A valuation from 6 months ago may be wildly inaccurate, especially around set releases or ban announcements
- No backup: Digital inventory without backup is fragile. Export to CSV monthly. Photograph premium cards for insurance
Related Skills
grade-tcg-card— Structured card grading for accurate condition assessmentbuild-tcg-deck— Deck construction using the collection inventory
Dépôt GitHub
Compétences associées
executing-plans
DesignUtilisez la compétence executing-plans lorsque vous disposez d'un plan de mise en œuvre complet à exécuter par lots contrôlés avec des points de contrôle de revue. Elle charge et examine le plan de manière critique, puis exécute les tâches par petits lots (3 tâches par défaut) tout en rapportant la progression entre chaque lot pour une revue par l'architecte. Cela garantit une mise en œuvre systématique avec des points de contrôle de qualité intégrés.
requesting-code-review
DesignCette compétence délègue un sous-agent réviseur de code pour analyser les modifications apportées au code par rapport aux exigences avant de poursuivre. Elle doit être utilisée après avoir terminé des tâches, implémenté des fonctionnalités majeures, ou avant une fusion vers la branche principale. La revue aide à détecter précocement les problèmes en comparant l'implémentation actuelle avec le plan initial.
connect-mcp-server
DesignCette compétence fournit un guide complet permettant aux développeurs de connecter des serveurs MCP à Claude Code via les transports HTTP, stdio ou SSE. Elle couvre l'installation, la configuration, l'authentification et la sécurité pour intégrer des services externes tels que GitHub, Notion et des API personnalisées. Utilisez-la lors de la configuration d'intégrations MCP, de la configuration d'outils externes ou du travail avec le Protocole de Contexte de Modèle de Claude.
web-cli-teleport
DesignCette compétence aide les développeurs à choisir entre les interfaces Web et CLI de Claude Code en fonction de l'analyse des tâches, puis permet une téléportation transparente des sessions entre ces environnements. Elle optimise le flux de travail en gérant l'état et le contexte de la session lors du passage entre le web, la CLI ou le mobile. Utilisez-la pour des projets complexes nécessitant différents outils à diverses étapes.
