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/....
90
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (Coinbase Design System documentation retrieval), lists specific capabilities, and provides explicit trigger guidance including edge cases like casual references. It also includes implementation details about preferred tools (MCP server vs curl fallback), which adds practical value for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: retrieve documentation, setup, installation, theming, tokens, per-component APIs/examples, and describes specific tools (MCP server commands, curl fallback with URL). | 3 / 3 |
Completeness | Clearly answers both 'what' (retrieve CDS documentation for setup, installation, theming, tokens, component APIs) and 'when' (whenever the task involves CDS components, design-system rules, theming, or choosing between packages, even if user only says 'use CDS' or names a component). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'CDS', 'Coinbase Design System', 'components', 'design-system rules', 'theming', 'tokens', 'web and mobile CDS packages', and even covers the casual 'use CDS' or naming a component. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically the Coinbase Design System documentation retrieval. The specific product name, MCP server tools, and URL make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, well-structured skill that provides clear, actionable guidance for retrieving and using CDS documentation. Its main strengths are the concrete tool usage instructions, explicit fallback mechanism, and clear workflow sequencing. Its primary weakness is moderate verbosity—some sections (the preamble, 'What done looks like') repeat or over-explain behavioral expectations that could be more concise.
Suggestions
Tighten the opening preamble: the instructions about internalizing docs and not dumping content could be condensed to 1-2 sentences instead of a full paragraph.
Consider merging 'What done looks like' into the workflow section or removing it, as it largely restates guidance already given in sections 1-4.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elaboration. The preamble about 'source material you have read' and 'internalize props, patterns, imports' is somewhat verbose—Claude understands how to use reference material. The 'What done looks like' section partially repeats earlier guidance. However, it avoids explaining basic concepts and stays focused on the task. | 2 / 3 |
Actionability | Provides concrete, executable guidance: specific MCP tool names and parameters (`list-cds-routes` with `platform: 'web' | 'mobile'`, `get-cds-doc` with route format), exact curl commands with URLs, and clear fallback logic. The route format (e.g., `web/getting-started/installation.txt`) is specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: (1) resolve platform, (2) load index, (3) fetch needed pages, then act. The tool order section provides an explicit fallback sequence (MCP → curl). The skill handles ambiguity cases with clear guidance on when to ask vs. decide. For a documentation retrieval skill, this level of workflow clarity is appropriate—no destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear numbered sections, but everything is inline in a single file. Given the skill's moderate length (~80 lines of content), this is acceptable, but the 'Practical notes' and 'What done looks like' sections could potentially be trimmed or consolidated rather than being separate sections. No bundle files are provided, so there's no external reference structure to evaluate, but the skill doesn't seem to need one. | 2 / 3 |
Total | 10 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coinbase/cds
- Commit
f79a780
- 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.