Jstodocx api
Skill aiskillstore/marketplace/skills/daanaagua/jstodocx-api
Generate Microsoft Word DOCX files through the jstodocx.com API. Use when Codex needs to create or download .docx files from basic HTML, JavaScript source text, or controlled document template fields; when a user asks for HTML to DOCX, JS source to Word, or template-based DOCX generation via an API; or when integrating a lightweight Cloudflare Worker DOCX conversion endpoint into scripts, tests, or agent workflows.From its SKILL.md
npx -y skills add aiskillstore/marketplace --skill jstodocx-apiAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
2.7 KB, 578 tokens by cl100k_base, as published. Nobody here has run it
jstodocx.com API
Use the jstodocx.com API to create Word .docx files from controlled inputs. The API is useful for agents that need a downloadable DOCX without installing document-generation dependencies locally.
Read references/api.md when you need exact request schemas, examples, status codes, or response headers.
Workflow
- Choose one mode:
html: convert basic HTML headings, paragraphs, lists, and tables into DOCX.js-source: archive JavaScript source text as a readable Word document. Do not treat this as code execution.template: create a report, invoice, proposal, resume, or meeting-notes DOCX from structured fields.
- Send
POST https://jstodocx.com/api/v1/docxwithcontent-type: application/json. - If the endpoint returns
401, ask the user for an API key or use the browser-local website instead. Do not guess credentials. - Save the binary response to a
.docxfile. - Verify the result when possible by checking the response
content-type, filename, and ZIP magic bytesPK.
Safety Rules
- Do not execute arbitrary JavaScript through this API. The
js-sourcemode treats JavaScript as text only. - Do not send protected, confidential, or high-risk content unless the user explicitly confirms it is acceptable to send it to the API.
- Do not print, log, commit, or store API keys.
- Do not include raw user document content in logs or final summaries. Summarize mode, byte size, filename, and status instead.
- Do not claim pixel-perfect HTML fidelity. The API supports basic document formatting.
Minimal Example
curl -X POST "https://jstodocx.com/api/v1/docx" \
-H "content-type: application/json" \
--output release-plan.docx \
--data '{
"mode": "html",
"title": "Release Plan",
"html": "<h1>Release Plan</h1><p>Hello <strong>team</strong>.</p>"
}'
If the user provides an API key:
curl -X POST "https://jstodocx.com/api/v1/docx" \
-H "content-type: application/json" \
-H "authorization: Bearer $JSTODOCX_API_KEY" \
--output source-archive.docx \
--data '{
"mode": "js-source",
"title": "Widget Export Code",
"code": "function exportWidget() {\n return 42;\n}",
"options": { "lineNumbers": true }
}'
What ships with it: 3 files
31.0 KB alongside SKILL.md
agents/
- openai.yaml215 B
references/
- api.md2.7 KB
- skill-report.json28.1 KB