mcpbeat Sign in

Codeck Export Agent Skill

| Internal publisher module for /codeck. Exports deck to PDF or PPTX with post-export QA. User-facing export requests should enter through /codeck; this skill defines the export behavior.

1.8k tokens
context cost
SKILL.md, read when the skill is used
70
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
206
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/hiyeshu/codeck --skill codeck-export

The instruction itself

13 sections, as written by the author

<!--

[INPUT]: Depends on latest assembled HTML, MEMORY.md, tasks/tasks.md, and threads/threads.md.

[OUTPUT]: Provides PDF/PPTX exports and export QA notes.

[POS]: skills/codeck-export lane; publishes the reviewed deck from room state to final artifacts.

[PROTOCOL]: 变更时更新此头部,然后检查 CLAUDE.md

-->

codeck export — @export lane

Minimum conversation, maximum output. Export the deck to the user's format.

@export owns PDF/PPTX output and export QA.

Write boundaries:

  • May write final PDF/PPTX files in the user's project directory
  • May write export QA notes to $DECK_DIR/review.md or $DECK_DIR/MEMORY.md
  • May update $DECK_DIR/roles/export.md, $DECK_DIR/tasks/tasks.md, and $DECK_DIR/channel/YYYY-MM-DD.md
  • Must not edit deck.md, DESIGN.md, custom.css, slides.html, or speech.md
  • Export defects that require source changes become proposals in $DECK_DIR/threads/threads.md

Step 1: Status

DECK_DIR="$HOME/.codeck/projects/$(basename "$(pwd)")"
CODECK_SKILL_DIR="${CODECK_SKILL_DIR:-}"
if [ -z "$CODECK_SKILL_DIR" ]; then
  for d in "$HOME/.agents/skills/codeck" "$HOME/.codex/skills/codeck" "$HOME/.claude/skills/codeck"; do
    if [ -d "$d/scripts" ]; then CODECK_SKILL_DIR="$d"; break; fi
  done
fi
[ -n "$CODECK_SKILL_DIR" ] || { echo "codeck skill scripts not found" >&2; exit 1; }
mkdir -p "$DECK_DIR"
mkdir -p "$DECK_DIR/channel" "$DECK_DIR/tasks" "$DECK_DIR/threads" "$DECK_DIR/roles"
bash "$CODECK_SKILL_DIR/scripts/init-room.sh" "$DECK_DIR"
bash "$CODECK_SKILL_DIR/scripts/status.sh" "$DECK_DIR"

Read $DECK_DIR/MEMORY.md, active rows in $DECK_DIR/tasks/tasks.md, and open rows in $DECK_DIR/threads/threads.md. Do not read channel/YYYY-MM-DD.md unless debugging history.

