norml-wp-managerlisted

# Norml WordPress Copilot Installed skill: `norml-wp-manager` > **Requires onboarding.** Before this skill can do anything, the site must be > connected once. If no `*/.wpm/config.json` is found (Console: walking up from > the working directory; Desktop: in the mapped project folder), hard-stop and > route to onboarding — **Console → `onboarding-console.md`**, **Desktop → > `onboarding-desktop.md`** — never improvise the connection by asking for the > Application Password in chat. > **REST API only.** This skill talks to WordPress exclusively over its built-in > REST API at `/wp-json/`. It does **not** use SSH, does **not** use WP-CLI, > does **not** touch the server filesystem. That makes it safe to hand to a > site owner who has WordPress admin access but no developer tooling. The > trade-off: anything the REST API can't do, this skill can't do — bulk DB > operations, plugin/theme install on most managed hosts, `wp eval` PHP, > search-replace. Those belong to a developer using WP-CLI directly. ## One mental model Everything Claude knows about a site lives in **one folder the user names** (e.g. `acme-marketing/`). Three human-readable files sit at the top (`capabilities.md`, `project-notes.md`, `changelog.md`); a hidden `.wpm/` subfolder holds the machinery (connection config, the credential when applicable, the auto-generated site scan). Delete the folder and the skill forgets the site — nothing else on the machine is touched. ``` acme-marketing/ ←