团队频道发帖作者

文档 社区

技能解读

当前原文的自动摘译,尚未人工审校。

概述

创建结构良好的教育性 Teams 频道帖子,以共享有关 Claude Code 功能和最佳实践的内部知识。此技能提供模板、编写指南和结构化工作流程,以生成一致的、可操作的内容,帮助同事学习有效的克劳德代码用法。

何时使用此技能

创建 Teams 频道帖子时会激活此技能,以: 宣布并解释新的 Claude Code 功能 分享 Claude Code 技巧和最佳实践 教授有效的提示模式和工作流程 将功能与更广泛的工程原理联系起来(例如,上下文工程)

1. 理解主题

收集有关要写的内容的信息: 使用官方文档彻底研究功能/主题 从变更日志中验证发布日期和版本号 确定帖子应教授的核心优势或原则 从实际使用中收集具体示例

2. 规划内容

根据references/writing-guidelines.md中的写作指南,计划: Hook:这个主题有什么新的或重要的内容?核心原则:这说明了什么最佳实践?示例:哪些具体提示或工作流程证明了这一点?号召性用语:读者接下来应该尝试什么?

3. 使用模板起草

从assets/post-template.md中的模板开始并填写: 标题:使用表情符号和清晰的描述 简介:包括发布日期和简要上下文 它是什么:1-2 句话解释 如何使用它:显示“正常 vs 更好”模式并提供明确说明

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
文档
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@daymade · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
即装即用
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

# Teams Channel Post Writer

## 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.

## 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

## Workflow

### 1. Understand the Topic

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

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?

### 3. Draft Using the Template

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

### 4. Apply Writing Guidelines

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

### 5. Save and Share

Save the final post to your team's documentation location with a descriptive filename like "Claude Code Tips.md" or "[Topic Name].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.

### 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.

### 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
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
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.

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。