extension-build

Automate the extension materials pipeline to publish NotebookLM assets to CreatorHub.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/elliot200852-lab/waldorf-teacher-os --skill extension-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extension-build
Source: https://github.com/elliot200852-lab/waldorf-teacher-os/tree/main/.claude/skills/extension-build
Command: npx skills add https://github.com/elliot200852-lab/waldorf-teacher-os --skill extension-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end extension materials pipeline, enabling teachers to publish NotebookLM-derived assets (infographics, slides, teaching reflections, and videos) to CreatorHub when a main course closes.

Core Features & Use Cases

  • Automates the orchestration of four asset types (infographics, slides, teaching reflections, videos) from production to publishing on CreatorHub.
  • Triggers on course closure and user utterances such as "extension build" to kick off the deployment process, enabling hands-off publishing.
  • Integrates with the existing master workflow and CLI tooling to run the pipeline from the repository root and stay in sync with the original specification.

Quick Start

Run the extension-build pipeline from the repository root using the provided master CLI.

Frequently Asked Questions about extension-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate publishing NotebookLM teaching materials to CreatorHub?

You can automate the extension materials pipeline by running the bin/ext-pipeline CLI tool from the repository root to publish NotebookLM-derived assets directly to CreatorHub channel pages.

What is the best way to publish infographics, slides, and videos when a course closes?

The extension build process orchestrates these four asset types automatically upon course closure, triggering the deployment pipeline to publish the generated teaching materials to CreatorHub without manual intervention.

Can I use the extension-build pipeline with my existing master workflow?

Yes, the pipeline integrates with your existing master workflow and CLI tooling, executing from the repository root to stay aligned with the original plan-based specification for asset publication.

Do I need a specific CLI tool to trigger the extension materials deployment?

Yes, you need to run the provided master CLI tool bin/ext-pipeline from the repository root to execute the end-to-end pipeline for publishing educational assets to CreatorHub.

How does the extension build trigger work for automating course material publication?

The deployment process triggers automatically on course closure or when a user utters 'extension build,' initiating the hands-off publishing of teaching reflections, slides, infographics, and videos to CreatorHub.

Are there limitations to automating NotebookLM asset publishing with this pipeline?

The pipeline is specifically designed for educators generating four predefined asset types and requires execution via the CLI tool from the repository root, aligning strictly with the original plan-based workflow.