chapter-analyzer
Validates and analyzes Docusaurus MDX chapters for structure, pedagogical quality, and component usage.
Best use case
chapter-analyzer is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Validates and analyzes Docusaurus MDX chapters for structure, pedagogical quality, and component usage.
Validates and analyzes Docusaurus MDX chapters for structure, pedagogical quality, and component usage.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "chapter-analyzer" skill to help with this workflow task. Context: Validates and analyzes Docusaurus MDX chapters for structure, pedagogical quality, and component usage.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/chapter-analyzer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How chapter-analyzer Compares
| Feature / Agent | chapter-analyzer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validates and analyzes Docusaurus MDX chapters for structure, pedagogical quality, and component usage.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Chapter Analyzer Logic
## Target Directory
- **Location**: `textbook/docs/`
- **Format**: MDX (`.mdx` or `.md`)
## Structural Validation
Every chapter must have valid YAML frontmatter:
```yaml
---
id: my-chapter-id
title: My Chapter Title
sidebar_label: Sidebar Label
description: Brief summary of the chapter.
---
```
## Content Rules
1. **Heading Hierarchy**:
- The Docusaurus title acts as H1.
- Start content with H2 (`##`).
- Do not use H1 (`#`) within the body.
2. **Pedagogical Flow**:
- **Introduction**: Hook the reader.
- **Learning Objectives**: Bullet points on what will be learned.
- **Core Content**: Explained with text + diagrams/code.
- **Interactive Element**: At least one Quiz or Simulation per major section.
- **Summary**: Recap key points.
## Interactive Components
We use custom components in MDX:
- `<Quiz questions={[...]} />`: For knowledge checks.
- `<Simulation type="ros2-node" ... />`: For embedded simulations.
- `<Tabs>` / `<TabItem>`: For multi-language code blocks (Python/C++).
## Tone Check
- **Voice**: Encouraging, Authoritative but Accessible.
- **Perspective**: "We will learn", "Let's explore".
- **Clarity**: Avoid jargon without explanation.Related Skills
health-trend-analyzer
分析一段时间内健康数据的趋势和模式。关联药物、症状、生命体征、化验结果和其他健康指标的变化。识别令人担忧的趋势、改善情况，并提供数据驱动的洞察。当用户询问健康趋势、模式、随时间的变化或"我的健康状况有什么变化？"时使用。支持多维度分析（体重/BMI、症状、药物依从性、化验结果、情绪睡眠），相关性分析，变化检测，以及交互式HTML可视化报告（ECharts图表）。
when-optimizing-prompts-use-prompt-optimization-analyzer
Active diagnostic tool for analyzing prompt quality, detecting anti-patterns, identifying token waste, and providing optimization recommendations
when-auditing-security-use-security-analyzer
Comprehensive security auditing across static analysis, dynamic testing, dependency vulnerabilities, secrets detection, and OWASP compliance
when-analyzing-user-intent-use-intent-analyzer
Advanced intent interpretation system using cognitive science principles and probabilistic intent mapping
when-analyzing-skill-gaps-use-skill-gap-analyzer
Analyze skill library to identify coverage gaps, redundant overlaps, optimization opportunities, and provide recommendations for skill portfolio improvement
intent-analyzer
Advanced intent interpretation system that analyzes user requests using cognitive science principles and extrapolates logical volition. Use when user requests are ambiguous, when deeper understanding would improve response quality, or when helping users clarify what they truly need. Applies probabilistic intent mapping, first principles decomposition, and Socratic clarification to transform vague requests into well-understood goals.
naming-analyzer
Suggest better variable, function, and class names based on context and conventions.
log-analyzer
Parse and analyze application logs to identify errors, patterns, and insights.
complexity-analyzer
Measure and report code complexity metrics with actionable recommendations.
auth-analyzer
Review and analyze authentication and authorization patterns for security vulnerabilities.
wp-test-analyzer
Analyze WordPress theme PHP files to extract testable elements for E2E test generation.
test-coverage-analyzer
Analyzes test coverage gaps and suggests test cases for untested code paths. Use when user requests test improvements, coverage analysis, or wants to increase test coverage.