pswritepdf-retirement
Skill713 starsChanged yesterdayMITView on GitHub
Use when retiring PSWritePDF behavior into OfficeIMO and PSWriteOffice, comparing PDF gaps, or deciding where PowerShell-facing PDF features should live. Keep reusable PDF behavior in OfficeIMO and PSWriteOffice cmdlets thin and friendly.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- officeimo-build-releaseSkill
- officeimo-conversion-operatorSkill
- officeimo-studio-translationsSkill
- officeimo-website-wasmSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for PSWritePDF retirement and PSWriteOffice PDF surface work.
- Very specific: line 12
Read Docs/ROADMAP.md, OfficeIMO.Pdf/README.md, and Docs/officeimo.pdf.current-state.md for open work and current PDF contracts.
- Very specific: line 15
Put PDF generation, parsing, metadata, conversion, and rendering behavior in OfficeIMO or the shared PDF engine.
- Distinctive: line 16
Keep PSWriteOffice as a friendly command surface.
- Distinctive: line 19
Avoid cmdlet-specific forks of conversion or PDF logic.
≈ “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
PSWritePDF Retirement
Use this skill for PSWritePDF retirement and PSWriteOffice PDF surface work.
Golden Path
- Read
Docs/ROADMAP.md,OfficeIMO.Pdf/README.md, andDocs/officeimo.pdf.current-state.mdfor open work and current PDF contracts. - Inventory the OfficeIMO reusable capability before adding PowerShell code.
- Put PDF generation, parsing, metadata, conversion, and rendering behavior in OfficeIMO or the shared PDF engine.
- Keep PSWriteOffice as a friendly command surface.
- Parameters should map to reusable options.
- Presets and themes are welcome when they hide complexity without hiding behavior.
- Avoid cmdlet-specific forks of conversion or PDF logic.
- Validate both developer-source and package-style usage when a change crosses repo boundaries.
Questions To Answer Before Coding
- Is this a core PDF capability, a conversion adapter, or a PowerShell UX feature?
- Does OfficeIMO already have the right byte or stream API?
- Will Blazor WebAssembly need this behavior too?
- Is the downstream PSWriteOffice package using local project references, a packed artifact, or a published NuGet version?
Useful Checks
dotnet build OfficeIMO.Word.Pdf\OfficeIMO.Word.Pdf.csproj -c Release -f net10.0
dotnet test OfficeIMO.Pdf.Tests\OfficeIMO.Pdf.Tests.csproj -c Release --filter "*Pdf*"For PSWriteOffice changes, also validate import and command discovery from the target PSWriteOffice worktree.
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.

