figma-workflow-auditor
Audit Figma MCP, design-to-code, code-to-canvas, canvas-editing, and design-system workflows for correctness, freshness, privacy, evidence, and routing quality. Use this skill when the user asks whether a Figma workflow, skill, task plan, MCP capability claim, or agent handoff is valid, current, safe, or production-ready.
How do I install this agent skill?
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill figma-workflow-auditorIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill audits Figma workflows for correctness, privacy, and evidence. It does not perform network operations or code execution. It is categorized as low risk because it processes untrusted inputs, such as transcripts and other skills, without explicit boundary markers, which is a structural surface for indirect prompt injection.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Figma Workflow Auditor
Use this skill as the quality gate for Figma-related workflows. It does not mutate Figma files.
Modes
capability-audit: verify claims against current Figma MCP/tool availability.privacy-audit: check whether data transfer and permissions are acceptable.evidence-audit: check whether claimed reads/writes/exports actually ran.routing-audit: check whether the right Figma specialist was selected.skill-audit: review a Figma skill draft or existing skill.
Workflow
- Identify the workflow under review: prompt, plan, skill, transcript, report, or file change.
- Check official/current sources when capability details may have changed.
- Verify tool evidence: tool response, metadata readback, screenshot/export, local diff, or report artifact.
- Flag overclaims separately from implementation bugs.
- Return findings ordered by severity, with concrete fixes.
Findings Format
Use assets/audit-report-template.md.
Audit Rules
- A Figma MCP claim is weak if it lacks session tool availability and evidence.
- A mutation claim is invalid without a target, scope, executed tool, and readback.
- A privacy plan is weak if it omits what data is sent to Figma or another service.
- A design-to-code plan is weak if it skips local component inspection and visual verification.
- An effects plan is weak if it treats
NOISE,TEXTURE,GLASS, or progressive blur as universally available without runtime checks.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/figma-workflow-auditor">View figma-workflow-auditor on skillZs</a>