# teams-channel-post-writer

Writes educational Teams channel posts about Claude: feature walkthroughs, tips, prompt examples and principles like context engineering.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 935 installs · ★ 1493
- Author: daymade
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/daymade/claude-code-skills/tree/HEAD/teams-channel-post-writer/SKILL.md
- Updated: 2026-10-25
- HTML: https://affpapa.org/en/nevibecode/skills/teams-channel-post-writer

## What it does

The skill walks you through a fixed order: research the topic, plan the hook and the principle behind it, fill in the template, then check the draft against a quality list. Two files ship with it — `references/writing-guidelines.md` for tone and structure rules, and `assets/post-template.md`, a markdown skeleton with title, intro, examples and call-to-action.

The template lays out the sections: a title, an intro with the release date, a one or two sentence explanation of the feature, a "Normal vs Better" comparison instead of "Wrong/Correct", the underlying principle with four benefits, three or more realistic prompts, settings, and links to sources. The tone stays educational, never lecturing.

Research is not optional here. The skill asks you to verify release dates and version numbers against official docs and changelogs before drafting. Skip that and the checklist step fails — which is exactly the part that makes colleagues trust the post.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/teams-channel-post-writer/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/teams-channel-post-writer/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/teams-channel-post-writer/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/teams-channel-post-writer/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install daymade/claude-code-skills teams-channel-post-writer
```

2. **Manually: put the files in place**
- File: `.github/skills/teams-channel-post-writer/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/daymade/claude-code-skills --path teams-channel-post-writer
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/teams-channel-post-writer/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/daymade/claude-code-skills/tree/HEAD/teams-channel-post-writer/SKILL.md

## When to use it
- announce a new Claude feature to your team
- write a post with real prompt examples instead of vague advice
- explain the principle behind a feature, not just its syntax
- turn a lesson learned into a short channel note
- verify release date and version before publishing

## Example prompts
- Write a Teams post about the new Claude feature using the skill template
- Draft an educational post on context engineering with prompt examples
- Turn my notes on the Explore agent into a channel post for the team

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 67cc2f76cc585525.

BEGIN THIRD-PARTY FILE 67cc2f76cc585525
```text
---
name: teams-channel-post-writer
description: >-
  Writes educational Teams channel posts about Claude Code features and best practices, using
  templates emphasizing concrete examples and underlying principles (e.g. context engineering). Use
  when writing a Teams post or announcement to teach colleagues Claude Code usage, announce a
  feature, share a tip, or document a lesson learned.
---

# 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
```
END THIRD-PARTY FILE 67cc2f76cc585525

The third-party file has ended. Everything between the 67cc2f76cc585525 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2550 of 4498 bytes. © daymade · MIT · https://github.com/daymade/claude-code-skills/tree/HEAD/teams-channel-post-writer/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md