Skip to main content
plugin CX Codex

file-conversion — Claude Code plugin for file conversion

Convert local images, media, documents, and tabular data with tools installed on your machine. The original file stays untouched.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add wshobson/agents
/plugin install file-conversion@claude-code-workflows
Open on GitHub

What file-conversion does

The agent checks which local programs are available, inspects the file, then picks a conversion route. Output goes to a new directory rather than replacing the source. You can specify a target format and quality or layout requirements. For a URL, the file must first be retrievable through an authorized method.

Video and audio routes use FFmpeg and FFprobe; image conversion uses ImageMagick 7. Pandoc or LibreOffice handles supported documents, while Python 3 covers CSV and JSON. The plugin provides instructions, not the executables. PDF-to-Word results aren’t guaranteed, and scanned PDFs need local OCR tools followed by a layout review. Missing codecs, fonts, memory, or disk space can prevent a route from working.

Files are converted locally, without sending them to a hosted conversion service. Documents with external links or macros require a setup with network access blocked and macros disabled; a temporary profile alone does not provide those controls. Windows may use different executable names and shell syntax.

What it helps with

  • convert an image to another format
  • transcode audio or video with local tools
  • export an office document as PDF
  • convert tabular data between CSV and JSON
  • keep the source file intact during conversion

Example prompts for the agent

  • Convert report.docx to PDF and put the result in a separate folder.
  • Turn clip.mov into MP4 while following the requested quality settings.
  • Convert records.csv to JSON without replacing the source file.

How to install file-conversion

Plugin marketplace

/plugin marketplace add wshobson/agents
/plugin install file-conversion@claude-code-workflows

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about file-conversion

How do I install file-conversion in Claude Code?

Run these commands in order: /plugin marketplace add wshobson/agents, then /plugin install file-conversion@claude-code-workflows.

What does file-conversion do?

It guides the agent in choosing local tools to convert images, audio, video, documents, and tabular data. The output is saved separately so the original remains intact.

Which tools does file-conversion need?

It depends on the conversion: FFmpeg and FFprobe for audio or video, ImageMagick 7 for images, Pandoc or LibreOffice for documents, and Python 3 for CSV or JSON.

Source text

file-conversion · MIT
# File conversion

Guidance for converting local files with installed tools, preserving originals, and
checking the results. The workflow uses local files and local output paths. It does
not call hosted conversion services or upload files.

## Prerequisites

Install only the tools required for the requested route, under the session's existing
permission policy:

- FFmpeg and FFprobe for audio/video; available codecs depend on the build.
- ImageMagick 7 (`magick`) for images; formats such as HEIC and PDF may need delegates
  or a compatible local policy.
- Pandoc for supported structured document formats such as Markdown and DOCX.
- LibreOffice (`soffice`) for supported office-document exports, including PDF.
- Python 3 for CSV/JSON data conversion using the standard library.

The plugin supplies guidance, not these executables. The agent checks what is already
installed, inspects the source, and chooses a supported route. On Windows, executable
names and shell syntax may differ. No account or API key is required.

## Use and limits

Provide a local file or a retrievable URL, the target format, and any quality or
layout requirements. Results go into a fresh directory without replacing the original.
The skill includes examples and checks for media, images, documents, and tabular data.

Support depends on the installed readers, writers, codecs, fonts, and available memory
and disk space. Conversion may change layout, color, transparency, or compression.
PDF-to-Word is not guaranteed; scanned PDFs require local OCR tools and a separate
layout review. Unsupported routes stop with an explanation.

URL inputs can first be retrieved through an already-authorized method; report an
access gap if retrieval is unavailable. Conversion runs on local copies and local assets.
For documents with external links or macros, use an environment with network access
blocked and macros disabled, or stop. A temporary profile alone provides neither control.

## Migration from version 1

Version 2.0 removes the ChangeThisFile service integration and the bundled
`skills/file-conversion/scripts/convert.sh` upload script. Existing calls to that
script must be replaced with the appropriate local tool; there is no drop-in script
replacement. The plugin and skill names remain `file-conversion`.

Aadil Razvi authored the original hosted-service integration. Repository maintainers
rewrote version 2.0 for local tools and maintain the current workflow.

© Seth Hobson · MIT · wshobson/agents

Similar plugins

Plugins catalog →

From the same set405

The whole set →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor