Live survey304 models · 14 providers · 23,592 auditsAudited implement · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Figma.Enumerate Component Urls

skill · coinbase/cdsNOASSERTION licenceAudited 14 Oct 2026 · source a03fbe3db14b

★ 506pushed 7 days ago
!CAUTIONGrade B · 89/100 · 2 findings · a03fbe3
506repo stars · whole coinbase/cds

Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit a03fbe3db14b and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 2 findings, 0 critical or high. What it does: Enumerates every public component set in a CDS Figma file and produces a list of [Component Name]: [Figma URL] entries grouped by page section. Use this skill whenever asked to list, generate, or audit Figma component…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Figma.Enumerate Component Urls (coinbase/cds)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/coinbase/figma-enumerate-component-urls

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100!CAUTION B
0 critical0 high2 medium0 low0 info

CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 17,406 of 18,389 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityWARN2
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (2)

Audit 0.4.1 · source sha a03fbe3db14b · 14 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publishercoinbase GitHub organizationOwner of the repository this skill is read from
  • Source foldercoinbase/cds/.claude/skills/figma.enumerate-component-urlsThe exact folder we audited
  • LicenceNOASSERTIONAs the repository states it
  • Commit pinned for this verdicta03fbe3db14bA new audit runs when the source changes
  • Repository statusNot archivedLast push 7 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Enumerates every public component set in a CDS Figma file and produces a list of [Component Name]: [Figma URL] entries grouped by page section. Use this skill whenever asked to list, generate, or audit Figma component…

---
name: figma.enumerate-component-urls
description: >
  Enumerates every public component set in a CDS Figma file and produces a
  list of [Component Name]: [Figma URL] entries grouped by page section. Use
  this skill whenever asked to list, generate, or audit Figma component URLs,
  produce a component inventory from a Figma file, or when doing a Code Connect
  refresh/audit that requires knowing which Figma node each component maps to.
  Also trigger when someone asks "what are the Figma URLs for CDS components"
  or wants to find the node-id for a specific component.
---

## Overview

Produces a `[Name]: [URL]` list for every **public** component set in a CDS
Figma file, grouped by the file's page sections. Uses the Figma REST API
directly (more reliable than the Figma MCP tools, which only expose the
currently open page in the desktop app).

Requires `$FIGMA_ACCESS_TOKEN` to be set in the environment.

**Default file**: Unless the user provides a different Figma URL, always use
the canonical CDS Components file:

- **File key**: `k5CtyJccNQUGMI5bI4lJ2g`
- **URL**: https://www.figma.com/design/k5CtyJccNQUGMI5bI4lJ2g/%E2%9C%A8-CDS-Components

---

## Step 1 — Get all pages via the REST API

Use the file key above (or extract it from a user-provided URL — it's the
segment between `/design/` and the next `/`). Then fetch all pages at depth=1:

```bash
FILE_KEY="k5CtyJccNQUGMI5bI4lJ2g"  # override if user provided a different URL
curl -s -H "X-Figma-Token: $FIGMA_ACCESS_TOKEN" \
  "https://api.figma.com/v1/files/${FILE_KEY}?depth=1" | python3 -c "
import json, sys
data = json.load(sys.stdin)
pages = data['document']['children']
for p in pages:
    print(p['id'], '|', p['name'])
"
```

The output mixes two kinds of pages:

| Pattern                            | Meaning                                                         |
| ---------------------------------- | --------------------------------------------------------------- |
| `⚡️ Actions`, `🔘 Inputs`, ...      | **Section header** — group label only, no component sets inside |
| `     ↳ Button`, `     ↳ Modal`, ... | **Component page** — contains the actual component set(s)       |

Collect only the component page IDs (those with the `↳` prefix) for Step 2.
Ignore section header pages, cover pages, staging pages, and deprecated
sections (usually marked `⛔️ Deprecated`).

---

## Step 2 — Batch-query pages for component sets

Query the `/nodes` endpoint at `depth=2` to discover `COMPONENT_SET` children
within each page. Batch many page IDs into one request to stay efficient:

