wow-addon-structure
Verbose guide for WoW AddOn structure, .toc metadata, loading order, SavedVariables, and C_AddOns metadata and load APIs. Use when planning addon folder layout, file order, or SavedVariables wiring. Select Retail, Forever, or Classic with wow-client-targets before using historical listings.
How do I install this agent skill?
npx skills add https://github.com/jburlison/wowaddonapiagents --skill wow-addon-structureIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides comprehensive documentation for World of Warcraft AddOn development, covering folder structure, metadata, and loading lifecycles. It is informational but includes instructions for the agent to process external AddOn files, creating a potential surface for indirect prompt injection. No malicious code or suspicious network activity was identified.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerpass
7 files scanned · No issues
What does this agent skill do?
addon structure
Use for any selected combination of Retail, Forever, and Classic progression. First resolve the target and pinned source with wow-client-targets.
Target-specific decisions
Load the base localization catalog, locale overrides and then text consumers in each target's file list. Initialize/migrate SavedVariables before options registration; keep database keys independent of display language.
Verify third-party TOC directives, client interface, addon loading APIs, dependencies, initialization order, and SavedVariables. Package a normal TOC per target rather than assuming every client supports the same suffixes or conditions.
Read the relevant row in compatibility guidance. Verify only the APIs needed for this task, using commit-pinned definitions and loaded client code. Missing evidence means unknown, not supported or removed. When offline, disclose the snapshot version/date and unresolved behavior.
Detailed lookup material
Use the pinned source schemas for complete generated contracts in this domain, including typed arguments, returns, event payloads and restrictions. Query only the needed symbols. Source declarations leave loading, runtime behavior and addon permission unresolved unless separately verified.
The historical Retail baseline retains the original API listings and examples. It is a research aid, not current or cross-client verification. Open only relevant supporting references:
For implementation and release validation, use wow-addon-development.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/jburlison/wowaddonapiagents/wow-addon-structure">View wow-addon-structure on skillZs</a>