Total 53,816 skills, Document Processing has 772 skills
Showing 12 of 772 skills
Convert Markdown files and strings into DOCX documents using @mohtasham/md-to-docx. Use when a user needs Markdown to Word conversion, CLI-based file conversion, options-driven styling/alignment/font family, TOC/page break handling, underline/strikethrough formatting, multi-section documents with per-section headers/footers, or programmatic conversion in Node/browser code.
Use when auditing a wiki for health issues — contradictions between pages, orphan pages, broken cross-references, stale claims, missing pages, or coverage gaps. Run after every 5-10 ingests.
This skill is to be used when users explicitly request "migrate LaTeX templates", "integrate old projects into ChineseResearchLaTeX", "apply old bids/papers/graduation theses/resumes to the current template", "organize Word/PDF/Markdown/scattered tex files into existing projects", or directly mention `transfer-old-latex-to-new`. The old alias `migrating-latex-templates` is also supported. This skill only migrates the main content to the content layer of the existing templates in the current repository; it must never modify the source code of public packages in `packages/`, nor modify the template styles or entry skeletons in `projects/`, and can only write to content files allowed to carry the main content in the target project.
Extract text from PDFs as structured, semantic Markdown. Use when converting a PDF to Markdown, extracting text from a PDF, processing one or more PDFs into Markdown output, reading PDF contents for analysis, ingesting documents for RAG pipelines, preparing PDFs for LLM context, or any task where PDF text needs to be in a machine-readable format. ALWAYS use this skill when the user has a PDF and needs its content as text or Markdown — even if they don't explicitly say "convert to markdown".
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles
Documenterra integration. Manage Documents, Folders, Users, Groups, Tags. Use when the user wants to interact with Documenterra data.
Extract structured data from multiple documents into comparison matrix with citations. Use for bulk document review.
Analyze a batch of functional specs from a ***plain spec file to determine which pairs conflict. Replaces the pair-by-pair `analyze-2-func-specs` flow when a caller wants to check many specs at once (e.g. a new spec against every existing spec, or a freshly inserted batch against itself).
Create or include a Liquid template in a ***plain spec file using {% include %} syntax. Use when the same spec content needs to be reused across multiple .plain files with different parameters.
Translates a contract review into a summary the business stakeholder will actually read. Not a legal memo — a two-minute answer to "can I sign this and what do I need to know." Use when user says "summarize for the business", "write this up for [stakeholder]", "explain this to procurement", "non-legal summary", or when a review is done and needs to go to someone outside legal.
Comet Phase 5: Archive. Invoke with /comet-archive. Sync delta spec to main spec and archive the change.
Convert Markdown documents into beautiful, comfortable, well-structured, directly openable HTML long-form reports. Suitable for converting .md files to HTML, standardizing the layout of research/industry/survey documents, generating single-file web reports for offline sharing, embedding or verifying local images, fixing misaligned columns caused by Markdown table separators, or optimizing reading margins, image presentation, directory navigation, table responsiveness, and print styles of existing HTML reports.