How do I install the Officeimo Conversion Operator skill?

Run npx skillmds@latest add evotecit/officeimo-conversion-operator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Officeimo Conversion Operator safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Officeimo Conversion Operator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Officeimo Conversion Operator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Officeimo Conversion Operator?

evotecit (@evotecit) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Officeimo Conversion Operator by evotecit

Name: Officeimo Conversion Operator
Author: evotecit

Officeimo Conversion Operator

Use when contributing code that changes or validates OfficeIMO conversion behavior, especially DOCX/XLSX/PPTX/HTML/Markdown/PDF byte and stream APIs, browser-safe paths, or fidelity diagnostics. Prefer OfficeIMO core APIs first and keep hosts, websites, cmdlets, MCP tools, and demos thin.

evotecit 6d49162 2 files · 2.7 KB Updated Sep 17, 2026

File contents

OfficeIMO Conversion Operator

Use this skill for OfficeIMO conversion work across Word, Excel, PowerPoint, Markdown, HTML, and PDF.

Golden Path

Start by locating the owning reusable API.
- Word behavior belongs under OfficeIMO.Word*.
- Excel behavior belongs under OfficeIMO.Excel*.
- PowerPoint behavior belongs under OfficeIMO.PowerPoint*.
- Shared PDF behavior belongs in the PDF engine projects, not in a host wrapper.
Treat file paths as adapter concerns.
- Prefer byte array and stream entrypoints for conversion APIs.
- Keep browser, CLI, PowerShell, MCP, and website shells as orchestration only.
Validate real artifacts.
- For PDF output, at minimum verify the returned bytes start with %PDF.
- For browser work, validate inside a real Blazor WebAssembly runtime before calling it GitHub Pages-safe.
- For fidelity work, keep a named fixture and record the expected known gap.
Separate platform limits from conversion defects.
- Browser-safe means no Office automation, LibreOffice process, native graphics dependency, server filesystem dependency, or environment-only state.
- Font coverage, Unicode embedding, large memory use, and startup size are conversion quality gaps even when the browser runtime works.
Keep public surfaces friendly.
- Add simple options and presets at host layers only after the reusable OfficeIMO API already supports the behavior.
- Avoid hidden environment-variable switches for behavior that should be an explicit option.

Useful Checks

dotnet build OfficeIMO.Word.Pdf\OfficeIMO.Word.Pdf.csproj -c Release -f net10.0
dotnet test OfficeIMO.Word.Tests\OfficeIMO.Word.Tests.csproj -c Release --filter "*SaveAsPdf*"
dotnet test OfficeIMO.Html.Tests\OfficeIMO.Html.Tests.csproj -c Release --filter "*Html*"
dotnet test OfficeIMO.Markdown.Tests\OfficeIMO.Markdown.Tests.csproj -c Release --filter "*Markdown*"

When the work targets GitHub Pages or OfficeIMO.com, pair these with the browser conversion proof described in Docs/officeimo.blazor-wasm-conversion-proof.md.

---name: officeimo-conversion-operatordescription: Use when contributing code that changes or validates OfficeIMO conversion behavior, especially DOCX/XLSX/PPTX/HTML/Markdown/PDF byte and stream APIs, browser-safe paths, or fidelity diagnostics. Prefer OfficeIMO core APIs first and keep hosts, websites, cmdlets, MCP tools, and demos thin.---# OfficeIMO Conversion OperatorUse this skill for OfficeIMO conversion work across Word, Excel, PowerPoint, Markdown, HTML, and PDF.## Golden Path1. Start by locating the owning reusable API. - Word behavior belongs under `OfficeIMO.Word*`. - Excel behavior belongs under `OfficeIMO.Excel*`. - PowerPoint behavior belongs under `OfficeIMO.PowerPoint*`. - Shared PDF behavior belongs in the PDF engine projects, not in a host wrapper.2. Treat file paths as adapter concerns. - Prefer byte array and stream entrypoints for conversion APIs. - Keep browser, CLI, PowerShell, MCP, and website shells as orchestration only.3. Validate real artifacts. - For PDF output, at minimum verify the returned bytes start with `%PDF`. - For browser work, validate inside a real Blazor WebAssembly runtime before calling it GitHub Pages-safe. - For fidelity work, keep a named fixture and record the expected known gap.4. Separate platform limits from conversion defects. - Browser-safe means no Office automation, LibreOffice process, native graphics dependency, server filesystem dependency, or environment-only state. - Font coverage, Unicode embedding, large memory use, and startup size are conversion quality gaps even when the browser runtime works.5. Keep public surfaces friendly. - Add simple options and presets at host layers only after the reusable OfficeIMO API already supports the behavior. - Avoid hidden environment-variable switches for behavior that should be an explicit option.## Useful Checks```powershelldotnet build OfficeIMO.Word.Pdf\OfficeIMO.Word.Pdf.csproj -c Release -f net10.0dotnet test OfficeIMO.Word.Tests\OfficeIMO.Word.Tests.csproj -c Release --filter "*SaveAsPdf*"dotnet test OfficeIMO.Html.Tests\OfficeIMO.Html.Tests.csproj -c Release --filter "*Html*"dotnet test OfficeIMO.Markdown.Tests\OfficeIMO.Markdown.Tests.csproj -c Release --filter "*Markdown*"```When the work targets GitHub Pages or OfficeIMO.com, pair these with the browser conversion proof described in `Docs/officeimo.blazor-wasm-conversion-proof.md`.

Frequently asked questions