Individual skill

figma-bridge-doctor

Diagnose or restore the figma-console Desktop Bridge with a minimal state-based action and verified pairing. Recovery is session-safe; macOS scripts, restart and persistent helpers keep their own permissions.

plugins/thiagoxikota/figma-maxxing/skills/figma-bridge-doctor/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Figma Desktop Bridge recovery

Choose the smallest action that gets this task connected to the intended file,
and verify it. This skill owns figma-console Desktop Bridge recovery, not
canvas work or the official remote server. Scripts are macOS-specific; on other
platforms report the relevant manual path without running macOS commands.

## Normal path

1. Probe the available `figma_get_status`; confirm pairing/file, not just a
listening process. Use this skill’s `scripts/figma-status.sh` when local
ports/owners/plugin drift are needed; it is diagnosis, not pairing proof.
2. Resolve the target from URL, paired file or a verified alias. Ask only for a
missing/ambiguous file; do not require the user to name a harmless derived alias.