Back to Details

teams-channel-post-writer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Teams Channel Post Writer

Teams频道帖子撰写工具

Overview

概述

Create well-structured, educational Teams channel posts for internal knowledge sharing about Claude Code features and best practices. This skill provides templates, writing guidelines, and a structured workflow to produce consistent, actionable content that helps colleagues learn effective Claude Code usage.
创建结构清晰、用于内部知识共享的教育类Teams频道帖子，内容围绕Claude Code的功能和最佳实践。本技能提供模板、写作指南和结构化工作流，帮助产出一致、实用的内容，助力同事学习如何有效使用Claude Code。

When to Use This Skill

适用场景

This skill activates when creating Teams channel posts to:
  • Announce and explain new Claude Code features
  • Share Claude Code tips and best practices
  • Teach effective prompting patterns and workflows
  • Connect features to broader engineering principles (e.g., context engineering)
  • Document lessons learned from using Claude Code
当你需要创建以下类型的Teams频道帖子时，可使用本技能：
  • 宣布并讲解Claude Code的新功能
  • 分享Claude Code的使用技巧和最佳实践
  • 教授有效的提示词模式和工作流
  • 将功能与更广泛的工程原理（如上下文工程）关联起来
  • 记录使用Claude Code过程中总结的经验教训

Workflow

工作流

1. Understand the Topic

1. 理解主题

Gather information about what to write about:
  • Research the feature/topic thoroughly using official documentation
  • Verify release dates and version numbers from changelogs
  • Identify the core benefit or principle the post should teach
  • Collect concrete examples from real usage
Research checklist:
  • Found official release date/version number
  • Verified feature behavior through testing or documentation
  • Identified authoritative sources to link to
  • Understood the underlying principle or best practice
收集要撰写内容的相关信息：
  • 利用官方文档深入研究功能/主题
  • 从更新日志中核实发布日期和版本号
  • 确定帖子要传授的核心价值或原理
  • 收集实际使用中的具体示例
研究清单：
  • 找到官方发布日期/版本号
  • 通过测试或文档验证功能行为
  • 确定可链接的权威来源
  • 理解底层原理或最佳实践

2. Plan the Content

2. 规划内容

Based on the writing guidelines in 
references/writing-guidelines.md
, plan:
  • Hook: What's new or important about this topic?
  • Core principle: What best practice does this illustrate?
  • Examples: What concrete prompts or workflows demonstrate this?
  • Call-to-action: What should readers try next?
根据
references/writing-guidelines.md
中的写作指南，规划以下内容：
  • 钩子：本主题有哪些新内容或重要信息？
  • 核心原理：这体现了哪项最佳实践？
  • 示例：哪些具体的提示词或工作流可以演示这一点？
  • 行动号召：读者接下来应该尝试什么？

3. Draft Using the Template

3. 使用模板撰写初稿

Start with the template in 
assets/post-template.md
and fill in:
  1. Title: Use an emoji and clear description
  2. Introduction: Include release date and brief context
  3. What it is: 1-2 sentence explanation
  4. How to use it: Show "Normal vs Better" pattern with explicit instructions
  5. Why use it: Explain the underlying principle with 4 key benefits
  6. Examples: Provide 3+ realistic, concrete prompts
  7. Options/Settings: List key configurations or parameters
  8. Call-to-action: End with actionable next step
  9. Learn more: Link to authoritative resources
以
assets/post-template.md
中的模板为基础，填写以下内容：
  1. 标题：使用表情符号和清晰的描述
  2. 引言：包含发布日期和简要背景
  3. 是什么：1-2句话的解释
  4. 如何使用：展示“普通用法 vs 优化用法”模式，并给出明确说明
  5. 为什么使用：结合4个核心优势解释底层原理
  6. 示例：提供3个以上真实、具体的提示词
  7. 选项/设置：列出关键配置或参数
  8. 行动号召：以可执行的下一步操作结尾
  9. 了解更多：链接到权威资源

4. Apply Writing Guidelines

4. 遵循写作指南

Review the draft against the quality checklist in 
references/writing-guidelines.md
:
  • Educational and helpful tone
  • "Normal/Better" pattern (not "Wrong/Correct")
  • Concrete, realistic examples
  • Explains the "why" with principles
  • Clear structure with bullets and formatting
  • Verified facts and dates
对照
references/writing-guidelines.md
中的质量清单审核初稿：
  • 语气兼具教育性和实用性
  • 使用“普通用法 vs 优化用法”模式（而非“错误 vs 正确”）
  • 具体、真实的示例
  • 结合原理解释“为什么”
  • 结构清晰，使用项目符号和格式
  • 核实事实和日期的准确性

5. Save and Share

5. 保存并分享

Save the final post to your team's documentation location with a descriptive filename like "Claude Code Tips.md" or "[Topic Name].md"
将最终帖子保存到团队的文档位置，使用描述性文件名，如“Claude Code Tips.md”或“[主题名称].md”

Key Principles

核心原则

Show, Don't Just Tell

展示而非说教

Always include concrete examples users can adapt. Use "Normal vs Better" comparisons to demonstrate improvements without making readers feel criticized.
始终包含用户可以直接借鉴的具体示例。使用“普通用法 vs 优化用法”的对比来展示改进，避免让读者感到被批评。

Connect to Principles

关联至原理

Don't just describe features—explain the underlying best practices. For example, connect the Explore agent to "context offloading" principles in context engineering.
不要仅描述功能——要解释背后的最佳实践。例如，将Explore agent与上下文工程中的“上下文卸载”原理关联起来。

Make it Actionable

确保可执行

Be explicit about invocation patterns. Users should be able to copy/paste examples and immediately use them.
明确说明调用模式。用户应该能够复制示例并立即使用。

Verify Everything

核实所有信息

Always research release dates, verify feature behavior, and link to authoritative sources. Accuracy builds trust.
务必研究发布日期、验证功能行为，并链接到权威来源。准确性建立信任。

Resources

资源

references/writing-guidelines.md

references/writing-guidelines.md

Comprehensive writing guidelines including:
  • Tone and style standards
  • Structure patterns for different post types
  • Formatting conventions
  • Research requirements
  • Quality checklist
Reference this file for detailed guidance on tone, structure, and quality standards.
全面的写作指南，包括：
  • 语气和风格标准
  • 不同类型帖子的结构模式
  • 格式规范
  • 研究要求
  • 质量清单
参考此文件获取有关语气、结构和质量标准的详细指导。

assets/post-template.md

assets/post-template.md

Ready-to-use markdown template with placeholder structure for:
  • Title and introduction
  • Feature explanation
  • Usage examples
  • Benefits and principles
  • Options and settings
  • Call-to-action and resources
Copy this template as a starting point for new posts, then customize the content while maintaining the proven structure.
即用型Markdown模板，包含以下占位符结构：
  • 标题和引言
  • 功能说明
  • 使用示例
  • 优势和原理
  • 选项和设置
  • 行动号召和资源
复制此模板作为新帖子的起点，然后自定义内容，同时保留经过验证的结构。