agentsclimarketplace

Review comments

Skill tokyo-megacorp/figma-differ/skills/review-comments

Fetches comments from a Figma file and surfaces unresolved ones grouped by node. Use when the user runs /figma-differ:review-comments with a Figma URL, or says "show Figma comments", "what are the open Figma comments", "review Figma feedback", or "check Figma annotations".From its SKILL.md

Install
npx -y skills add tokyo-megacorp/figma-differ --skill review-comments

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, as published. Nobody here has run it

Fetch and Surface Figma Comments

1. Parse the URL

Extract fileKey from the Figma URL. Note nodeId if present (used for filtering). Check for --all-comments flag in arguments.

2. Check prerequisites

Verify a Figma token is loadable: bash scripts/auth.sh status (if it fails, tell the user to run bash scripts/auth.sh set and stop).

Data discipline

  • NEVER keep raw API responses, JSON trees, or large frame content in the conversation context
  • ALWAYS write intermediate data to disk (temp files or ~/.figma-differ/)
  • Subagent prompts MUST include: "Write results to <path>. Report only counts and file paths."
  • Final summary to user: counts, paths, and actionable next steps only

3. Fetch comments

bash $CLAUDE_PLUGIN_ROOT/scripts/figma-api.sh fetch_comments <fileKey>

4. Filter and group

From the JSON response:

  • Default: filter to comments where resolved_at is null (unresolved only)
  • If --all-comments: include all comments
  • Group by client_meta.node_id (the node the comment is anchored to)
  • Sort by created_at descending (newest first)

5. Display

Figma Comments — <fileKey>
<N> unresolved comments (run with --all-comments to see resolved)

Node: <node_name or node_id>
  - [<author>] <message> (<relative_time>)
  - [<author>] <message> (<relative_time>)

Node: <node_name or node_id>
  - [<author>] <message> (<relative_time>)

File-level comments (no node anchor)
  - [<author>] <message> (<relative_time>)

If no unresolved comments: No unresolved comments in this file.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.