DOCX proposals and reports
Full-page branded covers, structured sections, reusable placeholders, embedded imagery, and editable body content.
This is not an in-browser generator. Install the Templify skill in a compatible AI agent, then ask that agent to create a local DOCX, PPTX, or XLSX file you can open and edit.
Free Templify skill. Requires a compatible AI agent; your agent’s usage charges may apply.
This builder creates prompt text only. Copy the result into an agent where the free Templify skill is installed; the agent creates and validates the local Office file.
Choose the essentials. You can refine details with your agent afterward.
Paste this prompt into Claude Code, Codex, or another compatible agent after installing the skill.
.manifest.json beside it. It does not upload, publish, email, or share anything unless you separately request the optional MCP handoff.These labeled illustrations show the kind of editable structure the skill creates. They are not customer files or fabricated case studies.
Proposal for {{client_name}}
Scope, timeline, pricing, and next steps remain editable.
ILLUSTRATIVE LAYOUT
The skill produces a real, editable Office file and validates it before handoff.
Full-page branded covers, structured sections, reusable placeholders, embedded imagery, and editable body content.
Presenter-led decks with clear visual hierarchy, one message per slide, branded layouts, and reusable content fields.
Editable structured plans, pricing models, trackers, and formulas designed around the workflow you describe.
The agent follows a deliberate workflow instead of guessing the format or silently choosing a design.
The skill collects format, purpose, audience, structure, style source, placeholders, language, and output directory.
Your agent studies the supplied website or style direction and translates it into colors, typography, spacing, shapes, and voice.
It writes the Office file and manifest, parses the package, checks layout and placeholders, and tests representative personalization values.
Start a Claude Code, Codex, or compatible agent session and paste the setup prompt. The agent identifies its own installation workflow, preserves your current configuration, and verifies the local skill without touching Google Drive.
branded-template-generator is discoverable, without uploading or deploying anything.Set up the free Templify branded-template-generator skill in this agent. Do what you can and guide me through anything that needs my input. 1. Identify this agent and version, then inspect existing plugins and skills. Preserve existing configuration and avoid duplicates. 2. Install the Templify plugin or branded-template-generator skill using this agent's supported workflow from https://github.com/Doc-Failure/templify-agent-plugin. Check the installed client's help or current documentation before running commands. 3. Confirm that branded-template-generator is discoverable and explain how to invoke it in this agent. 4. Do not start Google OAuth, access Google Drive, upload files, deploy proposals, or purchase anything during setup. When setup is complete, briefly report what succeeded, any action I must take, and the exact command or invocation for creating my first local DOCX, PPTX, or XLSX template.
Clone the repository, load the plugin, then invoke the template skill explicitly.
git clone https://github.com/Doc-Failure/templify-agent-plugin.git claude --plugin-dir ./templify-agent-plugin /templify:branded-template-generator
# Load the repository with your Codex plugin workflow, # then invoke: $branded-template-generator
If DOCX, PPTX, or XLSX is not specified, the agent must ask. It also confirms the structure, style source, and exact output directory before generation.
Prices, dates, results, biographies, statistics, and commitments cannot be fabricated. Assumptions and example content must be labeled.
Reusable fields use consistent {{snake_case_placeholders}}, and every token maps exactly once to the generated manifest.
A Markdown outline or screenshot is not completion. The Office package must exist, open structurally, and pass layout and placeholder checks.
Both paths begin with the same editable DOCX, PPTX, or XLSX file. MCP is optional and is not required for the Google Workspace add-on.
Upload the Office file to Drive and convert it to native Google Docs, Slides, or Sheets. Review the converted layout and placeholders, then use the Templify add-on to create client copies, publish proposal links, and review engagement signals.
The add-on does not import the manifest, and this path does not require MCP.
Connect Templify MCP so your agent can upload the Office file, convert it to an editable Google file, apply reviewed edits, publish a proposal, and retrieve engagement signals.
Your agent supplies the AI. Templify supplies Google file, publishing, and analytics operations.
Install the open-source skill in a compatible agent, then run the prompt you built above.