addon-complexity

Analyze World of Warcraft addon Lua, TOC, and documentation files for complexity and time estimates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/clearcmos/nixos --skill addon-complexity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: addon-complexity
Source: https://github.com/clearcmos/nixos/tree/main/claude-config/skills/addon-complexity
Command: npx skills add https://github.com/clearcmos/nixos --skill addon-complexity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a realistic assessment of the complexity and development time required for a World of Warcraft addon, cutting through inflated estimates.

Core Features & Use Cases

  • Complexity Auditing: Analyzes Lua source, TOC, and documentation files to evaluate system count, API surface, and novelty.
  • Time Estimation: Delivers a calibrated, honest time estimate for a seasoned developer, broken down by development phase.
  • Use Case: Upload your addon's code and ask for a complexity audit to understand if a feature is a weekend project or a multi-month endeavor.

Quick Start

Run the addon-complexity skill on the current directory to audit the WoW addon.

Frequently Asked Questions about addon-complexity

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

FAQPage Schema
How do I estimate the development time for a WoW addon from its Lua source?

To estimate WoW addon development time, audit the Lua source, TOC, and documentation files to evaluate system count, API surface, and novel work, producing a calibrated per-phase time breakdown for seasoned developers.

What makes a World of Warcraft addon complex to code?

WoW addon complexity is driven by the system count, API surface area, and amount of novel work required, which are evaluated by analyzing Lua source and TOC files to generate a tiered complexity rating.

How do I audit my addon codebase to see if a feature is a weekend project or a multi-month endeavor?

Auditing an addon codebase involves analyzing Lua source and documentation to assess overall scope and novelty, delivering a structured verdict with key complexity drivers and a realistic time estimate.

Can I get a time estimate for developing a WoW addon if I only have Lua and TOC files?

Yes, analyzing Lua source and TOC files provides enough context to evaluate the API surface and system count, generating a calibrated time estimate broken down by development phase.

What is the process for evaluating the API surface of a WoW addon?

Evaluating the API surface involves analyzing the addon's Lua source code and TOC files to measure the scope of systems and novel work, resulting in a tier rating and per-phase time breakdown.