SkillAgentSearch skills...

teams-channel-post-writer

Writes educational Teams channel posts about Claude Code features and best practices, using templates emphasizing concrete examples and underlying principles (e.g. context engineering)

Install / Use

npx skills add daymade/claude-code-skills --skill teams-channel-post-writer

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Claude Code

Tags

Our assessment of teams-channel-post-writer

teams-channel-post-writer scores 82/100 on our quality scale, 972nd of 1,155 Content & Media skills we index.

Its SKILL.md is 4.4 KB long, well organised into 17 sections and no code examples: a solid amount of guidance for an agent.

With 1,426 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so teams-channel-post-writer is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

teams-channel-post-writer compared with similar skills

All 4 of these similar skills score higher than teams-channel-post-writer; compare them before choosing.

SkillScoreStarsUpdatedFormat
teams-channel-post-writer (this skill)by daymade821.4k53d agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install teams-channel-post-writer?
Run npx skills add daymade/claude-code-skills --skill teams-channel-post-writer. The install tabs above show the steps for each supported agent.
Which AI agents does teams-channel-post-writer work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is teams-channel-post-writer safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is teams-channel-post-writer still maintained?
The repository was last updated about 2 months ago, so teams-channel-post-writer is actively maintained.

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

Related Skills

View on GitHub
GitHub Stars1.4k
CategoryContent
Updated1mo ago
Forks219

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions