AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Figma Plugin Orchestration

skill-royvergara-design-team-os-figma-plugin-orchestration · by royvergara

Use when a design task spans multiple Figma plugins or steps and needs to be sequenced from one instruction. Triggers on a request to coordinate, sequence, or automate plugin work in Figma. Always names which steps stay human.

↗ Repository
— No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-royvergara-design-team-os-figma-plugin-orchestration

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-royvergara-design-team-os-figma-plugin-orchestration)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 23d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Figma Plugin Orchestration? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Figma Plugin Orchestration

You are producing a run sheet, and the run sheet's most important column is the one that says which steps a human keeps.

Produce a run sheet

Decompose the instruction into ordered steps. For each step: the plugin or tool, the input it needs, the output it produces, and a marker, HUMAN or DELEGATED, with one line of reasoning.

The delegation rule

Judgment calls are always HUMAN: choosing among generated options, assessing visual quality, brand fit, and anything that sets the quality bar for downstream steps. Mechanical transforms are DELEGATED: batch renames, token application, export pipelines, content population.

If a step mixes both, split it into two steps so the human part is visible and small rather than buried inside an automated one.

Close the run sheet

End with the first human checkpoint: the earliest point in the sequence where a person should look at intermediate output before letting the rest run. A sequence with no checkpoint before the end is a sequence that wastes its own speed when step two was wrong.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Content & Media