MilkClouds

Build fully editable PowerPoint (.pptx) decks from code: native textboxes, shapes, tables, charts, and real PowerPoint equations (LaTeX→OMML), so the result stays editable in PowerPoint instead of being flat images. Use this whenever the user wants to make, generate, build, or rebuild a slide deck, presentation, or .pptx, including turning notes, a paper, a markdown outline, or an HTML deck into slides, adding editable equations to slides, or producing a deck programmatically, even if they don't say "pptx" explicitly. Prefer it over exporting images or hand-placing text boxes. Triggers on "make/build slides", "presentation", "slide deck", "pptx", "editable slides", "PowerPoint equations", "turn this into slides".

Synchronizes commits between two git remotes with unrelated histories via cherry-pick, preserving original authorship and committer metadata. Use when the user asks to sync repos, bring upstream changes, push to public, cherry-pick between remotes, or mentions syncing a fork. Also triggers on "sync from upstream", "push changes to public", "bring in latest changes", "pull from public repo", or any mention of keeping two repositories in sync.

Generate accurate BibTeX entries from authoritative sources (DBLP, ACL Anthology, PMLR, CrossRef, arXiv). Use this skill whenever the user needs a citation, BibTeX entry, bibliography fix, or wants to look up where/whether a paper was published — even if they don't explicitly say "BibTeX." Triggers on: paper titles, arXiv IDs, DOIs, DBLP keys, "cite this paper", "add to references", reference list verification, or any academic citation task.

Report an agent's progress to a researcher's live dashboard using the adash tool (adash report, adash serve). Use this skill whenever a worker or user wants to log or report a finished step, checkpoint, or status to a dashboard someone is monitoring, tell or notify or update whoever is watching the session, or start or run or view the agent dashboard server. Trigger even when the request only mentions a dashboard, reporting progress, or letting the researcher know, and even when it never says adash by name. Do not trigger for building data-visualization or monitoring dashboards such as React, Grafana, or sales charts, for writing a status-report document, for adding a status column, or for reporting a software bug.