360 Secure SkillHub
360 安全技能中心

Poe UMG 4o Modular Speech Style

核心功能:仅调整内容呈现形式不改变原意,通过分设带emoji的章节、控制短段落、合理使用列表等方式,提升窄屏聊天场景的可读性。典型使用场景:用户提出格式化、整理、优化可读性、模块化内容等需求时激活。输出遵循规范:章节配emoji短标题,段落1-3句,按需用列表,适度强调关键信息,避免过度格式化。

neomagnetar
neomagnetar
热度 19.49
最近更新 2026-03-26 23:31:55
分类:效率依赖:纯提示词应用场景:模板 / 文件转换

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add poe-umg-4o-modular-speech
Metadata
name
poe-umg-4o-modular-speech
description
Render responses in a structured, modular GPT-4o-derived UMG speech style for highly readable chat output.
version
1.0.0
metadata
{"openclaw":{"emoji":"🧱","skillKey":"poe-umg-4o-modular-speech"}}

Poe UMG 4o Modular Speech Style

Use this skill when the user wants a response reformatted into a clear, readable, modular speech style.

Purpose

This skill changes presentation, not meaning.

It reshapes output into:

  • sectioned structure
  • short paragraphs
  • visible hierarchy
  • scan-friendly bullets or numbered steps
  • strong readability in narrow chat layouts

Activation cues

Prefer this skill when the user says things like:

  • format this
  • make this structured
  • clean this up
  • organize this
  • modularize this
  • improve readability
  • rewrite clearly
  • apply poe style

Rendering rules

1. Section architecture

  • Break the response into sections.
  • Each major section should begin with exactly one emoji and a short title.
  • Keep titles clear and compact.

2. Paragraph control

  • Keep paragraphs short: 1 to 3 sentences.
  • Avoid wall-of-text output.
  • Use vertical spacing between paragraphs.

3. Structure usage

  • Use bullet lists for grouped ideas.
  • Use numbered lists for sequences or steps.
  • Use tables only when comparison is clearer than bullets.

4. Rhythm

Alternate naturally between:

  • short explanation
  • structure
  • short explanation

5. Emphasis

  • Use bold only for load-bearing ideas.
  • Use italics sparingly for nuance.
  • Avoid decorative over-formatting.

6. Density

  • Prefer more sections over dense blocks.
  • Keep the output readable in a chat-width column.

7. Closing

  • End important sections with a short takeaway line when helpful.

Fail conditions

Do not:

  • output one giant paragraph
  • overuse emojis
  • place emojis inline casually
  • over-format every sentence
  • change the user's meaning

Minimal response template

🧩 Section Title

Short framing paragraph.

  • Point one
  • Point two
  • Point three

Short closing line.

Operating note

This is a rendering layer for clarity and structure.