ygopro-script-self-evolve

Updates YGOPro script skill documentation based on comparison and debugging feedback.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When YGOPro card script implementations produce wrong results despite following documented skills, the underlying skill documentation itself is wrong or incomplete. This Skill closes that gap by systematically updating API docs, build rules, and comparison guides based on evidence from comparison and debugging sessions. ## Core Features & Use Cases - Trigger-Based Evolution: Activates when script comparison reveals systematic errors (event codes, effect types, helper usage, scoping), made-up functions or constants, undocumented API patterns, or multi-effect cards merged into single effects. - Targeted Documentation Updates: Routes fixes to the correct file — api/procedure.md for helper misunderstandings, api/constants.md for constant usage errors, build SKILL.md for common mistakes and absolute prohibitions. - Verification Loop: Re-runs the triggering comparison after updates and enforces constraints like the 200-line file limit and parent SKILL.md linkage. - Use Case: A comparison reveals a hallucinated constant in generated card scripts. This Skill adds an explicit prohibition to the build skill's Absolute Prohibitions section and verifies the fix by re-running the comparison. ## Quick Start Use the ygopro script self-evolve skill to update the script build documentation based on the errors found in this comparison report.

Frequently Asked Questions about ygopro-script-self-evolve

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

FAQPage Schema
How do I fix recurring errors in YGOPro card script generation?▼

Identify the error category from comparison results, then update the responsible skill file: build SKILL.md for common mistakes, api/procedure.md for helper misunderstandings, or api/constants.md for constant usage errors. Re-run the comparison afterward to confirm the fix.

What triggers a script skill self-evolution cycle?▼

Triggers include systematic comparison errors in event codes or effect types, made-up functions or constants, undocumented API patterns found during debugging, multi-effect cards merged into one effect, and missing EFFECT_FLAG_CARD_TARGET or chkc checks.

How should hallucinated YGOPro API functions be handled?▼

Treat a made-up function or constant as a critical failure. Add an explicit prohibition to the Absolute Prohibitions section of the script-build SKILL.md so the build skill stops generating it.

What constraints apply when updating YGOPro skill files?▼

Updated skill files must stay under 200 lines and remain linked from their parent SKILL.md. After editing, re-run the comparison that triggered the evolution to verify the gap is addressed.

When should API documentation be updated instead of build rules?▼

Update api/ files when a real function, pattern, or procedure helper is undocumented or misunderstood. Update build or compare skills when the issue is a recurring mistake pattern or a fabricated API element.