react-component-documentation
Create or update component documentation in Sentry's MDX stories format. Use when asked to "document a component", "add stories", "write component docs", "create an mdx file", "add a stories.mdx", or document a design system component. Generates structured MDX with live demos, accessibility guidance, and auto-generated API docs from TypeScript types.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 an excellent skill description that hits all the marks. It provides specific capabilities (structured MDX, live demos, accessibility guidance, auto-generated API docs), includes a comprehensive 'Use when...' clause with natural trigger terms developers would actually say, and is clearly scoped to Sentry's MDX stories format, making it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create/update component documentation, generate structured MDX with live demos, accessibility guidance, and auto-generated API docs from TypeScript types. | 3 / 3 |
Completeness | Clearly answers both 'what' (create/update component documentation in MDX stories format with live demos, accessibility guidance, and API docs) and 'when' (explicit 'Use when...' clause with multiple trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'document a component', 'add stories', 'write component docs', 'create an mdx file', 'add a stories.mdx', 'design system component'. These are realistic phrases developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Sentry's MDX stories format, design system component documentation, and TypeScript-based API doc generation. Unlikely to conflict with generic documentation or coding 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 strong, highly actionable skill that provides clear step-by-step guidance for creating MDX component documentation in Sentry's design system. Its greatest strengths are the concrete examples, complete templates, and thoughtful editorial guidance (Step 0's prop triage and editorial questions). The main weakness is its length — at ~250 lines it's dense for a single file, and some reference tables could be extracted, though the content itself is well-organized and mostly earns its place.
Suggestions
Consider extracting the category table, prop triage table, and demo layout helpers into a separate reference file to reduce the main SKILL.md length and improve progressive disclosure.
Tighten the Step 0 editorial content section — the two large tables could be condensed into a shorter checklist format since Claude can infer the mapping between questions and MDX sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is thorough but includes some content Claude could infer (e.g., the category table mapping components to categories, explaining what sub-components are). The prop triage table and editorial questions table add value but could be more compact. Some sections like the import order comments are helpful but slightly verbose. | 2 / 3 |
Actionability | Highly actionable with concrete file paths, exact import syntax, complete MDX examples, specific frontmatter YAML templates, and a full end-to-end Alert example. Every step provides copy-paste ready patterns with real component names and actual project conventions. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced from Step 0 (gather editorial content) through Step 5 (props table), with a final checklist serving as a validation checkpoint. The step numbering, decision points (e.g., product vs scraps components, prop triage tiers), and the comprehensive checklist at the end provide clear guidance and verification. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and logical sections, but it's a long monolithic file (~250 lines) with no references to external files for detailed content like the complete example or the accessibility patterns. The category table, prop triage table, and demo layout helpers table could potentially be split into reference files, though no bundle files exist to support this. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- getsentry/sentry
- Commit
552fb5c
- 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.