ygo-card-self-evolve

Diagnoses and updates card-building skill files based on validation failures and comparison mismatches.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/ZisIsNotZis/ygoskill --skill ygo-card-self-evolve-zisisnotzis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ygo-card-self-evolve
Source: https://github.com/ZisIsNotZis/ygoskill/tree/main/ygo/card-self-evolve
Command: npx skills add https://github.com/ZisIsNotZis/ygoskill --skill ygo-card-self-evolve-zisisnotzis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When Yu-Gi-Oh! card builds fail validation checks or diverge from reference cards, this Skill provides a structured loop to trace the root cause and update the responsible skill files so the same errors do not recur. ## Core Features & Use Cases - SMART Self-Evaluation Loop: A six-step non-negotiable cycle covering card rebuild, mdcheck/catalogcheck/combocheck verification, reference comparison, root-cause analysis, skill file updates, and re-validation. - Trigger-Based Diagnosis: Maps specific failure signals (validation score below threshold, comparison match rate under 50 percent, missing catalog entries) to the exact skill file that needs correction. - Use Case: After building a card that fails combocheck.py, run this loop to determine whether the build workflow, catalog data, or validation rules caused the failure, update that file, and rebuild until all checks pass. ## Quick Start Run the card self-evolution loop on the card that just failed validation and update whichever skill file caused the failure.

Frequently Asked Questions about ygo-card-self-evolve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a Yu-Gi-Oh! card that fails validation checks?▼

Run the self-evolution loop: rebuild the card following the build workflow, run mdcheck.py, catalogcheck.py, and combocheck.py, then trace each error to the responsible skill file and update it before rebuilding from scratch.

What triggers the card self-evolution process?▼

Triggers include mdcheck.py errors after following the build workflow, validation scores below threshold, comparison match rates under 50 percent, missing catalog cards, combo validation failures, and incorrect power level calibration.

How do I know which skill file to update after a failure?▼

Map the failure type to its source: ambiguous build steps go to card-build, missing or wrong catalog entries go to catalog files, comparison workflow gaps go to card-compare, and wrong combo validation rules go to the validate skill.

What verification is required after updating skill files?▼

Updated files must stay under 200 lines per the markdown-maintenance rules, be linked from their parent SKILL.md, and pass re-run validation scripts on the card that originally triggered the evolution.

When should the card catalog be updated instead of the build workflow?▼

Update the catalog when a key card is missing or an entry threshold is wrong, since these are data gaps rather than workflow problems. Build workflow updates apply only when steps are ambiguous or missing.