multiAI Summary Pending

chapter-analyzer

Validates and analyzes Docusaurus MDX chapters for structure, pedagogical quality, and component usage.

231 stars

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/chapter-analyzer/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/abdulsamad94/chapter-analyzer/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/chapter-analyzer/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How chapter-analyzer Compares

Feature / Agent	chapter-analyzer	Standard Approach
Platform Support	multi	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.

Which AI agents support this skill?

This skill is compatible with multi.

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.