client-communication-engine
Greek-language client correspondence — submission confirmations, summaries, document requests, reminders. Human review required before sending.
What this skill does
# Client Communication Engine This skill handles all outgoing communication from the accounting firm to its clients. It produces professional Greek-language letters, summaries, and notifications — the documents and emails that clients actually receive. Every piece of outgoing communication follows Greek business correspondence conventions, references the correct regulatory terminology, and is drafted for human review before anything is sent. The skill pairs with `greek-email-processor` (Skill 4), which handles inbound. Together they form the complete communication layer: Skill 4 reads the inbox, Skill 16 writes the outbox. ## Setup ```bash export OPENCLAW_DATA_DIR="/data" export SMTP_HOST="smtp.your-provider.com" # e.g. smtp.gmail.com, smtp.outlook.com export SMTP_USER="[email protected]" export SMTP_PASSWORD="app-specific-password" which jq curl || sudo apt install jq curl ``` SMTP credentials are required for sending client correspondence. All communications are drafted locally and require human review and approval before sending. Use app-specific passwords. ## Core Philosophy - **Draft First, Send Second**: Nothing is sent automatically. Every communication is drafted, shown for review, and requires explicit approval before dispatch. This applies to all communication types without exception - **Greek Business Standards**: Output matches what a professional Greek accounting firm would send — correct formal register, appropriate regulatory terminology, proper salutations and closings for Greek business correspondence - **Data-Driven Content**: Letters are generated from real system data — actual submission reference numbers, actual VAT amounts, actual deadlines. Nothing is fabricated or approximated - **Logged Against Client Record**: Every sent communication is recorded in `/data/clients/{AFM}/correspondence/` with timestamp, type, recipient, and content hash. The firm always knows what was said to whom and when - **Context-Aware Tone**: Document request letters are polite but clear. Deadline reminders escalate appropriately (informative → reminder → urgent → critical) without being aggressive. Submission confirmations are formal and precise - **Language Boundary**: Communications to clients are in Greek. Internal summaries and draft previews shown to firm staff are in English. The skill never sends English to a Greek client --- ## OpenClaw Commands ### Drafting Communications ```bash # Draft a submission confirmation letter openclaw comms draft --type submission-confirmation --afm EL123456789 --filing-type VAT --period 2026-01 openclaw comms draft --type submission-confirmation --afm EL123456789 --filing-type EFKA --period 2026-01 # Draft a monthly accounting summary openclaw comms draft --type monthly-summary --afm EL123456789 --period 2026-01 openclaw comms draft --type monthly-summary --afm EL123456789 --period 2026-01 --include-statements # Draft a document request openclaw comms draft --type document-request --afm EL123456789 --missing "bank-statements" --period 2026-01 openclaw comms draft --type document-request --afm EL123456789 --missing "october-invoices,payroll-hours" --deadline 2026-02-20 openclaw comms draft --type document-request --afm EL123456789 --from-pending-list # auto-reads pending.json # Draft a deadline reminder openclaw comms draft --type deadline-reminder --afm EL123456789 --deadline-type VAT --due-date 2026-02-25 openclaw comms draft --type deadline-reminder --afm EL123456789 --deadline-type VAT --due-date 2026-02-25 --urgency critical openclaw comms draft --type deadline-reminder --all-clients --deadline-type VAT --due-within 7-days # Draft an annual tax summary openclaw comms draft --type annual-tax-summary --afm EL123456789 --year 2025 openclaw comms draft --type annual-tax-summary --afm EL123456789 --year 2025 --include-e1-status # Draft a payment reminder (for clients with outstanding fees to the firm) openclaw comms draft --type payment-reminder --afm EL123456789 --invoice-ref INV-2026-001 # Free-form draft with prompt openclaw comms draft --type custom --afm EL123456789 --prompt "inform client that their ENFIA property tax instalment is due next month and we need their payment confirmation" ``` ### Reviewing Drafts ```bash # List all pending drafts openclaw comms drafts-list --all openclaw comms drafts-list --afm EL123456789 openclaw comms drafts-list --type document-request --pending-approval # Preview a draft (English summary of Greek content) openclaw comms preview --draft-id D20260218-001 openclaw comms preview --draft-id D20260218-001 --language el # Show full Greek text # Edit a draft before approval openclaw comms edit --draft-id D20260218-001 --field body --instruction "add mention of the EFKA deadline also due this month" openclaw comms edit --draft-id D20260218-001 --field tone --value formal # formal / professional / urgent ``` ### Approving and Sending ```bash # Approve and send a single draft openclaw comms send --draft-id D20260218-001 --approved-by "yannis.k" # Approve and send all drafts for a client openclaw comms send --afm EL123456789 --all-pending --approved-by "yannis.k" # Send via email (default) openclaw comms send --draft-id D20260218-001 --via email --approved-by "yannis.k" # Export as PDF for manual sending (no email integration configured) openclaw comms send --draft-id D20260218-001 --via pdf-export --approved-by "yannis.k" # Batch send — e.g. deadline reminders to all affected clients openclaw comms batch-send --type deadline-reminder --deadline-type VAT --due-within 7-days --approved-by "yannis.k" ``` ### Correspondence History ```bash # View sent communications for a client openclaw comms history --afm EL123456789 --last 30-days openclaw comms history --afm EL123456789 --type document-request --year 2026 openclaw comms history --afm EL123456789 --full # All time # Firm-wide communication log openclaw comms log --period 2026-01 --type all --format table openclaw comms log --period 2026-01 --unsent-drafts # Drafts that were created but never sent # Check if a specific type of communication has been sent recently openclaw comms check-sent --afm EL123456789 --type submission-confirmation --filing-type VAT --period 2026-01 ``` ### Template Management ```bash # List available templates openclaw comms templates-list openclaw comms templates-list --type document-request # Preview a template openclaw comms template-preview --name "vat-submission-confirmation" # Customise a template for a specific client (client-level override) openclaw comms template-override --afm EL123456789 --template "monthly-summary" --field salutation --value "Αγαπητέ κ. Παπαδόπουλε," ``` --- ## Communication Templates ### 1. Submission Confirmation Letter Sent after every successful government filing. References the actual AADE submission receipt. ``` [GREEK TEXT — rendered in Greek in the actual letter] [Firm letterhead] [Date in DD/MM/YYYY format] Αγαπητέ / Αγαπητή [Client contact name], [or: Αγαπητοί κÏÏιοι, for company-addressed] Σας ενημεÏώνουμε ότι ολοκληÏώθηκε επιτυχώς η υποβολή της παÏακάτω φοÏολογικής δήλωσης για λογαÏιασμό σας: ΤÏπος δήλωσης: [e.g. Δήλωση ΦΠΑ] ΠεÏίοδος: [e.g. ΘανουάÏιος 2026] ΑΦΜ: [EL123456789] ΑÏιθμός υποβολής: [AADE reference number] ΔμεÏομηνία υποβολής: [DD/MM/YYYY] Ποσό πληÏωτέο: [€X,XXX.XX] (εάν υφίσταται) ΠÏοθεσμία πληÏωμής: [DD/MM/YYYY] Για οποιαδήποτε αποÏία, παÏακαλώ επικοινωνήστε μαζί μας. Με εκτίμηση, [Accountant name] [Firm name] [Contact details] ``` ```yaml English_Preview_Fields: type: "VAT Return Submission Confirmation" client: "Alpha Trading AE (EL123456789)" period: "January 2026" reference: "AAD-2026-001234" submitted: "24/01/2026" amount_due: "EUR 3,340.00" payment_deadline: "25/02/2026" ``` --- ### 2. Monthly Accounting Summary Sent at month-end. Provides the client with a plain-language overview of what happened to their accounts that month. ```yaml Monthly_
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.