CtrlK
BlogDocsLog inGet started
Tessl Logo

cds-docs

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/....

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable procedural skill with concrete commands, a clear sequenced workflow, an error-recovery fallback, and a done-checklist. The only weakness is minor verbosity in a few meta-guidance sentences that could be tightened (one contains a typo: "The use" for "The user").

Suggestions

Tighten the meta-guidance paragraphs (e.g. the "implementation detail / the use does not need to know" sentence) to lift conciseness; fix the typo "The use" → "The user".

The intro Goal/principles block can be compressed — the core directive (ground edits in fetched docs; don't dump docs at the user) can be stated in one or two lines instead of three paragraphs.

Consider collapsing sections 2 and 3 since both describe the same fetch sequence from different angles; a single ordered workflow would reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly lean and directive with no concept-explanation padding, but a few meta sentences (e.g. "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...") could be trimmed; not every token earns its place.

4 / 5

Actionability

Provides copy-paste-ready commands covering common cases: MCP `list-cds-routes`/`get-cds-doc` with argument shapes, and curl examples for both web and mobile index and per-page fetches (`curl -fsSL '<url>'`).

5 / 5

Workflow Clarity

Section 3 gives a clear sequenced workflow (resolve platform → load index → targeted fetches → apply), with an error-recovery fallback (MCP fails → curl) and a "What done looks like" checklist closing the loop.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clearly numbered sections and a completion checklist; no external references are needed and nothing that belongs in a separate file is inlined, so structure is appropriate.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality description that concretely states capabilities, includes natural trigger phrases users would actually say, and explicitly covers both what and when in third person. It is distinct to the CDS niche with negligible overlap risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "setup, installation, theming, tokens, and per-component APIs/examples" plus retrieval mechanics (MCP `list-cds-routes`/`get-cds-doc`, curl) — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both: what ("Retrieve Coinbase Design System (CDS) documentation: setup, installation, theming, tokens, and per-component APIs/examples") and when ("Use this skill whenever the task involves CDS components, design-system rules, theming...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural terms users would say — "CDS components", "design-system rules", "theming", "web and mobile CDS packages", "use CDS", and naming a component — including synonyms (CDS / Coinbase Design System) and package names.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Coinbase Design System specifically) with distinct triggers (CDS, web/mobile packages, named components), giving minimal conflict risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
coinbase/cds
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.