Use this skill when reviewing programming course content for quality, accuracy, and effectiveness. Provides comprehensive review frameworks, checklists, and evaluation criteria for code correctness, pedagogical quality, consistency, and completeness. Trigger phrases include "review course", "check content", "evaluate quality", "find errors", "improve course", "consistency check".
/plugin marketplace add NathanJGaul/plugins/plugin install dev-course-builder@njg-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Comprehensive frameworks and checklists for reviewing programming educational content.
Use these severity levels to prioritize findings:
Issues that make content incorrect, misleading, or harmful to learning:
Issues that significantly impact quality or learning effectiveness:
Issues that affect polish but not correctness or core learning:
Opportunities to improve beyond current quality:
Learning Objectives Analysis
Prerequisite Analysis
Topic Sequencing
Scope Assessment
Terminology Audit
Code Style Audit
Structural Audit
Cross-Reference Audit
Code Verification Protocol
Explanation Quality Assessment
Exercise Evaluation
Assessment Alignment Check
# Course Review Report: [Course Name]
**Reviewer:** [Name]
**Date:** [Date]
**Scope:** [What was reviewed]
**Focus Areas:** [Specific focus if any]
## Executive Summary
### Overall Assessment
[2-3 sentence summary of course quality]
### Key Strengths
1. [Strength 1]
2. [Strength 2]
3. [Strength 3]
### Priority Action Items
1. [Critical item 1]
2. [Critical item 2]
3. [Critical item 3]
## Detailed Findings
### Critical Issues
| ID | Location | Issue | Recommendation |
|----|----------|-------|----------------|
| C1 | [file:line] | [description] | [fix] |
### Major Issues
| ID | Location | Issue | Recommendation |
|----|----------|-------|----------------|
| M1 | [file:line] | [description] | [fix] |
### Minor Issues
| ID | Location | Issue | Recommendation |
|----|----------|-------|----------------|
| m1 | [file:line] | [description] | [fix] |
### Enhancement Opportunities
| ID | Location | Suggestion | Benefit |
|----|----------|------------|---------|
| E1 | [area] | [suggestion] | [benefit] |
## Category Assessments
### Code Correctness: [Score/5]
[Summary and key findings]
### Technical Accuracy: [Score/5]
[Summary and key findings]
### Pedagogical Quality: [Score/5]
[Summary and key findings]
### Completeness: [Score/5]
[Summary and key findings]
### Consistency: [Score/5]
[Summary and key findings]
### Structure: [Score/5]
[Summary and key findings]
## Recommendations
### Immediate Actions (Critical)
1. [Action with specific steps]
2. [Action with specific steps]
### Short-Term Improvements (Major)
1. [Improvement with approach]
2. [Improvement with approach]
### Long-Term Enhancements
1. [Enhancement opportunity]
2. [Enhancement opportunity]
## Appendices
### A: Code Verification Results
[Details of code testing]
### B: Terminology Index
[List of terms and usage]
### C: Cross-Reference Map
[Dependency and reference tracking]
Content is publication-ready. No errors, clear explanations, perfect alignment with course standards, exemplary pedagogy.
Minor issues only. Solid content that needs light polishing. Achieves learning objectives effectively.
Some notable issues but fundamentally sound. Needs revision but not rewrite. Learning objectives achievable with effort.
Significant issues affecting learning outcomes. Major revision required. Core content may be salvageable.
Fundamental problems throughout. Likely requires rewrite. Not suitable for learners in current state.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.