```bash
# IDs are colon-separated (e.g. 60:512), URL-encode : → %3A and , → %2C
IDS="60%3A512%2C0%3A1%2C52733%3A3517"
curl -s -H "X-Figma-Token: $FIGMA_ACCESS_TOKEN" \
  "https://api.figma.com/v1/files/${FILE_KEY}/nodes?ids=${IDS}&depth=2" | python3 -c "
import json, sys
data = json.load(sys.stdin)
for nid, node in sorted(data['nodes'].items()):
    if node is None:
        continue
    page = node['document']
    sets = [c for c in page.get('children', []) if c['type'] == 'COMPONENT_SET']
    print(f'=== {page[\"name\"]} (id: {nid}) ===')
    for s in sets:
        print(f'  [SET] {s[\"id\"]} | {s[\"name\"]}')
    if not sets:
        # No sets at top level — print child types to diagnose
        for c in page.get('children', [])[:5]:
            print(f'  [{c[\"type\"]}] {c[\"id\"]} | {c[\"name\"]}')
"
```

### Edge case: pages that use SECTION containers

Some pages nest their component sets inside Figma `SECTION` nodes rather than
placing them directly as page children. When `depth=2` returns only `SECTION`
entries and no `COMPONENT_SET` entries, re-query those section IDs at `depth=2`
to find the component sets inside them.

The CDS **Tray** page is a known example — its `Tray` component set lives
inside a section called "Tray component".

---

## Step 3 — Exclude internal helper sets

Component sets whose names start with `.` are private design helpers used
internally by other components. They are not public consumer APIs and should
be excluded from the output.

Known examples in the CDS file:

- **Carousel**: `.count`, `.carouselPagination`
- **Select**: `.Input Chip`, `.Dropdown Menu`, `.Checkbox`, `.Tray/Multi Select`, `.Desktop Input Chips`, `.CheckboxGroup`
- **Modal**: `.Header`
- **SegmentedTabs**: `.tabs`
- **TabbedChips**: `.Tab Chip`
- **BottomTabBar**: `.Tab Bar Icon`
- **Tray**: `.ListCells-Mobile`, `.ListCells-Desktop`, `.TabbedChipps-Mobile`, `.TabbedChipps-Desktop`, `.Drag handle`

The rule is simple: if `name.startswith('.')`, skip it.

---

## Step 4 — Format the output URLs

Figma node IDs use `:` internally (`60:512`) but URLs use `-` (`node-id=60-512`).

**Always link to the component node — never the page node.**

Every entry must point to the actual component, whether it's a `COMPONENT_SET`
(has variants) or a bare `COMPONENT` (no variants). Both are valid link targets.
The only thing that's wrong is using a `CANVAS` (page) node ID — that lands on
the whole page rather than the component.

| Situation                                           | Use in URL               | Name entry                                |
| --------------------------------------------------- | ------------------------ | ----------------------------------------- |
| Page has **1** public component (set or standalone) | That component's node ID | The page name (stripped of `↳` and emoji) |
| Page has **2+** public components                   | Each component's node ID | The component/set name                    |

If you're unsure of a node's type, check via the REST API — `type` will be
`COMPONENT_SET`, `COMPONENT`, or `CANVAS`. Skip `CANVAS` IDs.

**URL template:**

```
https://www.figma.com/design/k5CtyJccNQUGMI5bI4lJ2g/✨-CDS-Components?node-id={component-set-id-with-dashes}
```

---

## Output format

Group entries under the section headers from the file (Layout, Actions, Inputs,
etc.) using markdown `##` headings. Within each section, list components in 

Excerpt, first 6,001 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit a03fbe3

Download folder ↗
git clone https://github.com/coinbase/cds
git -C cds checkout a03fbe3db14b

The author documents no install command, so this uses the repository directly. Our verdict covers commit a03fbe3db14b only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. !CAUTION B 89 / 100

    first audit · source a03fbe3db14b

Questions about Figma.Enumerate Component Urls

What does the Figma.Enumerate Component Urls skill do?
Coinbase Design System
Is Figma.Enumerate Component Urls safe to install?
With care. The audit graded it B (89/100) and found 2 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Figma.Enumerate Component Urls access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (a03fbe3db14b), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.