Agent skill · Audited from source
Components.Write 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: Guidelines for creating or updating documentation for a CDS component on the docsite (apps/docs/). Use this skill after creating or making updates to a CDS React component to write high quality documentaiton in the CDS…
Cite
Cite this page
ModelsAtlas. “Components.Write Docs (coinbase/cds)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/coinbase/components-write-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/.claude/skills/components.write-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: Guidelines for creating or updating documentation for a CDS component on the docsite (apps/docs/). Use this skill after creating or making updates to a CDS React component to write high quality documentaiton in the CDS…
---
name: components.write-docs
description: Guidelines for creating or updating documentation for a CDS component on the docsite (apps/docs/). Use this skill after creating or making updates to a CDS React component to write high quality documentaiton in the CDS docsite.
argument-hint: <ComponentName> [additional context] (e.g., "Button", "LineChart add real-time examples")
model: claude-sonnet-4-6
---
Goal: Create or update documentation for a CDS component on the docsite (apps/docs/).
If no component name is provided, ask the user which component they want to document.
## Step 1: Check for Existing Documentation
First, check if documentation already exists for this component:
```bash
apps/docs/docs/components/*/[ComponentName]/
```
- **If docs exist**: Review the existing documentation and identify what needs to be added, updated, or improved. Consider the user's additional context if provided.
- **If docs don't exist**: Follow the full workflow below to create new documentation.
For updates, focus on the specific areas that need improvement rather than rewriting everything.
### Reference Components
When creating or updating docs, reference these well-documented components to understand the documentation style and patterns:
- **LineChart** (`apps/docs/docs/components/charts/LineChart/`) - Comprehensive example with many composed examples
- **Button** (`apps/docs/docs/components/buttons/Button/`) - Good basic component documentation
- **IconButton** (`apps/docs/docs/components/buttons/IconButton/`) - Simple component with clear examples
- **Sidebar** (`apps/docs/docs/components/navigation/Sidebar/`) - Complex component with multiple sub-components
Review these before writing to ensure consistency in style, structure, and depth.
### Reference Files
When writing examples, reference these files for valid values:
- **Icon names** (`packages/icons/src/IconName.ts`) - All valid icon names (e.g., `'checkmark'`, `'close'`, `'warning'`)
- **Design tokens** - Use the `components.best-practices` SKILL for knowledge on valid CDS design token values (Color, Space, BorderRadius, Font, etc.)
## Step 2: Research Phase (for new docs or major updates)
Before writing documentation, research how other popular component libraries document the same (or similar) component. Use web search to find documentation for the component in:
- **Material UI** (mui.com)
- **Radix UI** (radix-ui.com)
- **Mantine** (mantine.dev)
- **Ant Design** (ant.design)
- **Base UI** (base-ui.com)
Look for:
- What examples they provide and how they're organized
- Common use cases they demonstrate
- Edge cases or patterns worth highlighting
- Accessibility guidance they include
- How they explain complex features
Use these insights to inform your documentation structure and examples.
## Step 3: Check Component Availability
Verify where the component exists:
```bash
packages/web/src/[source-category]/[ComponentName].tsx # for web
packages/mobile/src/[source-category]/[ComponentName].tsx # for mobile
```
Also check for Storybook stories (`packages/*/src/**/__stories__/[ComponentName].stories.tsx`). If one exists, add the `storybook` field to webMetadata.json.
### Check for Styles
Check if the component supports the `styles` and/or `classNames` props by looking at its type definitions. Components with these props should have a styles tab in the documentation. Look for:
- `styles?: { ... }` prop with named style selectors
- `classNames?: { ... }` prop with named class selectors
If the component has these props, the docgen will generate styles data that can be used for the styles doc.
## Step 4: Required Setup Steps (for new docs only)
Before creating the component documentation, complete these setup steps:
### 4.1 Add to ReactLiveScope
In `apps/docs/src/components/page/ReactLiveScope.ts`, add the component imports and add them to the scope:
```ts
// Add imports
import { ComponentName } from '@coinbase/cds-web';
// Add to scope object
const ReactLiveScope = {
// ... existing scope
ComponentName,
};
```
There is a chance that the component has already been imported.
### 4.2 Update sidebars.ts
In `apps/docs/sidebars.ts`, add the component to its category section:
```ts
module.exports = {
docs: [
// ... other sections
{
type: 'category',
label: 'Category', // e.g., 'Buttons', 'Layout', etc.
items: [
// ... other components
'components/category/ComponentName/index',
],
},
],
};
```
### 4.3 Update docgen.config.js
In `apps/docs/docgen.config.js`, add the component paths to generate props data:
```js
module.exports = {
web: {
// ... other configs
category: {
// e.g., 'buttons', 'layout', etc.
ComponentName: {
source: 'packages/web/src/category/ComponentName.tsx',
},
},
},
// If component has a mobile version
mobile: {
// ... other configs
category: {
ComponentName: {
source: 'packages/mobile/src/category/ComponentName.tsx',
},
},
},
};
```
## Step 5: Create Directory Structure (for new docs only)
Create the documentation directory and files based on component availability:
```bash
apps/docs/docs/components/[docs-category]/[ComponentName]/
├── index.mdx # Required for all components
├── webMetadata.json # If web version exists
├── _webExamples.mdx # If web version exists
├── _webPropsTable.mdx # If web version exists
├── _webStyles.mdx # If web version has styles/classNames API
├── mobileMetadata.json # If mobile version exists
├── _mobileExamples.mdx # If mobile version exists
├── _mobilePropsTable.mdx # If mobile version exists
└── _mobileStyles.mdx # If mobile version has styles/classNames API
```
## File Templates
### Metadata Files
#### webMetadata.json
```json
{
"import": "import { ComponentName } from '@coinbase/cds-web/[source-category]/[ComponentName]'",
"source": "https://github.com/coinbExcerpt, first 6,000 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 Components.Write Docs
What does the Components.Write Docs skill do?
Is Components.Write Docs safe to install?
What can Components.Write Docs access on my machine?
How current is this page?
Sources
- github.com/coinbase/cds/tree/master/.claude/skills/components.wr — 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 Components.Write Docs skill do?
- Is Components.Write Docs safe to install?
- What can Components.Write Docs access on my machine?