pf2e-mcp: Skill for Claude Code

Building a PF2e character with pf2e-mcp

This skill is the conversational playbook for the pf2e-mcp tools. It does not contain rules content itself -- PF2e content changes on a near-weekly cadence via errata, and the whole point of the rules_* / build_* tools is that they're regenerated from the current official data, so they're a better source of truth than recalled training knowledge. Always call a tool instead of answering a rules or eligibility question from memory.

Tool namespaces

• rules_* (rules_search, rules_get_entry, rules_related, rules_explain, rules_data_version, rules_list_variant_rules): general reference lookup, independent of any character.
• build_* (build_list_ancestries, build_list_backgrounds, build_list_classes, build_list_available_feats, build_list_ability_boost_options, build_check_prerequisite, build_validate_build, build_calculate_derived_stats, build_get_level_up_choices, build_to_pathbuilder_export): character-building tools. Every build_* tool that takes a character argument is a pure function -- it reads the character JSON you pass it and returns a result, but the server keeps no state between calls. You are responsible for holding the in-progress character JSON across the conversation and passing the current version into each call.

Also hold the chosen variant rules, PFS mode, and legacy-content setting across the conversation, the same way you hold the character JSON -- they aren't stored in the character JSON itself (keeps it a clean, portable Pathbuilder export), so you pass them as explicit arguments on every call where they matter:

• variant_rules: list[str] -- on build_get_level_up_choices and build_validate_build. Only 'free-archetype' and 'ancestry-paragon' currently change computed results; other valid slugs (see rules_list_variant_rules) are accepted but don't affect output yet.
• pfs_legal_only: bool -- on build_validate_build, to get a warning for any taken option whose best-effort PFS status isn't 'legal'.
• include_legacy: bool -- on every rules_search/build_list_* discovery tool (rules_search, build_list_ancestries, build_list_backgrounds, build_list_classes, build_list_available_feats, build_list_available_spells, build_list_equipment). Defaults to False (Remaster-only) in every one of them -- pass True for the whole rest of the build once the user says they want legacy content included, don't ask per-tool-call.