GitHub to Skool Sync

GitHub to Skool Sync is a Chrome extension that bridges your GitHub repository and your Skool community. Write or edit course content in your repo (as Markdown or .skool.html files), then pull it into Skool classroom lessons—or push what you've written in Skool back to GitHub. Automatically sync embedded YouTube videos along with your content. No manual copy-paste, no separate API: the extension runs in your browser and syncs content directly. Key features • Auto-Map All Lessons: Map Skool lessons to GitHub files quickly; fuzzy matching for truncated titles; matches titles to folder names (e.g. "My Lesson" → "My_Lesson/SKOOL.html"); maps most lessons automatically. • Bulk operations: Pull ALL / Push ALL for 100+ lessons in one batch with progress and cancel; large courses in minutes. • Bidirectional sync, smart mapping, branch support, file browser, default folder in Settings. • Compare Skool ↔ GitHub: Check whether the current lesson matches GitHub before Pull or Push—see in sync, out of sync, or missing file without guessing. • Drift indicators: In the file tree, mapped files changed on GitHub since last sync show a ↓ GitHub badge; parent folders show counts and auto-expand so you can spot what needs Pull without clicking Compare on every lesson. • View-only Push: Push from classroom lessons you cannot edit (read-only or no Save button)—useful for locked or view-only content. • GitHub setup: Paste a full repository URL in Settings (https://github.com/owner/repo or owner/repo) and use Test connection to verify token access, including private repos. • Transcripts: When Skool exposes a Transcript field, it is saved in SKOOL_SYNC_META on Push and restored on Pull. • Community feed (HTML): On community home, open Create post and apply a repo .html file into title and body (YAML title and/or SKOOL_SYNC_META; optional video URLs for Add video). Primary authoring is semantic HTML; separate from classroom lesson sync. What it does • Two-way sync: Push content from the current Skool page to a file in your GitHub repo, or pull content from a GitHub file into the Skool editor. • Video syncing: Automatically detect and sync embedded YouTube videos with your content—videos are preserved during push and restored during pull (including placeholder URLs → iframe embeds where supported). Also supports Vimeo, Loom, and native video URLs where detectable. • Page-to-file mapping: Map each Skool classroom lesson (or post) to a specific file path in your repo. Once mapped, one click pushes or pulls that page. • Bulk sync: Use Push ALL or Pull ALL to sync every mapped page in a folder—ideal for whole modules or courses. • Branch support: Choose which branch to read from and write to (default branch or any other). • File browser: Browse your repo in the side panel, pick a file (or type a path), then map the current Skool page to it. Mapped files with GitHub drift are highlighted in the tree. • Default folder: In Settings you can set a default folder in the repo (e.g. course or content). The panel's path starts there when you have no mapping; your choice isn't overwritten when you push or pull. The extension works by injecting content into Skool's editor the same way you'd paste it—so it works with Skool's native rendering (including Markdown). No Skool API key is required. Who it's for • Creators who keep course material in GitHub (version control, collaboration, backups) and publish to Skool. • Anyone who wants to edit in Skool and push changes back to GitHub for history and reuse. • Communities that use a repo as the single source of truth and Skool as the delivery platform. Getting started Install the extension from the Chrome Web Store. Settings: Click the extension icon to open the side panel, then open Settings. Enter: GitHub Token: A Personal Access Token from GitHub (scope "repo" for private repos, or "public_repo" for public only). Create one at github.com/settings/tokens. GitHub repository URL: e.g. https://github.com/yourname/your-course-repo (or yourname/your-course-repo). Default folder (optional): e.g. course or leave blank for repo root. This is the starting folder for the path box; it is not overwritten when you sync. Click Test connection before Save to confirm your token can access the repo. Open a Skool page: Go to your Skool community and open the classroom lesson (or post) you want to sync—or stay on community home to draft a feed post from HTML (see below). Side panel: Click the extension icon so the side panel opens. Select the branch, then either browse to a file in the file list or type the file path (e.g. course/intro/welcome.skool.html). Map (classroom): Click "Map Page to Content" to save the link between this Skool page and that file. The panel will show the mapping (e.g. "Classroom Lesson → path/to/file.skool.html"). Sync (classroom): Check Skool ↔ GitHub (optional): See if Pull or Push would change anything before you sync. Push to GitHub: Sends the current Skool page content to the mapped file (creates or updates the file in the repo). Works on view-only lessons too. Pull from GitHub: Fetches the mapped file from GitHub and injects it into the Skool editor. For a whole folder of lessons, enter a folder path (no file extension) in the path box. Push ALL pushes all mapped pages in that folder from Skool to GitHub; Pull ALL pulls all of them from GitHub into Skool. Community post draft (HTML): On community home, open "Write something". Enter a path to a .html file in the side panel and use "Apply selected file → post" (or the floating Community pull control). Pick category and Post in Skool. Does not use lesson mappings. File format • .skool.html / .html: HTML fragments or full snippets that Skool can render. The extension can create or update these when you push. Community apply uses semantic .html (optional YAML or SKOOL_SYNC_META for title, video URLs, and transcript). • Markdown (.md): Pulling a .md file injects the raw Markdown into th…