Where this fits

You're maintaining a PowerShell module that wraps PDF generation, but your library is growing unwieldy—cmdlets duplicate logic, and conversion code is scattered. You've decided to retire PSWritePDF and fold its capabilities into OfficeIMO and PSWriteOffice. The pswritepdf-retirement skill guides you through this migration, ensuring reusable PDF logic lands in the right layer and PowerShell cmdlets stay thin and user-friendly.

Why agents benefit

• Structured retirement path: The skill points to a gap analysis document and gives a golden path, so your agent doesn't improvise the migration order.
• Layered architecture decisions: It forces the agent to ask whether a feature is core PDF capability, a conversion adapter, or a PowerShell UX feature—preventing cmdlet-specific forks.
• Repository boundary awareness: The skill validates both developer-source and package-style usage, which is critical when changes span OfficeIMO and PSWriteOffice repos.
• Preset and theme guidance: It encourages presets that hide complexity without hiding behavior, so agents can design friendly cmdlets without losing flexibility.
• Cross-repo consistency: The skill ensures the agent checks OfficeIMO's existing capabilities before adding PowerShell code, reducing redundancy.

Practical scenarios

Migrating a PDF generation cmdlet

Your existing New-PDF cmdlet has a -Header parameter that duplicates OfficeIMO's header logic. The skill tells the agent to first inventory OfficeIMO's reusable capability, then map the parameter to the shared option, and keep the cmdlet as a thin wrapper with a clear default preset.

Comparing PDF feature gaps

You're not sure whether OfficeIMO already supports metadata extraction or if you need to build it. The skill directs the agent to read Roadmap/PSWritePDF-RetirementGapAnalysis.md, then decide if the missing feature should live in the shared engine or as a thin PowerShell adapter.

Adding a new conversion option

The agent is asked to add a PDF-to-image conversion toggle. Instead of coding it directly in PSWriteOffice, the agent uses the skill's questions to categorize it as a conversion adapter and implements the logic in the shared PDF engine, exposing a simple switch in the cmdlet.

Add it to your agent workflow

Install the skill with:

npx skills add EvotecIT/OfficeIMO --skill pswritepdf-retirement

Then your agent can read the retirement gap analysis and follow the golden path before writing any code. For example, prompt: "Using the pswritepdf-retirement skill, plan how to move the PDF stamping feature from PSWritePDF to OfficeIMO and expose it as a PSWriteOffice cmdlet."

Compare before adopting

Before committing, compare the skill against:

• Quality signals: Check OfficeIMO's GitHub stars (515), recent commits, and whether the retirement analysis is actively updated.
• Maintenance freshness: Look for recent releases and issue responses, indicating the maintainer is engaged.
• Alternatives: If you're not deeply tied to the EvotecIT ecosystem, evaluate standalone PDF libraries or other PowerShell wrappers.
• Workflow fit: Ensure the skill's approach matches your existing agent conventions and whether your team prefers cmdlet-thin vs. feature-richer modules.

Why it is worth tracking

This skill is a practical bridge for a real migration, backed by an active project (EvotecIT/OfficeIMO). It encodes architectural wisdom that prevents common pitfalls when consolidating PowerShell PDF features. Track it if you're planning any PSWritePDF retirement or want to align your PowerShell PDF surface with a reusable engine. As the retirement gap analysis evolves, the skill will stay current—making it a low-effort, high-signal addition to your agent's toolkit. For more context, see the OpenAgentSkill listing.