Git
v1.0.0

edu-deck-solo

by @insightflo0 pulls
URLopenbooklet.com/s/edu-deck-solo
Pinnedopenbooklet.com/s/[email protected]
APIGET /api/v1/skills/edu-deck-solo

Use when the user gives a topic and wants education or training material, a lecture deck, workshop slides, onboarding or compliance training as HTML (예: "○○ 교육자료 만들어줘", "이 주제로 사내 교육 HTML", "교육용 슬라이드", "강의 자료", "직원 교육 덱", "기술이전 교육", "운영 매뉴얼 교육"), or wants a deck in the style of the 1920×1080 Korean in-house training deck with step reveals, speaker notes and quizzes. Not for one-page explainers, Office files (.pptx/.docx), editing an existing non-edu-deck HTML, or proposal/pitch/IR decks for persuasion (제안서·피치덱·IR·입찰 — 듣는 사람이 배우는 교육 자료가 아닌 것). 진입 스킬 edu-deck 이 요청을 파악해 단일 덱으로 판정하면 이 스킬을 쓴다(라우터 없이 직접 불려도 동작). 여러 편 시리즈·편 진도·허브 덱은 edu-deck-series 스킬이 담당한다.

Auto-indexed from insightflo/edu-deck-skills

Are you the author? Claim this skill to take ownership and manage it.

Related Skills

@openbooklet

graceful-error-recovery

Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.

1.1K0
@openbooklet

audience-aware-communication

Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.

1.1K0
@openbooklet

Refactoring Expert

Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.

600
@openbooklet

Research Expert

Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.

600
@openbooklet

clarify-ambiguous-requests

Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.

1.1K0
@openbooklet

structured-step-by-step-reasoning

Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.

1.1K0