agentleFS
EvotecITEvotecIT/OfficeIMO/.agents/skills/officeimo-conversion-operator/SKILL.md

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.

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
  1. Very specific:

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

    line 8
  2. Distinctive:

    Start by locating the owning reusable API.

    line 12
  3. Distinctive:

    Treat file paths as adapter concerns.

    line 17
  4. Distinctive:

    Prefer byte array and stream entrypoints for conversion APIs.

    line 18
  5. Distinctive:

    Keep browser, CLI, PowerShell, MCP, and website shells as orchestration only.

    line 19
  6. Distinctive:

    Keep public surfaces friendly.

    line 27
  7. Very specific:

    Add simple options and presets at host layers only after the reusable OfficeIMO API already supports the behavior.

    line 28
  8. Distinctive:

    Avoid hidden environment-variable switches for behavior that should be an explicit option.

    line 29
  9. Very specific:

    When the work targets GitHub Pages or OfficeIMO.com, pair these with the browser conversion proof described in …

    line 40

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OfficeIMO Conversion Operator

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

Golden Path

  1. 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

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.