ygopro-script-research

Analyzes existing YGOPro Lua card scripts to explain effect implementations and API usage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding how a Yu-Gi-Oh! card effect is implemented in YGOPro requires digging through Lua scripts, constants, and procedure helpers scattered across the codebase. This Skill provides a structured workflow to locate, read, and summarize any card script. ## Core Features & Use Cases - Script Location & Identification: Find card scripts by ID or name using ydkshow.py or sqlite3 on cards.cdb, mapping to the c<card_id>.lua file convention. - Effect Breakdown: Identify registered effect types, event codes, and callback functions (condition, cost, target, operation) with cross-references to API documentation. - Structured Output: Produce a standardized summary listing effects, API functions, constants, and procedure helpers used. - Use Case: Given a card like a Synchro monster, trace its AddSynchroProcedure call in procedure.md, decode its EFFECT_TYPE and EVENT constants, and document exactly how each effect triggers and resolves. ## Quick Start Analyze the YGOPro script for card ID 44519536 and summarize its effects, callbacks, and API functions used.

Frequently Asked Questions about ygopro-script-research

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

FAQPage Schema
How do I find the Lua script for a specific Yu-Gi-Oh! card in YGOPro?▼

Identify the card by ID or name using ydkshow.py or by querying cards.cdb with sqlite3. The script is located at script/c<card_id>.lua, where the card ID is the 8-digit zero-padded password.

How to understand what a YGOPro card script does?▼

Read the script and identify registered effect types, event codes, and callback functions such as condition, cost, target, and operation. Cross-reference unfamiliar API functions and constants against the api/ documentation files.

What is the aux namespace in YGOPro scripts?▼

The aux namespace is the standard alias for utility functions defined in script/utility.lua. Card scripts use it to call common helper functions rather than writing the full Auxiliary prefix.

Where are YGOPro constants and procedure helpers defined?▼

Constants are defined in script/constant.lua and documented in api/constants.md and api/consteffect.md. Summoning procedure helpers like AddSynchroProcedure and AddFusionProcMix live in script/procedure.lua and are documented in api/procedure.md.

What naming conventions do YGOPro card scripts follow?▼

Scripts define a local card ID variable and an initial_effect function that registers effects with SetCode, SetType, SetRange, SetCondition, SetCost, SetTarget, and SetOperation. Callbacks are typically named cXXXXX.filter, cXXXXX.condition, cXXXXX.target, and cXXXXX.activate.