MCP HubMCP Hub
Volver a habilidades

manage-tcg-collection

pjt222
Actualizado 2 days ago
4 vistas
17
2
17
Ver en GitHub
Diseñodesigndata

Acerca de

Esta habilidad de Claude ayuda a los desarrolladores a crear herramientas para gestionar colecciones de TCG, proporcionando seguimiento de inventario, orientación de almacenamiento y valoración basada en grados para las cartas. Es útil para catalogar colecciones, evaluar el valor con fines de seguros o venta, y decidir sobre envíos a servicios de calificación profesional. La habilidad soporta juegos populares como Pokémon, MTG, Flesh and Blood y Kayou.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add pjt222/agent-almanac -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativo
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/manage-tcg-collection

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

Manage TCG Collection

Organize, inventory, value TCG collection → structured tracking + storage + data-driven valuation.

Use When

  • New collection → set up tracking
  • Existing collection grew past casual knowledge
  • Value for insurance/sale/estate
  • Manage want-lists + trade binders
  • Decide grading candidates by value potential

In

  • Required: Game(s) (Pokemon, MTG, FaB, Kayou)
  • Required: Scope (entire / sets / specific cards)
  • Optional: Current system (sheet, app, binder)
  • Optional: Goal (sets, play, invest, nostalgia)
  • Optional: Budget for supplies/grading

Do

Step 1: Inventory System

Tracking system matched to size.

  1. Method by 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 |
+-----------+-------+-------------------------------------------+
  1. Fields per card:
    • Identity: Set, num, name, variant (holo, reverse, full art)
    • Condition: Raw grade (NM, LP, MP, HP, DMG) or numeric
    • Qty: Copies owned
    • Location: Binder page, box label, slab
    • Acquisition: Date, price paid, source
    • Value: Market value at condition, last update
  2. Set up system w/ fields
  3. Cadence (weekly active, monthly stable)

→ Working system + fields, ready for entry. Matches scale.

If err: ideal app missing → sheet. Consistency > format. Sheet updated > app abandoned.

Step 2: Catalog

Enter cards into system.

  1. Sort physically first:
    • By set
    • Within set, by num ascending
    • Variants w/ base
  2. Enter:
    • Bulk where possible (barcode, set checklists)
    • Honest condition — over-grade → valuation err
    • Note provenance (signed, 1st ed, prizes)
  3. Large → sessions:
    • One set/box per session
    • Mark progress
    • Random sample verify
  4. Cross-ref set checklists → completion %

→ All cards entered w/ condition + location. Completion % known.

If err: too large → priority: rares first, bulk-enter commons w/ est qty. 80% accurate > none.

Step 3: Physical Storage

Store by value + use.

  1. 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.|
+----------+---------------+----------------------------------------------+
  1. Env controls:
    • Cool, dry, dark (not attic/basement)
    • No direct sun, humidity, temp swings
    • Silica gel in boxes
  2. Label all:
    • Box: contents (set, range, date)
    • Binder pages → location codes
    • Graded: ID matches digital
  3. Update locations in system

→ All cards stored by tier w/ location in inventory. Premium protected, bulk accessible.

If err: no premium supplies → penny sleeve + top-loader min for >$10. Upgrade as available.

Step 4: Value Collection

Current market values.

  1. Pricing source:
    • TCGPlayer Market Price: US (MTG, Pokemon)
    • CardMarket: EU
    • eBay Sold Listings: Rare/unique
    • PSA/BGS Price Guide: Graded
  2. Update Standard + Premium values
  3. Bulk → per-set bulk pricing
  4. Summary:
Collection Value Summary:
+------------------+--------+--------+
| Category         | Count  | Value  |
+------------------+--------+--------+
| Graded cards     |        | $      |
| Premium ungraded |        | $      |
| Standard cards   |        | $      |
| Bulk cards       |        | $      |
+------------------+--------+--------+
| TOTAL            |        | $      |
+------------------+--------+--------+
  1. Grading candidates: grade-premium > grading cost
    • Rule: grade if (graded value - raw) > 2x grading cost

→ Current valuation, per-card for significant + aggregate bulk. Grading candidates flagged.

If err: stale pricing → note date + source. Rare → multi-source median. Never trust outlier.

Step 5: Maintain + Optimize

Ongoing routines.

  1. Updates (Step 1 cadence):
    • New acquisitions immediately
    • Premium quarterly, Standard semi-annually
    • Re-tier as values shift
  2. Want-list:
    • Desired cards + max price
    • Cross-ref vs. trade binder
    • Price alerts if supported
  3. Analytics:
    • Monthly value snapshots
    • Set completion %
    • Concentration risk (one card/set heavy)
  4. Annual audit:
    • Physical vs. inventory random sample
    • Storage check (humidity, pests)
    • Re-eval grading candidates

→ Living system, current, supports buy/sell/grade/trade decisions.

If err: lapse → Premium values first, then new acquisitions. Know top values today.

Check

  • System established w/ fields
  • All cards cataloged + condition + location
  • Storage matches tiers
  • Env controls (cool, dry, dark)
  • Valued w/ current prices + dates
  • Grading candidates flagged w/ cost/benefit
  • Maintenance cadence followed
  • Want-list maintained

Traps

  • Over-grade own cards: Collectors rate own +1-2 grades. Honest or use grade-tcg-card
  • Ignore bulk: 800 commons @ $0.10 = $80. Track
  • Bad env: Humidity + temp swings damage > handling. Env > sleeves
  • Stale values: 6 months old → wildly off, esp. set release/ban
  • No backup: Export CSV monthly. Photograph premium for insurance

  • grade-tcg-card — structured grading
  • build-tcg-deck — deck from inventory

Repositorio GitHub

pjt222/agent-almanac
Ruta: i18n/caveman-ultra/skills/manage-tcg-collection
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Habilidades relacionadas

executing-plans

Diseño

Utilice la habilidad executing-plans cuando tenga un plan de implementación completo para ejecutar en lotes controlados con puntos de revisión. Esta habilidad carga y revisa críticamente el plan, luego ejecuta tareas en pequeños lotes (por defecto 3 tareas) mientras reporta el progreso entre cada lote para la revisión del arquitecto. Esto asegura una implementación sistemática con puntos de control de calidad integrados.

Ver habilidad

requesting-code-review

Diseño

Esta habilidad despacha un subagente revisor de código para analizar los cambios en el código frente a los requisitos antes de proceder. Debe usarse después de completar tareas, implementar funciones principales o antes de fusionar con la rama principal. La revisión ayuda a detectar problemas de forma temprana al comparar la implementación actual con el plan original.

Ver habilidad

connect-mcp-server

Diseño

Esta habilidad proporciona una guía integral para que los desarrolladores conecten servidores MCP a Claude Code mediante transportes HTTP, stdio o SSE. Cubre la instalación, configuración, autenticación y seguridad para integrar servicios externos como GitHub, Notion y APIs personalizadas. Úsala al configurar integraciones MCP, al configurar herramientas externas o al trabajar con el Protocolo de Contexto del Modelo de Claude.

Ver habilidad

web-cli-teleport

Diseño

Esta habilidad ayuda a los desarrolladores a elegir entre las interfaces web y CLI de Claude Code mediante el análisis de tareas, y luego permite la teletransportación fluida de sesiones entre estos entornos. Optimiza el flujo de trabajo gestionando el estado y el contexto de la sesión al cambiar entre web, CLI o móvil. Úsala para proyectos complejos que requieren diferentes herramientas en varias etapas.

Ver habilidad