Single-source build pipeline for a WSQ course — one content module (course_data.py + data_domainN.py) drives ALL artifacts (the all-white slide deck PPT, the Lesson Plan LP, the Learner Guide LG + its Markdown mirror, and the labs/ index) so they stay 100% aligned. Generic and course-agnostic: it locates the course repo and derives every filename from course_data, so the same engine works for any WSQ course. Use to regenerate courseware after editing course content.
Push the current courseware's Google Drive links into the course record on lms-tms.tertiaryinfotech.com via its API — sets Trainer Slides URL (PPT from Master Trainer Slides), Learner Slides URL (slide PDF from Learner Guide), Learner Guide URL (LG PDF) and Lesson Plan URL (LP PDF). The Drive folder is read from the course's own Courseware Link field via the API. Use when the user runs /lms-push or asks to update/sync the LMS-TMS course links.
Generate a Tertiary Infotech Academy WSQ Learner Guide as BOTH an aligned Markdown file (LEARNER-GUIDE.md) and a professionally formatted Word document (.docx) from a single source so the two never diverge. The DOCX has the WSQ cover page (course title + n8n & Tertiary logos + UEN), Document Version Control Record, auto Table of Contents, Arial 11pt body, embedded workflow screenshots, and a copyright + page-number footer on every page. Use when writing or updating a detailed step-by-step learner guide for a WSQ course.
Generate a Tertiary Infotech Academy WSQ Lesson Plan as a professionally formatted Word document (.docx) with the house cover page (course title + n8n & Tertiary logos + UEN), Document Version Control Record, auto Table of Contents, Arial 11pt body, colour-coded daily schedule tables, and a copyright + page-number footer on every page. Each training day totals exactly 8 instructional hours (9:30am–6:30pm with a 1-hour lunch; tea breaks counted within). Use when creating or updating a lesson plan / training schedule for a WSQ course.
Best-practice design system and rules for building highly professional, visual training/course slide decks with python-pptx (Tertiary Infotech house style). Use whenever creating or polishing a .pptx deck so the result is clean, white-theme, visual, and consistent — large readable fonts, brand colours, icon/card layouts, screenshots and diagrams instead of walls of text. Pair with the tertiary-course-slides skill.
Generate WSQ course assessments as professionally formatted Word documents (.docx) — a Written Assessment (WA) that tests KNOWLEDGE and a practical instrument that tests PRACTICAL ability, each as a question paper PLUS a model-answer / marking guide. Two builders are provided. build_assessment.py produces WA (SAQ) + PP (Practical Performance): the WA is open-ended short-answer knowledge questions drawn from the course slides, and the PP is activity-based practical tasks (LO1..LOn) whose model answers are the in-class lab build steps; both carry the WSQ house COVER PAGE (same as the Lesson Plan / Learner Guide — course title + logos + UEN); assessments have the cover page only (no version-control record). build_wsq_assessment.py is the alternate WA + Case Study (CS) variant. ALL questions are OPEN-ENDED (no multiple choice). Use when creating or revising assessments, written/practical/case-study questions, answer keys, or marking guides for a WSQ course.
Create a WSQ Learner Guide document (.docx) for Tertiary Infotech Academy Pte Ltd in the house template format. Use when building, revamping or standardising a WSQ learner guide. Enforces the cover page, Document Version Control Record, Word Table of Contents field, and a body of topics with detailed step-by-step activities.
Create a WSQ Lesson Plan document (.docx) for Tertiary Infotech Academy Pte Ltd in the house template format. Use when building, revamping or standardising a WSQ lesson plan. Enforces the cover page, Document Version Control Record, Word Table of Contents field, the day schedule table, and the assessment scheduling rules.
Generate or revamp WSQ courseware slide decks for Tertiary Infotech Academy Pte Ltd. Use whenever building, revamping, or standardising a WSQ training PowerPoint (.pptx). Enforces the house standards: copyright line, organisation name + UEN on the front page, two "About the Trainer" variants (a blank General Trainer template and the named trainer) as visual profile cards, the correct admin slide order (Briefing for Assessment before the Assessment slide), a Lesson Plan slide, a mandatory professional visual component system (tile grids, flow diagrams, cards, profile cards — never plain bullet walls), and the assessment admin pages (Assessment, Assessment Flow, Digital Attendance/TRAQOM) repeated at the END of the deck before Thank You.
Single-source build pipeline for a NON-WSQ (C-prefix) course — one content module (course_data.py + data_domainN.py) drives ALL artifacts (the all-white slide deck PPT, the Lesson Plan LP, the Learner Guide LG + its Markdown mirror) so they stay 100% aligned. Excludes all WSQ funding, SSG/SkillsFuture, TRAQOM, digital-attendance and assessment content. Use to build or regenerate courseware for a Tertiary Infotech non-WSQ short course.
Audit NON-WSQ courseware (PPT, LP, LG, labs) for completeness, alignment, visual defects and — critically — any leaked WSQ funding, SSG/SkillsFuture, TRAQOM, digital-attendance or assessment content. Run after every non-WSQ courseware build, before publishing or pushing.
Push a NON-WSQ course's courseware (slide deck PPT + PDF, Learner Guide, Lesson Plan, labs) to the user-supplied Google Drive course folder — auto-creating each folder's archive/ subfolder and moving superseded versions into it, never deleting, then emitting anyone-with-link viewer links. No assessment is ever uploaded.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Used when the user asks to "create slides", "make a presentation", "build a deck", "design slides", "generate a pitch deck", "create a conference talk", "make a keynote", "presentation design", "slide layout", "slide template", "presentation structure", or mentions slides, presentations, decks, or talks in any context. Also triggers when the user wants to plan the content and visual direction of a presentation before generating it. This is the entry-point orchestrator that drives the full slide creation workflow across both HTML and PPTX formats. Examples: "I need to create slides for my conference talk about AI adoption", "can you turn this markdown into a presentation?", "I have a product demo tomorrow and need visual materials", "convert my existing PowerPoint to interactive HTML slides".
Best-practice design system and rules for building highly professional, visual training/course slide decks with python-pptx (Tertiary Infotech house style). Use whenever creating or polishing a .pptx deck so the result is clean, white-theme, visual, and consistent — large readable fonts, brand colours, icon/card layouts, screenshots and diagrams instead of walls of text. Pair with the tertiary-course-slides skill.
Generate or revamp WSQ courseware slide decks for Tertiary Infotech Academy Pte Ltd. Use whenever building, revamping, or standardising a WSQ training PowerPoint (.pptx). Enforces the house standards: copyright line, organisation name + UEN on the front page, two "About the Trainer" variants (a blank General Trainer template and the named trainer) as visual profile cards, the correct admin slide order (Briefing for Assessment before the Assessment slide), a Lesson Plan slide, a mandatory professional visual component system (tile grids, flow diagrams, cards, profile cards — never plain bullet walls), and the assessment admin pages (Assessment, Assessment Flow, Digital Attendance/TRAQOM) repeated at the END of the deck before Thank You.
Single-source build pipeline for a WSQ course — one content module (course_data.py + data_domainN.py) drives ALL artifacts (the all-white slide deck PPT, the Lesson Plan LP, the Learner Guide LG + its Markdown mirror, and the labs/ index) so they stay 100% aligned. Generic and course-agnostic: it locates the course repo and derives every filename from course_data, so the same engine works for any WSQ course. Use to regenerate courseware after editing course content.
Best-practice design system and rules for building highly professional, visual training/course slide decks with python-pptx (Tertiary Infotech house style). Use whenever creating or polishing a .pptx deck so the result is clean, white-theme, visual, and consistent — large readable fonts, brand colours, icon/card layouts, screenshots and diagrams instead of walls of text. Pair with the tertiary-course-slides skill.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
tertiarycoursesSkill