agentleFS
charleslucascharleslucas/poe_mcp_suite/.claude/skills/spectre-analysis/SKILL.md

spectre-analysis

Skill9 starsChanged 3 months agoMITView on GitHub

Choose, measure, and correctly model spectres for a Path of Exile minion build — which spectre to raise or buy, what a spectre actually grants, and why PoB shows no change when you add one. Use for "which spectres should I use", "is spectre X worth buying", "what does this spectre grant", "my spectres do nothing in PoB", or any minion-build measurement that looks lower than the in-game character sheet.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read playbooks/README.md first — the shared meta-framework (cursory-vs-detailed gate, pre-flight, trust hierarchy, narration norms).

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

This task uses the Spectre Analysis playbook. The playbooks in playbooks/ are the single source of truth — read them rather than working from memory.

  1. Read playbooks/README.md first — the shared meta-framework (cursory-vs-detailed gate, pre-flight, trust hierarchy, narration norms).
  2. Then read playbooks/spectre-analysis.md and follow it.

The one thing that invalidates naive work here:

  • PoB applies the buffs of only ONE spectre — the selected minion of a Raise Spectre instance (CalcPerform.lua:2169). Adding a spectre and seeing zero change is the expected result for a non-selected spectre, and is indistinguishable from a broken mod. Measure by listing the spectre first, or build the modeling group (playbook Step 3) to model several at once.
  • Imports never set spectres; the PoE API doesn't report them. A modeling group is destroyed by every import — re-add it as part of the post-import checklist.
  • grants: in the text lake is lossy: it drops conditions (MonsterTag) and omits auras, which live in skills:. Read the raw Data/Spectres.lua entry before believing it.
  • Corpse spectres are traded by base_type, not name, and are absent from poe.ninja.

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.