ygo-deck-self-evolve

Iteratively improves Yu-Gi-Oh deck-building skills using ydkcheck.py failures and comparison results.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deck-building guidelines can silently produce invalid or weak Yu-Gi-Oh decks, and without a feedback loop the same mistakes repeat. This Skill closes that gap by turning ydkcheck.py errors, low match rates, and self-duel observations into concrete updates to the underlying deck-building knowledge files. ## Core Features & Use Cases - SMART Self-Evaluation Loop: Runs a 7-step cycle of building, validating with ydkcheck.py, comparing against reference decks, and self-duel playtesting until quality thresholds are met. - Root-Cause Diagnosis: Maps each failure type (ban limit violations, unsummonable extra deck cards, low hand trap counts, missing engines) to the specific skill file responsible. - Targeted Evolution Actions: Updates deck-build workflow, metrics thresholds, engines data, card catalogs, or comparison logic with evidence-backed changes. - Use Case: After building a deck that scores below 60 on ydkcheck.py, run this loop to identify whether the metric threshold or the build workflow is wrong, fix the responsible file, and rebuild until the deck passes with 0 errors and a 50%+ match rate. ## Quick Start Run the deck self-evolve loop on my latest deck build and update whichever skill files caused the ydkcheck.py errors.

Frequently Asked Questions about ygo-deck-self-evolve

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

FAQPage Schema
How do I fix a Yu-Gi-Oh deck that fails ydkcheck.py validation?▼

Follow the self-evolve loop: rebuild the deck using the deck-build workflow, run ydkcheck.py with section all, then trace each error to the responsible skill file such as build steps, metrics thresholds, or catalog data. Update that file and rebuild until ydkcheck.py reports 0 errors.

What triggers the deck self-evolution loop?▼

Triggers include ydkcheck.py errors, quality scores below 60, T1 start rate under 80 percent, comparison match rate below 50 percent, fewer than 9 hand traps, unsummonable extra deck cards, missing catalog cards, undocumented engines, ban limit violations, and alias conflicts.

How does deck comparison improve deck-building accuracy?▼

Comparing your build against reference decks and recording all differences exposes gaps in core card identification and card selection. A match rate below 50 percent indicates the build workflow needs correction, and each systematic difference is traced back to its root-cause skill file.

When is a deck build considered successfully evolved?▼

A one-time pass requires ydkcheck.py to report 0 errors on the first run after building, a comparison match rate of 50 percent or above, and self-duel observations matching the written deck experience file. The loop repeats until all three conditions hold.

What are the limitations of automated deck self-evolution?▼

The loop depends on the accuracy of existing reference decks, catalog data, and engine documentation, so missing or outdated source data limits diagnosis quality. It also requires ygopromcp self-duel capability for playtest verification, which may not cover every matchup scenario.