Translate a Beamer `.tex` lecture to a Quarto RevealJS `.qmd` mirror. Multi-phase: TikZ extraction → slide-by-slide translation → citation conversion → automatic QA parity check. Use when user says "translate to quarto", "port to revealjs", "make an html version", "convert this beamer to quarto", "mirror this lecture in qmd", or after a Beamer deck is ready for web publication. Output lands in `Quarto/`.
npx skills add https://github.com/pedrohcgs/claude-code-my-workflow --skill translate-to-quarto
Full translation of a Beamer LaTeX lecture to Quarto RevealJS HTML slides.
CRITICAL: The Beamer .tex file is the SINGLE SOURCE OF TRUTH.
Scan Beamer for all custom environments. Verify CSS equivalents exist in your theme SCSS. If any are missing, create them FIRST.
Run /extract-tikz to verify SVGs match current Beamer source.
List all RDS files needed for interactive charts.
Extract all citations from Beamer, map to bibliography keys.
beamer-translator agentReference extracted SVGs with 0-based indexing.
Interactive plotly from RDS data, static SVG for TikZ/complex figures.
Render, count slides, go through EVERY slide checking for issues.
Run pedagogy-reviewer before visual polish.
Semantic colors, transition slides, framing sentences.
Run /proofread on the QMD file.
Render, open in browser, verify all elements.
Apply any corrections back to Beamer source.
Update CLAUDE.md, session log, create PR.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take pedrohcgs/translate-to-quarto from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.