Gate check: if no assembled HTML exists (./*-r*.html), run /codeck to generate/rebuild the deck first.

Before export, claim the work ticket:

@orchestrator
Owner: @export. Task: export latest HTML and run export QA.

@export
I claim the export pass. I will write PDF/PPTX outputs and record any source defects as threads.

Append the exchange to today's channel file and update tasks/tasks.md.

Step 2: Format

Export Format is one allowed Decision Ask moment under /codeck.

Use the shared /codeck Decision Ask Policy. Skip Decision Ask when the user names a target:

  • PDF, print, save as PDF → export PDF
  • PPTX, PowerPoint, slides file → export PPTX
  • all, both → export PDF and PPTX

If the user only says "export", create a non-blocking D-YYYYMMDD-NN decision in threads/threads.md and render once:

codeck needs the export format.

Current read: HTML already exists as the audience preview.

I suggest PDF because it preserves the visual layout and is easiest to share.

A) PDF (recommended)
B) PPTX
C) PDF + PPTX

If the user does not answer or structured AskUser UI is unavailable, export PDF and write assumed default to MEMORY.md.

Do not offer HTML as an export choice. HTML is the preview/source artifact.

Step 3: Export

Find the HTML file (./*-r*.html in the user's project directory), derive baseName.

HTML

Already exists. Open in browser, F for fullscreen, arrows to navigate.

PDF — print from HTML

Use Playwright for WYSIWYG PDF:

npx playwright install chromium 2>/dev/null || true
import { chromium } from 'playwright';
import { resolve } from 'path';
import { readdirSync } from 'fs';
import { pathToFileURL } from 'url';

const html = readdirSync('.').find(f => /-r\d+\.html$/.test(f));
const baseName = html.replace('.html', '');
const browser = await chromium.launch();
const page = await browser.newPage();
await page.goto(pathToFileURL(resolve(html)).toString(), { waitUntil: 'networkidle' });
await page.emulateMedia({ media: 'screen' });
await page.pdf({
  path: `${baseName}.pdf`,
  printBackground: true,
  preferCSSPageSize: true,
  margin: { top: '12mm', right: '12mm', bottom: '12mm', left: '12mm' }
});
await browser.close();
console.log(`done: ${baseName}.pdf`);

Poster assets

.media-poster elements in slides.html are video/audio placeholders. Original file paths are in the caption and deck.md asset manifest.

Default: keep placeholders in export. If user says "embed video", extract path from caption, use slide.addMedia({ path: "..." }) for PPTX.

PPTX — from HTML

Option A (recommended): LibreOffice

CODECK_EXPORT_DIR="${CODECK_EXPORT_DIR:-}"
if [ -z "$CODECK_EXPORT_DIR" ]; then
  for d in "$HOME/.agents/skills/codeck-export" "$HOME/.codex/skills/codeck-export" "$HOME/.claude/skills/codeck-export"; do
    if [ -d "$d/pptx/scripts" ]; then CODECK_EXPORT_DIR="$d"; break; fi
  done
fi
[ -n "$CODECK_EXPORT_DIR" ] || { echo "codeck-export scripts not found" >&2; exit 1; }
EXPORT_SCRIPTS="$CODECK_EXPORT_DIR/pptx/scripts"
python "$EXPORT_SCRIPTS/office/soffice.py" --headless --convert-to pdf ./*-r*.html
python "$EXPORT_SCRIPTS/office/soffice.py" --headless --convert-to pptx ./*-r*.html

Option B (fallback): screenshot embed

If soffice unavailable, use Playwright to screenshot each page, then PptxGenJS to embed screenshots as slides. Read $CODECK_EXPORT_DIR/pptx/pptxgenjs.md for the API.

Step 4: QA (required for PDF/PPTX)

Assume the export has problems. Find them.

PDF

Check: pages complete (no truncation), backgrounds render, fonts display correctly.

PPTX

Generate thumbnails:

CODECK_EXPORT_DIR="${CODECK_EXPORT_DIR:-}"
if [ -z "$CODECK_EXPORT_DIR" ]; then
  for d in "$HOME/.agents/skills/codeck-export" "$HOME/.codex/skills/codeck-export" "$HOME/.claude/skills/codeck-export"; do
    if [ -d "$d/pptx/scripts" ]; then CODECK_EXPORT_DIR="$d"; break; fi
  done
fi
[ -n "$CODECK_EXPORT_DIR" ] || { echo "codeck-export scripts not found" >&2; exit 1; }
EXPORT_SCRIPTS="$CODECK_EXPORT_DIR/pptx/scripts"
python "$EXPORT_SCRIPTS/thumbnail.py" ./*-r*.pptx

Convert to images for detailed check:

python "$EXPORT_SCRIPTS/office/soffice.py" --headless --convert-to pdf ./*-r*.pptx
pdftoppm -jpeg -r 150 *.pdf slide-check

Use subagent to visually inspect screenshots. Focus on: overlapping elements, text overflow, uneven spacing, low-contrast text, differences from HTML original.

Fix loop

  • Find issue → adjust export params or HTML
  • Re-export → re-screenshot → re-check
  • Until one full check finds no new issues

At least one fix-verify cycle before declaring done.

If QA finds a source defect, do not edit source files directly. Add a thread with the affected artifact and suggested owner, then hand off to @design or @review.

After export:

  • Update MEMORY.md Active Context, Latest Channel Summary, Task Index, and Artifacts.
  • Mark the @export task done in tasks/tasks.md.
  • Append the handoff to today's channel file.

Step 5: Done

> Export done. Output: {baseName}.pdf / {baseName}.pptx

>

> @export

> I exported the latest HTML, ran QA, and recorded output paths in memory.

>

> Speech script: /codeck speech script. Overview: /codeck.

Other skills for the same job

different authors, same section of the catalogue
DOCX
by anthropics
vendor ×18

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

2.5k tokens
PDF
by anthropics
vendor ×18

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

1.8k tokens scripts
PPTX
by JayZeeDesign
×17

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

6.4k tokens scripts
Canvas Design
by anthropics
vendor ×16

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

3k tokens
PDF
by anthropics
vendor ×12

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

2k tokens scripts
DOCX
by w95
×6

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

5k tokens
Obsidian Markdown
by ZhanlinCui
×5

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

2.7k tokens
Obsidian Bases
by ZhanlinCui
×4

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

4.1k tokens

How to use it

Copy the folder

Take hiyeshu/codeck-export from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npx. Without those the skill loads but fails at the first command.