conference-report
FeaturedUse when the user attended one or more sessions of a conference (with audio recordings + slide photos) and needs help building (1) faithful per-session reconstructions in markdown (slide visuals + speaker transcript with Whisper hallucination annotations), and (2) a downstream report deliverable whose scope and format are decided interactively with the user. Pipeline phase (raw → mlx_whisper Chinese SRT → per-slide multimodal reconstruction → official agenda cross-check via Playwright if available) is deterministic. Report phase is interactive — always quiz user on scope (single-session / single-day / multi-day synthesis), format (existing template / free-form fallback), recipient (formal / informal), and any business workstream mapping before drafting.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- KerberosClaw
- Repository
- KerberosClaw/kc_ai_skills
- Created
- 6 months ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
meeting-audio-report
Transcribe a meeting recording and write a report from it. Use when the user has an audio or video file of a meeting, webinar, seminar, or Q&A session — .m4a/.mp3/.wav/.mp4/.mov — and wants a transcript, meeting notes, minutes, or a written report; also on 转录, 会议纪要, 会议记录, 会议报告, transcribe this, write up this meeting.
progress-report
Produce a readable, non-verbose progress report (Markdown by default, .docx on request) of what an orchestrated or long-running session has done since the LAST report — never overlapping a previous one — with what worked, what didn't, concerns, decisions made on the user's behalf, and manual steps for the user. Use when the user asks for "an update doc", "what's been done", "make a report", or "write up progress".
session-report
Generate an explorable HTML report of Claude Code session usage (tokens, cache, subagents, skills, expensive prompts) from ~/.claude/projects transcripts.