LeoYeAI/agent-master-skills / skills/ai-shifu-course-creator
ai-shifu-course-creator
VerifiedConvert raw course material into optimized, runnable MarkdownFlow teaching scripts and deploy them as live courses through a five-phase pipeline covering segmentation, orchestration, generation, optimization, and deployment.
references/report-template.md
View on GitHub# Course Author Report Template
Use the section matching the executed phase. Omit sections for phases not run.
## Phase 1: Segmentation Report
- Source files:
- Processing mode: `standard|fallback`
- Total segments:
- Lesson candidates:
- Immutable blocks preserved:
Validation:
- Source span traceability: `pass|fail`
- Immutable block preservation: `pass|fail`
- One-core-question lesson check: `pass|fail`
Issues:
- Blocking issues:
- Non-blocking suggestions:
Next actions:
- Targeted reruns:
- Downstream handoff notes:
## Phase 2: Orchestration Report
- Input set:
- Execution mode: `standard|fallback`
- Constraints:
- Lesson files generated:
- Course index status:
- Variable table status:
Gate results:
- Preservation gate: `pass|fail`
- One-core-question gate: `pass|fail`
- Interaction safety gate: `pass|fail`
- Variable safety gate: `pass|fail`
Issues:
- Blocking issues:
- Suggestions:
Rerun plan:
- Lessons to rerun:
- Dependency-linked lessons:
## Phase 3: Generation Report
- Lesson id:
- Execution mode: `standard|fallback`
- Constraints:
- Script generated: `yes|no`
- Interaction count:
- Variables used:
Validation:
- Syntax validity: `pass|fail`
- Variable safety: `pass|fail`
- Visual-text coordination: `pass|fail`
- Teaching loop completeness: `pass|fail`
Issues:
- Blocking issues:
- Suggestions:
Follow-up:
- Rerun needed: `yes|no`
- Upstream dependency notes:
## Phase 4: Optimization Report
- Target script(s):
- Source material set:
- Execution mode: `standard|fallback`
- Overall risk: `low|medium|high`
Issue breakdown:
- Coverage gaps:
- Meaning shifts:
- Interaction issues:
- Visual issues:
- Variable/syntax issues:
Changes applied:
- File references:
- Minimal-edit rationale:
Validation:
- Syntax check: `pass|fail`
- Variable safety check: `pass|fail`
- Interaction branching check: `pass|fail`
- Density preservation check: `pass|fail`
## Phase 5: Deployment Report
- Course directory:
- Platform region: `cn|global`
- Build result: `success|fail`
- Import result: `success|fail`
- Shifu BID:
- Lesson count imported:
- Publish result: `success|fail`
Validation:
- Import without errors: `pass|fail`
- Course accessible via URL: `pass|fail`
- Lesson count matches source: `pass|fail`
- Preview mode reachable: `pass|fail`
Verification URLs:
- Admin console:
- Preview:
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |