Converters
- When to use it
- Turn Markdown into Word, Excel, PowerPoint and Confluence files that people outside engineering can open, and turn their files back into Markdown. Standard-library Python scripts, with nothing to install.
- Covers
- Get a draft ready to ship (5)
- Where you decide
- No gated loop of its own; the skills run one at a time.
- Size
- 10 skills · 0 loops
10 to 20 minutes a session
npx skilldrop-cli install --pack converters
Installs 10 skills, including core.
Other ways to install
The pack's loops too, each as an invokable skill:
npx skilldrop-cli install --loop --pack converters
In Claude Code, as a plugin (after /plugin marketplace add sananthanarayan/skilldrop):
/plugin install converters@skilldrop
Into Cursor, Kiro or another IDE:
npx skilldrop-cli install --pack converters --ide cursor
Start here: Send a Markdown report as a Word document and its tables as a spreadsheet
Paste this into your agent:
Convert reports/q3-review.md to a Word document for the Acme account team, and put its tables in an Excel workbook for finance.
- Before you start
- Python 3.9 or later
- A Markdown file with a heading or two, and a table if you want a spreadsheet
- How to tell it worked
- md-to-docx writes q3-review.docx with the headings in Word's navigation pane and a WARN line for anything it dropped, and md-to-xlsx writes q3-review.xlsx with one sheet per table, numbers typed as numbers, and a frozen, filtered header row.
- If nothing happens
- If the script says python3 is not found, install Python 3.9 or later. If a skill does not activate, ask for it by name ("use md-to-docx"). If a table lands as text, read the per-sheet counts md-to-xlsx printed: a unit typed inside the number cells is the usual cause.
A typical session
When: Your draft is in Markdown, but the people who need it work in Word, Excel, PowerPoint or Confluence, or they sent you their files and you want to work on them as Markdown. About 10 to 20 minutes.
You bring:
- the Markdown draft, or the Word, PDF, Excel or HTML files you were sent
- a brand.json from brand-kit, if the Word file should be in your brand
- who it is for, and whether they edit it, calculate with it or only read it
-
- You
- If you start from someone else's files, hand them over.
- You get
- Markdown you can edit and diff, with a count of what could not come across (images, charts, comments, formulas, tracked changes).
-
- You
- Run it on the finished draft before it leaves the team.
- You get
- The draft with invisible characters and generated-by trailers stripped, and machine-sounding lines flagged with rewrites.
-
- You
- Convert the draft for readers who will edit or comment in Word.
- You get
- A .docx with real headings, live links, tables and embedded images, plus a list of anything dropped.
- You decide
- Send it, or fix the warnings in the Markdown and convert again.
-
- You
- Convert the tables for readers who will filter or total them.
- You get
- A .xlsx with one sheet per table, typed numbers, dates and percentages, and formulas off unless you ask.
You end with: The same content in the format each reader uses, with nothing dropped silently, and a Markdown source you can keep editing.
Compare Converters with another pack
Skills in this pack (5)
- file-to-markdown Convert a Word document, PowerPoint deck, Excel workbook, web page, CSV, JSON, text file, email (.eml or Outlook .msg) or PDF into clean Markdown. It keeps headings, lists, tables, links, bold and italic, slide titles and speaker notes. It saves embedded images beside the Markdown and links them, shows tracked changes as pending rather than accepted, and reports everything else it dropped (charts, comments, formulas), so the content can be read, reviewed or fed to another skill. Use when the user hands over a .docx, .pptx, .xlsx, .html, .csv, .json, .eml, .msg or .pdf and says "read this", "turn this into markdown", "extract the text", or wants it critiqued or briefed. light
- md-to-confluence Turn a Markdown runbook, design note or guide into a Confluence page: storage-format XHTML with real code blocks, tables, tasks, info and warning panels, images as attachments and an optional contents macro, a warning for everything dropped, and an optional publish that first shows which page it will create or overwrite and at what version, refuses stale or wrong-space overwrites, and takes credentials only from the environment. Use when the user says "put this in Confluence", "publish this markdown to the wiki", "update the Confluence page with this", "convert to Confluence storage format", or names a Confluence space for a Markdown file. light
- md-to-docx Turn a Markdown draft into a Word document (.docx) that someone outside engineering can open, edit and track changes in, with real Heading styles so the navigation pane and table of contents work, live hyperlinks, numbered and bulleted lists, tables, code blocks, embedded images and optional brand fonts and colours, and a warning for everything that could not be carried over. Use when the user wants a Markdown file as a Word doc, says "send this as a .docx", "convert to Word", "legal needs it in Word", or "make this editable for the client". standard
- md-to-pptx Turn an existing Markdown document (a status report, runbook, review or notes) into a PowerPoint deck (.pptx) that opens without a repair prompt, with nothing to install. Each heading becomes a slide, lists keep their nesting, tables become real PowerPoint tables, images are embedded, and comments become speaker notes. A section too long for one slide is split onto "continued" slides instead of shrinking the text, and the reply names every split, everything dropped, and any speaker note that would go out with the file. Use when the user says "turn this markdown into slides", "make this report a PowerPoint", "convert the .md to pptx", "I need this as a deck for Thursday", or "export these notes to PowerPoint". light
- md-to-xlsx Turn the tables in a Markdown file, a CSV or a JSON array into an Excel workbook (.xlsx) that finance, ops or a client can sort, filter and sum, with one sheet per table named from its heading, real numbers, percentages, currency and dates instead of text, a bold frozen header row with filters, sensible column widths, and formulas left inert unless asked for. Use when the user wants a spreadsheet from Markdown tables or data, says "put this in Excel", "convert the CSV to xlsx", "give finance a spreadsheet", or "turn this JSON into a sheet". standard
Included from core (5)
- brief-intake Turn raw mess — a Slack thread, meeting transcript, Jira ticket, half-written Notion page, email chain, or paragraph of free-form context — into a structured brief that the downstream skill (adr-generator, design-doc, runbook-generator, exec-summary, slide-outliner) can consume without further intake. Use whenever the user has unstructured source material and is about to invoke another skilldrop skill, or when a draft is missing the load-bearing context the next step will need. standard
- context-graph Map the decisions behind a codebase from its ADRs, RFCs and design records — each record's status and date, what supersedes or amends what, which records cite which, the files and folders each decision governs, and with git the commits that implemented it and the commits that changed each decision's code since it was made, and who made them — then answer "why is it like this?" from the record and check the record is still true. Finds supersessions only one side records, current decisions pointing at code that is gone, code that has drifted from its decision, two current decisions governing the same path, and references to records that don't exist. Use when the user asks "why do we use X", "which decisions govern this file or service", "is this ADR still current", "has the code drifted since we decided this", "are our ADRs out of date", "what was decided before I change this", wants a map of the architecture decisions, or is onboarding onto a codebase's history. standard
- council-review Convene a council of distinct senior-engineer personas (Architect, Security, Operator/SRE, Pragmatist, User-Advocate, plus optional bench seats) to deliberate a decision, design, or code change — each takes an independent stance, the genuine disagreements are surfaced as named cruxes, and a Chair issues a reconciled verdict that records dissents and states what would change the decision. The "Claude Council." Use when a choice has real tradeoffs and one reviewer's voice isn't enough: architecture decisions, risky changes before merge, RFC/design scrutiny, "should we adopt X?", rewrite-vs-refactor, or a pre-mortem. heavy
- doc-critique Review an existing document — ADR, design doc, runbook, exec summary, tech-comparison matrix, deck outline, decision log — and produce a structured critique against the same quality bars the skilldrop generators enforce. Categorizes findings by severity (blocker / major / minor / nit), points to the exact section/line, and suggests a concrete fix for each. Use when the user wants a second-pair-of-eyes review before sharing a doc, or has been handed someone else's artifact and wants to know what to push back on. heavy
- output-hygiene Review agent-written text before it ships and strip the machine artifacts it carries — invisible Unicode, non-breaking spaces, homoglyphs, harness-added provenance trailers, trailing chat closers — then flag the prose tells a script cannot catch, each quoted with a rewrite. Use when the user wants to clean up AI-generated output, asks to remove a Claude watermark, attribution footer, or "Generated with" line, wants a draft that does not read as machine-written, or needs a pre-ship hygiene pass on a document, commit message, or pasted chat answer. standard