officeimo-conversion-operator
Skill713 starsChanged yesterdayMITView on GitHub
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.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- officeimo-build-releaseSkill
- officeimo-studio-translationsSkill
- officeimo-website-wasmSkill
- pswritepdf-retirementSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill for OfficeIMO conversion work across Word, Excel, PowerPoint, Markdown, HTML, and PDF.
- Distinctive: line 12
Start by locating the owning reusable API.
- Distinctive: line 17
Treat file paths as adapter concerns.
- Distinctive: line 18
Prefer byte array and stream entrypoints for conversion APIs.
- Distinctive: line 19
Keep browser, CLI, PowerShell, MCP, and website shells as orchestration only.
- Distinctive: line 27
Keep public surfaces friendly.
- Very specific: line 28
Add simple options and presets at host layers only after the reusable OfficeIMO API already supports the behavior.
- Distinctive: line 29
Avoid hidden environment-variable switches for behavior that should be an explicit option.
- Very specific: line 40
When the work targets GitHub Pages or OfficeIMO.com, pair these with the browser conversion proof described in …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
- Word behavior belongs under
- 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.
- For PDF output, at minimum verify the returned bytes start with
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

