メニュー
Extract Figma frame trees and image renders via Figma REST API without Desktop MCP. Use for headless SSH/CI work, MCP startup failures, frame inventories, or downloading PNG/SVG/JPG outputs from Figma file/node URLs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Coordinate complex asynchronous multi-agent work with Honeybee `hive` and Pollinate. Use when Codex must plan, launch, ramp, monitor, message, collect, merge, stop, or recover many hive agents, from a few Claude/Codex/Grok bees to tens, hundreds, or thousands of sharded asynchronous agents, including Pollinate-triggered schedules/webhooks/polls and Hive flows/loops.
Operate Honeybee through the `hive` CLI for durable AI agent sessions, swarms, colonies, frames, flows, loops, buz messaging, sealing, transcripts, search, cleanup, remote nodes, and daemon state. Use when Codex must spawn or control Claude/Codex/OpenCode/Grok/Pi/Droid/arbitrary harness agents, coordinate multiple agents, inspect agent output, register reusable swarm blueprints, run Honeybee flows, or recover/stop Honeybee work.
Configure and operate Pollinate, the standalone trigger substrate for schedules, event polls, webhooks, temporary hooks, routers, delivery policies, context resolution, job inspection, and typed actions into Honeybee, Hermes, HTTP, shell commands, or internal emits. Use when Codex needs durable time/event/webhook activation, GitHub PR routing to hive agents, debounced/batched/throttled delivery, or observable trigger-to-action automation.
Generate ad-hoc and saved Honeybee `hive flow` templates for fan-out/fan-in, multi-agent coordination, loops, router-triggered work, collection, merge/review stages, and reusable orchestration recipes. Use when Codex must design, write, register, run, or explain JSON or TypeScript Hive flows, especially dynamic flows that spawn many agents, coordinate via buz/seals, loop until stop conditions, or integrate with Pollinate triggers.
Manage forge mesh topology: provision nodes, promote master, demote nodes, and verify routing readiness.
Use forge node command family for remote command routing and per-node registry access.
| name | figma-api-extractor |
| description | Extract Figma frame trees and image renders via Figma REST API without Desktop MCP. Use for headless SSH/CI work, MCP startup failures, frame inventories, or downloading PNG/SVG/JPG outputs from Figma file/node URLs. |
Use this skill when Figma Desktop MCP is unavailable or unstable and you still need frame/image extraction.
export FIGMA_TOKEN=... (or FIGMA_ACCESS_TOKEN).
Optional autoload: put token in ~/.config/env/figma.env (FIGMA_TOKEN=...), sourced by shell profile.python3 scripts/figma_extract.py --url "<figma-url>" --top-level-only --desktop-only --images --download-images --out /tmp/figma-outfile_key and node_id from URL./v1/files/{file_key}/nodes).top-level mode: direct child frames of the target node.
all-frames mode: recursive frame scan.--desktop-only, min size flags)./v1/images/{file_key}).frames.json: extracted frame metadata (id, name, depth, bbox)image-urls.json: frame id -> signed image URL (if --images)images/: downloaded files (if --download-images)scripts/figma_extract.py: main extractorscripts/sync_harness_skill.sh: symlink this skill into codex/cc/oc homes