Administrative Document Writing Assistant

Problem It Solves

The most common rework in enterprise administrative documents is often not missing content, but misaligned document type, tone, or format. For example, writing a funding request to headquarters as report, using commanding language in a letter to a partner, missing the document type in the title, or writing the date as 2026.7.25. These issues cause approvals, archiving, and seal workflow to be rejected repeatedly.

This skill is intended for administrative teams, executive offices, clerical roles, and business owners who need to issue formal letters. It turns a casual request into a ready-to-issue administrative document and reduces tone and formatting drift.

Core Capabilities and Workflow

• Identify type and direction: recognize notice, request for instructions, report, letter, minutes, or decision, and distinguish upward, lateral, and downward tone.
• Apply structure: organize title, recipient, body, signature, date, and attachments; the body follows basis, main content, and closing requirements.
• Calibrate wording: avoid commanding language in upward documents, use consultative language in lateral letters, and keep downward notices or decisions clear and actionable.
• Emit artifacts: provide a final text ready to copy, an OfficialDoc JSON object, and tone/format notes, with fields such as doc_type, recipient, body_sections, sign_off, and date for archiving or downstream systems.

Scope and Caveats

It is suitable for internal notices, funding or instruction requests, reports, letters, and meeting minutes. It is not for legal documents, government red-header documents, contracts, or personal letters. The skill does not invent sender units, fabricate dates, or make unauthorized external commitments. For outbound documents, users must verify facts, amounts, deadlines, and the seal/approval process.