igorwarzocha/opencode-workflows
2 skills4.4k installs248 starsGitHub
Install
npx skills add https://github.com/igorwarzocha/opencode-workflowsSkills in this repo
1Powerpointpowerpoint is a workflow-oriented agent skill for solo builders who need real .pptx files—not screenshots—for board meetings, investor updates, and internal status reviews. It splits creation into a high-fidelity HTML pipeline (fixed slide dimensions, Sharp-rasterized visuals, html2pptx execution per references/html2pptx.md) and a template editing pipeline (thumbnail.py layout audit, rearrange.py slide order, replace.py content from JSON inventory). Agents are steered toward design-quality guardrails: web-safe fonts, valid hex handling for PptxGenJS, and structured HTML text tags. Prism catalogs it under Build → docs as the canonical shelf, with multi-phase scope because the same skill supports validate-stage pitch narrative and grow-stage stakeholder updates. Intermediate complexity: you need Node/script execution and tolerance for multi-step doc generation. It complements generic chat slide outlines by enforcing executable steps and reference docs rather than vague bullet suggestions.3.9kinstalls2WordWord is a multi-phase agent skill that teaches agents how to produce valid Microsoft Word .docx files programmatically with the JavaScript docx package. Solo builders hit this when a client, investor, or compliance workflow expects a real Word deliverable—not a PDF export hack—and the agent must not corrupt the file with newline shortcuts or half-formed table markup. The skill is explicitly a read-first tutorial: setup assumes global or project docx install, then walks through paragraphs, runs, alignment, spacing, tables, media, headers, footers, and advanced pieces like table of contents and footnotes. The formatting guardrails matter as much as the API list; the documented anti-pattern of embedding line breaks in TextRun is a common source of broken documents in agent-generated code. You will use it during build when generating specs or handoff docs, in ship when packaging release notes, or in grow when templating customer-facing materials—any time the output must be a .docx blob or filesystem file from Node or browser code.593installs