“MCP gives your AI reach. Skills give it a recipe.” Murphy Trueman compresses two acronyms into one sentence you can actually hold onto. MCP is access: Claude reading your real Figma file, walking every fill on a button set and finding the fourteen layers still on raw hex, all of them on hover and disabled states. A skill is the playbook it follows once it’s in there. Their rule for writing one is the third time you catch yourself explaining the same preference, write it down.

The post above shows the skills, this one shows the plumbing. Miggi builds 3 skills: a type scale generator that also writes the variables, an image audit that drops a DPI card beside every image, and Shader Starter, which pairs neatly with the shaders update below.

Miggi rounds up ten community skills for the Figma agent, though the real news is in the first line: you can now author skills inside Figma. Ask the agent to draft one using a design frame as reference, preview it, then keep iterating in chat or open the markdown editor for manual changes. Emil Kowalski’s /find-animation-opportunities, which scans a file for places that don’t animate but should, and Jakub Krehel’s /better-interface which catches the details your interface is missing, are the ones I’d install first. 

The skills demo is the one to watch. Rodrigo calls a slash command for a skill his teammate Tammy wrote in plain English, carrying her own design-review conventions, and the agent returns the critique as annotations right on the canvas. Team practice becomes a callable command.