v3.4.0 — Setup checks the machine first
Setting these up used to mean checking four things by hand and hoping. Now the setup step checks them for you and names what is absent.
fig 3.4.0 · pm 0.6.0
The failure that never announced itself
The README already carried the warning: a skill cannot call a tool it was never given, and it does not fail loudly when one is missing — the run simply comes back thin, and that reads as the skill having found nothing to do. It was listed under troubleshooting, which is to say you met it after losing the time.
/fig:setup and /pm:setup now open with a preflight. It reports python3 and PyYAML, node, and which connectors actually answer, then stops if something required is absent rather than running on.
An optional connector that isn't connected comes back as absent rather than a failure — it only matters once a config key points at it, and the report says which key that would be. Claude in Chrome comes back unknown: it is a browser extension rather than an MCP server, so the shell genuinely cannot see it, and guessing would be worse than saying so.
Getting started branches
The install step has always offered pm as optional, and then every step after it was written for fig. If you installed pm alone, the guide ran out.
Step 2 is now a fork — fig, pm, or a deck template — with each path carried through to its own end. /fig:deck-setup, which has to run before /fig:deck and was mentioned twice in passing further down the page, sits in that table.
Both plugin READMEs also say what the setup step checks before it runs, and the Korean and English READMEs stay line-for-line aligned.