Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
Markdown Exporter provides AI agents with the ability to convert Markdown text into structured files. It enables automation builders to move beyond plain text by generating deliverables in formats such as PDF, DOCX, and PPTX.
The skill also handles technical extraction, allowing agents to isolate code blocks from Markdown and save them as standalone Python, Bash, or JavaScript files.
WHO IT'S FOR
AI agent / automation builders
integrating document export capabilities into AI workflows
Technical writers
converting markdown documentation to multiple delivery formats
Data analysts
exporting markdown tables to structured data files
Software engineers
extracting code blocks from markdown to source files
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Download the Markdown Exporter source-code ZIP from https://github.com/bowenliang123/markdown-exporter/archive/refs/heads/main.zip and import it using the platform's local Agent Skills import mechanism.
Use the markdown-exporter skill to convert the Markdown file at <input.md> into a Word document at <output.docx>. Treat both values as file-path placeholders that I will replace with the actual input and output paths.
Markdown file path replacing <tables.md>; it must contain one or more Markdown tables
Output XLSX file path replacing <output.xlsx>
Use the markdown-exporter skill to convert the Markdown tables in <tables.md> to Excel files, using <output.xlsx> as the output filename. Treat both values as file-path placeholders that I will replace. If multiple tables produce multiple files, allow the documented automatic filename numbering and report all generated paths.
Markdown file path replacing <source.md>; it must contain fenced code blocks
Output file path replacing <output-path>
Use the markdown-exporter skill to extract the fenced code blocks from <source.md> into language-appropriate code files using <output-path> as the output file path. Treat both values as placeholders that I will replace; if multiple code blocks are present, allow the documented automatic filename numbering.