Doc Importer
- 74 installs
- 325 repo stars
- Updated August 2, 2026
- athola/claude-night-market
Turn PDF, Office, or HTML files into editable markdown for your repo docs or agent rewriting workflows.
About
Document Importer is an agent skill for solo builders who receive specs, decks, spreadsheets, or exports as binary files and need them inside the repo as editable markdown. Use it when someone hands you a DOCX, PPTX, XLSX, PDF, or HTML path or URL and you want project documentation you can rewrite, diff, or feed into other scribe and leyline skills. The workflow starts by confirming the source exists or the URL is reachable, then applies the document-conversion protocol: construct a URI, try markitdown for best fidelity, and fall back to native tools when MCP is unavailable. It deliberately avoids overlapping jobs—academic papers go to tome:papers, web articles to memory-palace:knowledge-intake, and markdown already in tree goes straight to scribe remediation. Estimated footprint is lightweight (basic complexity, fast model hint), which suits indie operators batching client deliverables or internal wikis without standing up a separate ETL pipeline. Install it when ingestion is the bottleneck, not when you only need greenfield doc generation from scratch.
- Imports DOCX, PPTX, XLSX, PDF, and HTML into markdown via leyline:document-conversion
- Two-step workflow: identify source, then convert with markitdown MCP preferred and native fallbacks
- Chains scribe:slop-detector and scribe:doc-generator for downstream cleanup and authoring
- Explicit routing: not for academic papers (tome:papers) or web knowledge intake (memory-palace)
Doc Importer by the numbers
- 74 all-time installs (skills.sh)
- Ranked #711 of 1,879 Documentation skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/athola/claude-night-market --skill doc-importerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 74 |
|---|---|
| repo stars | ★ 325 |
| Security audit | 2 / 3 scanners passed |
| Last updated | August 2, 2026 |
| Repository | athola/claude-night-market ↗ |
What it does
Turn PDF, Office, or HTML files into editable markdown for your repo docs or agent rewriting workflows.
Files
Document Importer
Import external documents into editable markdown.
When To Use
- User provides a DOCX, PPTX, XLSX, PDF, or HTML file
to convert into project documentation
- User wants to extract content from a document for
rewriting or remediation
- User has a slide deck or spreadsheet to turn into
markdown documentation
When NOT To Use
- Academic paper analysis: use
tome:papers - Web article knowledge intake: use
memory-palace:knowledge-intake
- Content already in markdown: use
scribe:doc-generator
remediation mode directly
Import Workflow
Step 1: Identify Source
Determine the source document:
- Local file path: verify it exists with Read tool
- URL: verify accessibility
- User description: confirm format and location
Step 2: Convert to Markdown
Apply the leyline:document-conversion protocol:
1. Construct URI from source (file path or URL) 2. Try the markitdown MCP tool for best quality 3. If unavailable, use native tool fallbacks 4. If format unsupported, inform user
Step 3: Structural Cleanup
After conversion, normalize the markdown:
- Ensure ATX headings (
# style, not setext underlines) - Wrap prose lines at 80 characters per
leyline:markdown-formatting
- Fix broken tables (align columns, add headers)
- Remove conversion artifacts (page numbers,
headers/footers, watermarks, repeated logos)
- Preserve all substantive content
Step 4: Sanitize External Content
Apply the leyline:content-sanitization checklist:
- Size check (truncate sections over 2000 words)
- Strip system/instruction tags
- Wrap in external content boundary markers
Step 5: Write Draft
Write the converted markdown to the target location. Default: same directory as source, with .md extension. Ask the user for target path if ambiguous.
Step 6: Hand Off to Doc-Generator (Optional)
If the user wants polishing or rewriting:
- Invoke
Skill(scribe:doc-generator)in Remediation
mode on the imported file
- The doc-generator handles slop detection, style
application, and quality gates
Offer this step. Do not assume the user wants remediation.
Output Quality
The imported markdown should:
- Have a top-level
# Titlefrom the document title - Preserve the original heading hierarchy
- Convert tables to markdown tables
- Convert images to
references
(note: image files may need separate handling)
- Convert lists faithfully
- Mark unclear or garbled sections with
<!-- REVIEW: conversion artifact -->
Exit Criteria
- Source document identified and accessible
- Conversion attempted via document-conversion protocol
- Structural cleanup applied
- Sanitization checklist passed
- Draft written to target path
- User informed of any conversion limitations
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71FAQ
Is Doc Importer safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.