qwen_agent/skills/japanese-business-writer/SKILL.md

name	description
japanese-business-writer	Draft and polish formal Japanese business writing for emails, notices, request letters, cover notes, and workplace communication with clear structure and appropriate 敬語. Use this whenever users ask for Japanese business writing, formal JP writing, 敬語 polishing, 文面添削, 依頼メール, 案内文, 送付状, or 社内通知; use it for writing quality and business tone, not for compliance review or complaint de-escalation.

Japanese Business Writer

Overview

Create clear, polite, and actionable Japanese business writing for enterprise contexts.

This skill is for:

• Business emails (依頼・催促・お詫び・日程調整)
• Internal announcements (社内通知)
• Approval request style text (稟議向け下書き)
• Message polishing into proper 敬語 and business tone

Triggering Cues

Use this skill when user messages include:

• Chinese cues: 日文商务邮件、日企邮件、敬语润色、社内通知、商务公文、稟議
• Japanese cues: ビジネスメール、敬語、社内通知、依頼文、稟議、日程調整、お詫び
• English cues: Japanese business email, keigo rewrite, internal notice, formal JP message

Input Requirements

Ask for or infer these minimum inputs:

1. Purpose (what this document needs to achieve)
2. Audience (customer / vendor / manager / all employees)
3. Tone strength (soft / neutral / firm)
4. Deadline or key dates (if any)
5. Language preference from current conversation

If details are missing, proceed with best-effort draft and list assumptions clearly.

Output Format

Always output in this structure:

1. Draft (final text ready to send)
2. Subject options (2-3 options when relevant)
3. Tone note (one line: polite/firm and why)
4. Optional alternatives (short variant for different formality level)

For email drafts, use:

• 件名
• 宛名
• 挨拶
• 要件
• 依頼/対応期限
• 結び
• 署名（placeholder）

Workflow

1. Identify writing scenario and relationship (internal/external, hierarchy).
2. Determine required politeness level (丁寧語 / 尊敬語 / 謙譲語 balance).
3. Build a concise structure with clear action request.
4. Ensure no ambiguity in next steps, owner, and deadline.
5. Return polished text plus subject options.

Examples

Example 1

Input:

• 供应商连续两周未开票，需要礼貌但明确地催办，本周五前给到。

Output style:

• Japanese formal external email
• Firm but polite request
• Explicit due date and contact point

Example 2

Input:

• 社内通知：周六凌晨系统维护，可能影响登录 30 分钟。

Output style:

• Internal notice format
• Scope, window, impact, and inquiry contact clearly separated
• Easy to scan for all employees

Guidelines

• Keep paragraphs short and easy to scan.
• Be explicit about action owner and due dates.
• Prefer clarity over decorative language.
• Do not fabricate legal claims or policy references.
• When user language is non-Japanese, keep Japanese enterprise structure but write in user language unless user asks Japanese-only.