insightflo/edu-deck-skills / edu-deck
edu-deck
FlaggedEntry skill for education deck requests. Use FIRST when the user wants 교육자료, 강의 자료, 교육용 슬라이드, 직원 교육 덱, or a training series (예: "○○ 교육자료 만들어줘", "사내 교육 시리즈 만들어", "여러 편으로 나눠 교육 자료"). 판별 후 단일 발행(주제 하나, 파일 하나)이면 edu-deck-solo 경로를, 여러 편 시리즈·진도 관리·허브가 필요하면 edu-deck-series 경로를 탄다. 애매하면 사용자에게 한 번 묻는다. 덱 제작 절차는 이 스킬에 없고 각 하위 스킬에 있다.
shared/assets/packs/briefing/template.html
View on GitHub<section class="slide pack pack-briefing" data-design="briefing" data-archetype="compare-table">
<header class="briefing-header"><span class="pack-mark">BRIEFING / 판단을 위한 자료</span><p class="pack-topic">{{TITLE}}</p></header>
<!-- t2 2톤 문법: 핵심 어절(주로 마지막 어절, 문장당 1회·1~2 어절)을 <em class="t2">…</em>로 감싸면 강조색이 붙는다. flows.json 토큰 값엔 태그를 넣지 않는다(이스케이프됨). 규칙: references/expression.md 1절 -->
<div class="briefing-thesis"><p class="pack-kicker">{{KICKER}}</p><h1 class="pack-prompt">{{PROMPT}}</h1></div>
<dl class="briefing-ledger">
<div class="briefing-row"><dt><span class="pack-index">01</span>핵심 내용</dt><dd class="pack-body">{{BODY}}</dd><dd class="briefing-readout">무엇을<br>알아야 하는가</dd></div>
<div class="briefing-row"><dt><span class="pack-index">02</span>판단 근거</dt><dd class="pack-evidence">{{EVIDENCE}}</dd><dd class="briefing-readout">무엇으로<br>확인할 것인가</dd></div>
<div class="briefing-row briefing-decision"><dt><span class="pack-index">03</span>다음 행동</dt><dd class="pack-action">{{ACTION}}</dd><dd class="briefing-readout">무엇을<br>할 것인가</dd></div>
</dl>
<footer class="pack-footer briefing-footnote"><span>자료 → 해석 → 행동</span><p>수치가 있다면 단위 · 기간 · 비교 기준을 함께 확인하세요.</p></footer>
<aside class="notes">{{KICKER}}
핵심 내용과 그 근거를 구분해 읽으세요. 수치가 포함되면 단위, 측정 기간, 비교 대상을 확인하고 없는 값을 임의로 채우지 마세요.
{{BODY}}
확인할 근거: {{EVIDENCE}}
학습 활동: {{ACTION}}</aside>
</section>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |