Teams Channel Post Writer

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.

🎯 [Title]: [Feature/Tool Name]

New in [Tool Name] ([Date]): Brief introduction of what this is about.

What is it? [1-2 sentence explanation of the feature/tool/concept]

How to use it - BE EXPLICIT:

📝 Normal: "[Example of typical approach]"

⭐ Better: "[Example of improved approach with explicit instructions]"

Why use it? ([Key Principle/Best Practice]) [Explanation of the underlying principle or best practice]

• Benefit 1: Explanation
• Benefit 2: Explanation
• Benefit 3: Explanation
• Benefit 4: Explanation

[Optional analogy or comparison to make the concept relatable]

Example prompts:

"[Example 1]"

"[Example 2]"

"[Example 3]"

Key settings/levels/options:

• option1 - Description
• option2 - Description (recommended)
• option3 - Description

Try it next time you [call to action]!

Learn more: [Link to additional resources]

Teams Channel Post Writing Guidelines

Purpose

These posts are internal educational content to help team members learn effective Claude Code usage patterns and best practices.

Tone and Style

• Educational and helpful: Focus on teaching concepts, not just announcing features
• Professional but approachable: Conversational without being too casual
• Action-oriented: Include concrete examples and calls-to-action
• Concise: Keep posts scannable - use short paragraphs and bullet points

Structure Principles

1. Start with Context

• Always include release date or timing information when relevant
• Lead with what the feature/tool is and why it matters

2. Show, Don't Just Tell

• Use "Normal vs Better" comparisons instead of "Wrong vs Correct"
• Include 3+ concrete example prompts users can adapt
• Provide realistic use cases from actual development workflows

3. Explain the "Why"

• Connect features to broader best practices (e.g., context engineering)
• Use analogies to make technical concepts relatable
• Link to authoritative external resources when applicable

4. Make it Actionable

• Be explicit about how to invoke features
• Specify any options, settings, or parameters
• End with a clear call-to-action

Content Patterns

Feature Announcements

1. What is it? (with release date)
2. Why use it? (principles/benefits)
3. How to use it (with examples)
4. Key options/settings
5. Call-to-action + learn more

Best Practices/Tips

1. The challenge/problem
2. The solution/approach
3. Why it works (principles)
4. How to implement (examples)
5. When to use it
6. Related resources

Formatting Standards

• Emojis: Use sparingly and only in titles (🔍 🎯 💡 ⚡)
• Bold: Use for emphasis on key terms and section headers
• Code blocks: Use for example prompts (triple backticks or quotes)
• Lists: Use bullets for benefits/features, numbers for sequential steps
• Comparisons: Use 📝 for "Normal" and ⭐ for "Better"

Research Requirements

Before writing any post: 1. Verify release dates: Use official documentation or changelog 2. Test the feature: Ensure examples work as described 3. Find authoritative sources: Link to official docs or reputable technical blogs 4. Check for updates: Ensure information is current

Quality Checklist

• [ ] Includes specific release date or timing
• [ ] Explains the "why" with principles or best practices
• [ ] Provides 3+ concrete, realistic examples
• [ ] Uses "Normal/Better" pattern (not "Wrong/Correct")
• [ ] Includes clear call-to-action
• [ ] Links to additional learning resources
• [ ] Uses professional, educational tone
• [ ] Is scannable with clear structure
• [ ] All facts verified against official sources