<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[GLM 做企业材料写作，怎么避免全是公文味？]]></title><description><![CDATA[<p dir="auto">GLM 写中文正式材料挺稳，但我们产品里要写客户邮件，不想太公文。怎么调？</p>
]]></description><link>https://localaihub.com/topic/94/glm-做企业材料写作-怎么避免全是公文味</link><generator>RSS for Node</generator><lastBuildDate>Wed, 03 Jun 2026 17:51:03 GMT</lastBuildDate><atom:link href="https://localaihub.com/topic/94.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 05 May 2026 22:56:00 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 19:17:00 GMT]]></title><description><![CDATA[<p dir="auto">很好。别把模型风格问题当成单句 prompt 问题。</p>
]]></description><link>https://localaihub.com/post/693</link><guid isPermaLink="true">https://localaihub.com/post/693</guid><dc:creator><![CDATA[小曹]]></dc:creator><pubDate>Wed, 06 May 2026 19:17:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 18:08:00 GMT]]></title><description><![CDATA[<p dir="auto">我把 GLM 留给正式材料，客户邮件加品牌样例和动作校验，再和 Qwen/GPT 盲评。</p>
]]></description><link>https://localaihub.com/post/692</link><guid isPermaLink="true">https://localaihub.com/post/692</guid><dc:creator><![CDATA[晚点再说]]></dc:creator><pubDate>Wed, 06 May 2026 18:08:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 16:44:00 GMT]]></title><description><![CDATA[<p dir="auto">有一点，但不够。示例、长度限制、禁用短语、人工评测一起上。</p>
]]></description><link>https://localaihub.com/post/691</link><guid isPermaLink="true">https://localaihub.com/post/691</guid><dc:creator><![CDATA[陈一]]></dc:creator><pubDate>Wed, 06 May 2026 16:44:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 15:25:00 GMT]]></title><description><![CDATA[<p dir="auto">那系统提示里写“不要公文味”有用吗？</p>
]]></description><link>https://localaihub.com/post/690</link><guid isPermaLink="true">https://localaihub.com/post/690</guid><dc:creator><![CDATA[普通网友A]]></dc:creator><pubDate>Wed, 06 May 2026 15:25:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 12:39:00 GMT]]></title><description><![CDATA[<p dir="auto">文案生成也要接工具状态。已创建工单才能说“已创建工单”，不能靠模型推测。</p>
]]></description><link>https://localaihub.com/post/689</link><guid isPermaLink="true">https://localaihub.com/post/689</guid><dc:creator><![CDATA[rootless]]></dc:creator><pubDate>Wed, 06 May 2026 12:39:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 11:54:00 GMT]]></title><description><![CDATA[<p dir="auto">用户邮件里最烦的是“已为您反馈相关部门”。如果没有真实动作，别让模型写。</p>
]]></description><link>https://localaihub.com/post/688</link><guid isPermaLink="true">https://localaihub.com/post/688</guid><dc:creator><![CDATA[葡萄冰]]></dc:creator><pubDate>Wed, 06 May 2026 11:54:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 11:40:00 GMT]]></title><description><![CDATA[<p dir="auto">有可能，但别靠印象。拿 50 封真实邮件改写，盲评自然度、准确性、是否越权。</p>
]]></description><link>https://localaihub.com/post/687</link><guid isPermaLink="true">https://localaihub.com/post/687</guid><dc:creator><![CDATA[林小北]]></dc:creator><pubDate>Wed, 06 May 2026 11:40:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 10:36:00 GMT]]></title><description><![CDATA[<p dir="auto">Qwen/GPT 会不会更自然？</p>
]]></description><link>https://localaihub.com/post/686</link><guid isPermaLink="true">https://localaihub.com/post/686</guid><dc:creator><![CDATA[小周]]></dc:creator><pubDate>Wed, 06 May 2026 10:36:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 07:53:00 GMT]]></title><description><![CDATA[<p dir="auto">模型不是中文越强越懂你品牌。品牌语气要沉淀成示例和评测。</p>
]]></description><link>https://localaihub.com/post/685</link><guid isPermaLink="true">https://localaihub.com/post/685</guid><dc:creator><![CDATA[leaf_1997]]></dc:creator><pubDate>Wed, 06 May 2026 07:53:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 06:59:00 GMT]]></title><description><![CDATA[<p dir="auto">可以把输出结构固定：一句确认问题、一句处理动作、一句需要用户补充什么。不要开放长文。</p>
]]></description><link>https://localaihub.com/post/684</link><guid isPermaLink="true">https://localaihub.com/post/684</guid><dc:creator><![CDATA[阿宁]]></dc:creator><pubDate>Wed, 06 May 2026 06:59:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 06:25:00 GMT]]></title><description><![CDATA[<p dir="auto">我们用 GLM 做投标材料，正式感是优点；做客服邮件就要限制套话密度。</p>
]]></description><link>https://localaihub.com/post/683</link><guid isPermaLink="true">https://localaihub.com/post/683</guid><dc:creator><![CDATA[melo]]></dc:creator><pubDate>Wed, 06 May 2026 06:25:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 04:27:00 GMT]]></title><description><![CDATA[<p dir="auto">负例也有用。明确不要“感谢您的理解与支持”“造成不便深表歉意”这类空句，除非真需要。</p>
]]></description><link>https://localaihub.com/post/682</link><guid isPermaLink="true">https://localaihub.com/post/682</guid><dc:creator><![CDATA[nora]]></dc:creator><pubDate>Wed, 06 May 2026 04:27:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Wed, 06 May 2026 01:57:00 GMT]]></title><description><![CDATA[<p dir="auto">给风格样例比写形容词有效。放 3 封你们满意的邮件，让模型仿语气。</p>
]]></description><link>https://localaihub.com/post/681</link><guid isPermaLink="true">https://localaihub.com/post/681</guid><dc:creator><![CDATA[小曹]]></dc:creator><pubDate>Wed, 06 May 2026 01:57:00 GMT</pubDate></item><item><title><![CDATA[Reply to GLM 做企业材料写作，怎么避免全是公文味？ on Tue, 05 May 2026 23:19:00 GMT]]></title><description><![CDATA[<p dir="auto">先区分“正式”和“公文味”。客户邮件要清楚、尊重、具体，不一定要“特此说明”。</p>
]]></description><link>https://localaihub.com/post/680</link><guid isPermaLink="true">https://localaihub.com/post/680</guid><dc:creator><![CDATA[陈一]]></dc:creator><pubDate>Tue, 05 May 2026 23:19:00 GMT</pubDate></item></channel></rss>