Agent skill · Audited from source
Cds Docs
skill · coinbase/cdsNOASSERTION licenceAudited 14 Oct 2026 · source a03fbe3db14b
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: Retrieve Coinbase Design System (CDS) documentation: setup, installation, theming, tokens, and per-component APIs/examples. Use this skill whenever the task involves CDS components, design-system rules, theming, or…
Cite
Cite this page
ModelsAtlas. “Cds Docs (coinbase/cds)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/coinbase/cds-docs
Trust audit
Audit 0.4.1 · source read 14 Oct 2026
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
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | WARN | 2 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (2)
MEDIUMInventory / provenanceinv.symlink · .claude/skills/git.resolve-version-conflicts
.claude/skills/git.resolve-version-conflicts
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/skill-creator
.claude/skills/skill-creator
- Why
- link not followed
- Fix
- —
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/skills/cds-docsThe 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: Retrieve Coinbase Design System (CDS) documentation: setup, installation, theming, tokens, and per-component APIs/examples. Use this skill whenever the task involves CDS components, design-system rules, theming, or…
---
name: cds-docs
description: |
Retrieve Coinbase Design System (CDS) documentation: setup,
installation, theming, tokens, and per-component APIs/examples. Use this skill whenever the task involves CDS components,
design-system rules, theming, or choosing between web and mobile CDS packages, even if the user
only says "use CDS" or names a component. Always start from the docs route index, then fetch
only the pages you need to reason and implement correctly. Prefer the CDS MCP server
(`list-cds-routes`, `get-cds-doc`); if MCP is unavailable, use curl against
https://cds.coinbase.com/llms/....
license: Apache-2.0
metadata:
version: '2.0.0'
---
# CDS Documentation Skill
**Goal:** Pull CDS documentation **into the session** so your next edits, recommendations, and
API usage are **grounded in current docs**—not to produce a documentation handout for the user.
Treat fetched pages as **source material you have read**: internalize props, patterns, imports, and
setup constraints, then **act** (code, refactors, answers) from that understanding. Quote or
summarize for the user only when it helps. Keep the actual doc page contents to yourself
and only share their contents directly to the user if they ask.
Whether you use the CDS MCP server or fetch the pages yourself with `curl` is an implementation detail.
The use does not need to know your methodology unless they indicated they are debugging this skill.
**Ambiguous product requests** (e.g. “turn this into tabs,” “make it a card”) after you’ve read the
index: if **several** CDS components could be relevant (e.g. underline `Tabs` vs pill `SegmentedTabs` vs
`TabNavigation`), it is **acceptable and often better** to ask **one** short, concrete question (e.g.
which visual pattern matches their spec) while briefly naming the options and how they differ per
the docs. Do not pick one arbitrarily just to avoid asking.
## 1. Choose platform
Decide whether the work targets **web** (React, `@coinbase/cds-web`) or **mobile** (React Native,
`@coinbase/cds-mobile`). If unclear, infer from the repo (e.g. `package.json` dependencies, `apps/*`
layout) or ask a single clarifying question.
Pass `web` or `mobile` to `list-cds-routes` and when building curl URLs.
## 2. Tool order (try in sequence)
1. **CDS MCP server** (packaged `mcp-docs` in `@coinbase/cds-mcp-server` / `packages/mcp-server`):
- `list-cds-routes` with `platform`: `"web"` | `"mobile"`.
- `get-cds-doc` with `route`: path **including the platform**, ending in **`.txt`** (e.g.
`web/getting-started/installation.txt`). Paths must come from the index.
2. **curl** if MCP is not configured, fails, or returns errors:
- **Index:** `https://cds.coinbase.com/llms/web/routes.txt` or
`https://cds.coinbase.com/llms/mobile/routes.txt`
- **Page:** `https://cds.coinbase.com/llms/<route>` where `<route>` matches the index (e.g.
`web/getting-started/theming.txt`).
Use `curl -fsSL '<url>'`. Prefer **targeted fetches** (the pages you need for this task) over
loading everything; the index is for **routing**, not for echoing back wholesale.
## 3. Workflow whenever this skill applies
1. Resolve **platform** (`web` or `mobile`).
2. **Load the index** once per platform focus (`list-cds-routes` or `routes.txt`) and use it as the
canonical map of `.txt` paths.
3. **Fetch additional pages** only as needed for the work ahead; after each fetch, **apply** what
you learned (imports, props, patterns)—do not stop at regurgitating the file.
## 4. Practical notes
- Routes are **case-sensitive**; doc content is **`.txt`** from MCP or HTTP.
- Web and mobile docs differ; confirm the component or topic exists for that platform’s index.
- Human-readable URLs inside the `.txt` files are optional to share with the user; your priority is
**correct implementation**, not reproducing the doc site in the reply.
## 5. What “done” looks like
- **Platform** is correct or explicitly chosen.
- **Index** informed which pages you pulled.
- **User-facing output** is implementation-focused (components, imports, structure); retrieval steps
stay implicit unless the user needs them.
- If multiple components fit, you either **ground the choice in doc differences** or **ask one
clarifying question** when the product spec is under-specified.
- Your **actions and explanations** reflect **fetched** CDS details (APIs, setup, tokens)—especially
where memory would be risky—not a dump of documentation for its own sake.Excerpt, first 4,499 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
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
- !CAUTION B 89 / 100
first audit · source
a03fbe3db14b
Similar skills
All docs & writing skills →mattpocock/skills
Implement a piece of work based on a spec or set of tickets.
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
mattpocock/skills
Pursue a long-running goal in a single session by co-ordinating subagents.
Questions about Cds Docs
What does the Cds Docs skill do?
Is Cds Docs safe to install?
What can Cds Docs access on my machine?
How current is this page?
Sources
- github.com/coinbase/cds/tree/master/skills/cds-docs — the audited source at commit a03fbe3db14b and every finding aboveObserved · 14 Oct 2026
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.
- What does the Cds Docs skill do?
- Is Cds Docs safe to install?
- What can Cds Docs access on my machine?