corporate-letter

Generate branded 31C PDF and DOCX letters from JSON payloads.

10|1|Updated Jun 29, 2026

Search Tags:#automation #branding #compliance #document-generation #correspondence #31c

Ready to run

npx skills add https://github.com/mishahanin/heading-os --skill corporate-letter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: corporate-letter
Source: https://github.com/mishahanin/heading-os/tree/main/.claude/skills/corporate-letter
Command: npx skills add https://github.com/mishahanin/heading-os --skill corporate-letter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates the risk of non-compliant, unbranded, or inconsistent formal correspondence by automating the generation of 31C-branded PDF and DOCX documents.

Core Features & Use Cases

Locked Template Enforcement: Automatically applies official letterhead, confidentiality footers, and 31C-LET reference numbering.
Workflow Integration: Integrates with CRM context and pipeline data to ensure accurate, professional communication.
Use Case: Use this when you need to send a formal letter of interest to a regulator or a letter of introduction to a new institutional partner while maintaining strict corporate voice and formatting standards.

Quick Start

Invoke the corporate-letter skill by providing the recipient name and the subject of your formal letter.

Frequently Asked Questions about corporate-letter

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

FAQPage Schema

How do I generate branded corporate letters in PDF and DOCX formats?▼

To generate branded corporate letters, this Skill assembles JSON payloads into standardized PDF and DOCX documents using Python-based rendering scripts. It automatically applies official letterhead, confidentiality footers, and reference numbering to ensure strict style and formatting compliance.

Can I automate formal correspondence with regulators and investors?▼

Yes, you can automate formal correspondence with regulators and investors by invoking this Skill with recipient names and letter subjects. It enforces corporate voice and formatting guardrails, producing compliant external documents suitable for institutional communication.

Do I need Python to render compliant external correspondence documents?▼

Yes, Python is required to render compliant external correspondence documents. The Skill relies on Python-based rendering scripts to assemble JSON payloads into standardized PDF and DOCX artifacts while enforcing locked template guardrails.

How do locked templates enforce corporate voice in document generation?▼

Locked templates enforce corporate voice in document generation by automatically applying official letterhead, confidentiality footers, and 31C-LET reference numbering. This prevents non-compliant or inconsistent formatting across all generated external letters.

Does corporate letter generation integrate with CRM context and pipeline data?▼

Yes, corporate letter generation integrates with CRM context and pipeline data to ensure accurate, professional communication. This workflow integration allows the Skill to pull relevant recipient and subject data directly into the standardized document artifacts.

What are the limitations of automating external letter generation?▼

The limitation of automating external letter generation is that document artifacts are restricted to locked corporate templates, meaning custom formatting outside the strict 31C style, voice, and reference numbering guardrails is not supported. It requires structured JSON payloads for rendering.