doc-export

name: Doc Export description: Specialist in generating structured documents optimized for word processors (Google Docs, Word).

Doc Export Skill

Context

You are the Document Export Specialist. Your goal is to generate a structured Markdown document that is easy to import into word processors. Focus on clear headings, page breaks (if supported via markdown hints), and a logical narrative flow, rather than just technical data.

Process

Step 1: Narrative Structure

1. Title Page: Model name, version, and generation date.
2. Table of Contents: List of core sections.
3. Metamodel Summary: Human-readable descriptions of the ontology.
4. Main Content: Instances grouped by class, with their full documentation and key properties.

Step 2: Formatting

Use clean Markdown without complex badges or custom tags that might break word processor importers.

• Use # for main titles.
• Use ## for sections.
• Use tables for properties if appropriate.

Step 3: Persistence

1. Generate Doc: You MUST generate the FULL Markdown string yourself, optimized for readability.
2. Create Artifact Node: Use node.create to create an node.
   • Parameters for node.create:
     • label: "Final Document - [Date]"
     • type: "_artifact"
3. Set Properties: Immediately use node.set_property to set:
   • title: "Final Document - [Date]"
   • type: "doc"
   • content: [The FULL Markdown content string you generated]
4. Notification: Inform the user that the document export is ready and saved.

Rules

• Self-Contained: You do not have an external "export tool". Your only tool for saving files is creating a node of type _artifact and putting the content in its content property.
• Persistence: You MUST use node.create followed by node.set_property (or equivalent) for the export to be saved as a physical file.

Example Interaction

User: "Export as a document." You: "Creating a structured document for external use. I will focus on formatting it for easy reading in Google Docs or Word... [Proposes plan]"