agentleFS
Sign inStart free
JBurlisonJBurlison/WoWAddonAPIAgents/skills/wow-api-talents/SKILL.md

wow-api-talents

Skill75 starsChanged 13 days agoMITView on GitHub

Look up WoW Class Talents, Hero Talents, Traits system,

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for any selected combination of Retail, Forever, and Classic progression.

    line 18
  2. Distinctive:

    Read the relevant row in compatibility guidance.

    line 26
  3. Distinctive:

    Use the pinned source schemas for complete generated contracts in this domain, including typed arguments, returns, event payloads and …

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

api talents

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

Trace the loaded talent UI and generated definitions before selecting class-trait, talent/glyph, or specialization APIs. Keep talent identifiers and operations target-specific; unsupported tree operations must be reported.

For Forever Legacy trees, challenges, reward tracks or Legacy.* callbacks, start with Forever Legacy integration. It supplies the 70532 source trace, contracts and load-on-demand boundaries; runtime access still requires validation.

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 other talent features, use the baseline as a search aid and verify the relevant definitions upstream.

For implementation and release validation, use wow-addon-development.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free