Agent Skill
Figma Use Slides skill
figma-use-slidesDevin-AXIS/iPolloWorkexamples/plugin-packages/figma/skills/figma-use-slides/SKILL.md
This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
always on
43 tokname + description
once used
4,848 tokSKILL.md body
bundled files
646 KB
repo stars
7.1kGitHub
Install the Figma Use Slides skill
Skills CLI (Claude Code, Codex, Cursor and others)
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill figma-use-slides
Claude Code, by hand (all projects)
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git /tmp/iPolloWork mkdir -p ~/.claude/skills cp -R /tmp/iPolloWork/examples/plugin-packages/figma/skills/figma-use-slides ~/.claude/skills/figma-use-slides
For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.
What it costs your context
Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.
| When | What loads | Cost |
|---|---|---|
| Every session | Name and description | 43 tok |
| When the agent uses it | The SKILL.md instructions | 4,848 tok |
| Only if opened | 6 bundled files (46 KB) | varies |
Until it is used, figma-use-slides costs about 32× less than the median MCP server we measured (1,363 tokens on every turn). Installing all 102 skills from Devin-AXIS/iPolloWork would load 4,966 tokens of descriptions. Skills vs MCP study
Checks
Our checks found nothing to flag: it follows the Agent Skills specification's naming and size guidelines and doesn't pipe downloads into a shell.
Checked 2026-10-22 · method
What's inside
The headings of its SKILL.md. Read the full file on GitHub.
- usefigma — Figma Plugin API Skill for Slides
- Choosing How to Build a Slides Deck
- When to use which
- Pick one and commit
- Critical Rules (Slides-specific)
- Design Thinking
- New deck design process
- Reading a reference file
- Deck-Building Workflow
- Phase 1 — Design & Plan
- Phase 2 — Build
- Sections
- When asked to organize a deck
- Naming + scoping
- Renaming a section
- Speaker Notes
- When to write speaker notes
- What good speaker notes look like
- What to avoid in speaker notes
- Formatting
- Inspecting Slides Files
- Quick inspection scripts
- Reference Docs
More skills from Devin-AXIS/iPolloWork
- acme-researchDevin-AXIS/iPolloWork
Search and summarize material from the Acme research service.
7.1k16 tok idle · 126 in use - agent-first-screenshotsDevin-AXIS/iPolloWork
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
7.1k269 tok idle · 1,128 in use - context7-docs-researchDevin-AXIS/iPolloWork
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
7.1k29 tok idle · 99 in use - context7-version-aware-implementationDevin-AXIS/iPolloWork
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
7.1k31 tok idle · 106 in use - create-pluginDevin-AXIS/iPolloWork
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
7.1k58 tok idle · 1,227 in use - daytona-chrome-cdpDevin-AXIS/iPolloWork
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
7.1k49 tok idle · 556 in use - daytona-cloud-serverDevin-AXIS/iPolloWork
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
7.1k45 tok idle · 598 in use - daytona-devDevin-AXIS/iPolloWork
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.
7.1k49 tok idle · 1,455 in use