docx-import

Parse 84000-compliant Word documents to extract titles, metadata, and passages.

Updated Mar 26, 2024
One-click install
npx skills add https://github.com/84000/84000-apps --skill docx-import
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docx-import
Source: https://github.com/84000/84000-apps/tree/main/skills/docx-import
Command: npx skills add https://github.com/84000/84000-apps --skill docx-import

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates the complex, error-prone process of ingesting 84000 translation Word documents into the studio database, ensuring consistent mapping of titles, metadata, and passages.

Core Features & Use Cases

  • Structured Ingestion: Maps Word paragraph styles and document structure to database passages, titles, and folio annotations.
  • Validation & Preview: Provides a mandatory dry-run preview to verify mapping accuracy and identify deviations before applying changes.
  • Use Case: An editor needs to import a newly completed translation of a sutra; this skill parses the document, identifies the work, maps the content, and applies the import via the studio MCP tool.

Quick Start

Use the docx-import skill to parse the attached translation document and generate a preview of the database operations for the target work.

Frequently Asked Questions about docx-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import Word documents into a translation database?

To import Word documents into a translation database, this skill parses 84000-compliant .docx files to extract titles, metadata, and passages, mapping document styles directly to database operations for structured content ingestion.

What is the process for mapping translation document styles to database passages?

Mapping translation document styles to database passages involves parsing Word paragraph structures and folio annotations, automatically matching them to specific database fields while generating a mandatory review preview to verify accuracy.

Can I preview database changes before applying a Word document import?

Yes, you can preview database changes before applying a Word document import. The skill provides a mandatory dry-run review that verifies mapping accuracy and identifies any template deviations prior to final database ingestion.

Do I need a specific template to parse translation content from a docx file?

Yes, you need a specific template to parse translation content from a docx file. The ingestion process requires strict adherence to 84000 copy-editor template specifications to accurately map metadata and passages into the database.

What limitations exist when importing translation Word docs into a content management system?

A key limitation when importing translation Word docs is the strict dependency on the studio MCP endpoint and 84000-compliant formatting. Deviations from the specified copy-editor template will disrupt the automated mapping of titles and passages.