Voice Builder
charlie947/social-media-skills
Build a personalised voice profile inside a Codex or Claude project from a short interview plus 3 to 5 sample pieces of writing.
Writes educational Teams channel posts about Claude Code features and best practices, using templates emphasizing concrete examples and underlying principles (e.g.
Install Teams Channel Post Writer
$ npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install daymade/claude-code-skills teams-channel-post-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/teams-channel-post-writer .claude/skills/teams-channel-post-writer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "teams-channel-post-writer" agent skill from https://github.com/daymade/claude-code-skills/tree/main/teams-channel-post-writer into .claude/skills/teams-channel-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-channel-post-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/daymade/claude-code-skills/tree/main/teams-channel-post-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install daymade/claude-code-skills teams-channel-post-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/teams-channel-post-writer .agents/skills/teams-channel-post-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "teams-channel-post-writer" agent skill from https://github.com/daymade/claude-code-skills/tree/main/teams-channel-post-writer into .agents/skills/teams-channel-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-channel-post-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install daymade/claude-code-skills teams-channel-post-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/teams-channel-post-writer .cursor/skills/teams-channel-post-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "teams-channel-post-writer" agent skill from https://github.com/daymade/claude-code-skills/tree/main/teams-channel-post-writer into .cursor/skills/teams-channel-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-channel-post-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/daymade/claude-code-skills.git --path teams-channel-post-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install daymade/claude-code-skills teams-channel-post-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/teams-channel-post-writer .gemini/skills/teams-channel-post-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "teams-channel-post-writer" agent skill from https://github.com/daymade/claude-code-skills/tree/main/teams-channel-post-writer into .gemini/skills/teams-channel-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-channel-post-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install daymade/claude-code-skills teams-channel-post-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/teams-channel-post-writer .github/skills/teams-channel-post-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "teams-channel-post-writer" agent skill from https://github.com/daymade/claude-code-skills/tree/main/teams-channel-post-writer into .github/skills/teams-channel-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-channel-post-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install daymade/claude-code-skills teams-channel-post-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/teams-channel-post-writer .opencode/skills/teams-channel-post-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "teams-channel-post-writer" agent skill from https://github.com/daymade/claude-code-skills/tree/main/teams-channel-post-writer into .opencode/skills/teams-channel-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-channel-post-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
teams-channel-post-writer- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 523 words
- Files
- 3 (incl. references, assets)
- Skills in repo
- 104
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes educational Teams channel posts about Claude Code features and best practices, using templates emphasizing concrete examples and underlying principles (e.g.
- Works in 5 steps: Understand the Topic → Plan the Content → Draft Using the Template → …
- Writing a Teams post
- SKILL.md covers Overview, When to Use This Skill, Workflow and Key Principles, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Teams Channel Post Writer is an agent skill from daymade/claude-code-skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files and assets (for example `assets/post-template.md` and `references/writing-guidelines.md`).
It sits in Agent Workflows, covering Social media posts, Context engineering and Brand voice and tone. The repository describes itself as: Professional Claude Code skills marketplace featuring production-ready skills for enhanced development workflows. The licence is MIT.
When your agent uses it
- Writing a Teams post
- Announcement to teach colleagues Claude Code usage
- Announce a feature
- Document a lesson learned
Example prompts
- “Use the teams-channel-post-writer skill to write educational Teams channel posts about Claude Code features and best practices, using templates…”
- “/teams-channel-post-writer”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 0e52df5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Teams Channel Post Writer loads about 1.1k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 523 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from daymade/claude-code-skills at commit 0e52df5, republished under its MIT licence (© daymade). 523 words, ~1,124 tokens.
Download SKILL.mdSave it as
.claude/skills/teams-channel-post-writer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- 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:
- Title: Use an emoji and clear description
- Introduction: Include release date and brief context
- What it is: 1-2 sentence explanation
- How to use it: Show "Normal vs Better" pattern with explicit instructions
- Why use it: Explain the underlying principle with 4 key benefits
- Examples: Provide 3+ realistic, concrete prompts
- Options/Settings: List key configurations or parameters
- Call-to-action: End with actionable next step
- Learn more: Link to authoritative resources
Show full SKILL.md (226 more words)Show less
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.
© daymade, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references, assets) in teams-channel-post-writer of daymade/claude-code-skills.
- SKILL.md
- assets/post-template.md
- references/writing-guidelines.md
Open the folder on GitHubat commit 0e52df5
Compare with similar skills
Teams Channel Post Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Teams Channel Post Writer this skilldaymade/claude-code-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Voice Buildercharlie947/social-media-skills | 3.8k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Content Writerchrispangg/deepagentsdk | 128 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Content Creatorthatrebeccarae/claude-marketing | 161 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Content Creatorsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Write Like Meng On Xnirholas/three.ws | 229 | 1 repos | ~2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Content Writer
chrispangg/deepagentsdk
Writing content across different platforms and styles. An agent skill from chrispangg/deepagentsdk.
Content Creator
thatrebeccarae/claude-marketing
Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning.
Content Creator
sickn33/agentic-awesome-skills
Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.
Write Like Meng On X
nirholas/three.ws
Write, rewrite, review, or continuously refine X/Twitter posts in Meng To's current voice using his deduplicated authored-post corpus, personal and product context, shared resources, and Content…
Write
waynesutton/markdown-site
Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation.
More from daymade/claude-code-skills
All 104 skills in this repoVideo Comparer
daymade/claude-code-skills
This skill should be used when comparing two videos to analyze compression results or quality differences.
CLI Demo Generator
daymade/claude-code-skills
Generates professional animated CLI demos as GIFs using VHS terminal recordings.
Doc To Markdown
daymade/claude-code-skills
Converts DOCX/PDF/PPTX and saved HTML/HTM to high-quality Markdown with automatic post-processing.
Interaction Design Board
daymade/claude-code-skills
Generates several distinct, clickable HTML interaction prototypes for one product surface into a Design Board and collects selection/remix feedback before implementation.
Skill Creator
daymade/claude-code-skills
Creates, edits and benchmarks skills; supersedes the official skill-creator plugin, so when both are listed, use this one.
Auto Repo Setup
daymade/claude-code-skills
Diagnoses and repairs repository setup and guarded Git workflows for Claude Code or Codex — environment repair, startup sync, hook auditing, collaborator handoff.
Related
Categories
Questions about Teams Channel Post Writer
What does Teams Channel Post Writer do?
Writes educational Teams channel posts about Claude Code features and best practices, using templates emphasizing concrete examples and underlying principles (e.g. Teams Channel Post Writer is an agent skill from daymade/claude-code-skills.g.
When should I use Teams Channel Post Writer?
Teams Channel Post Writer fits situations like: writing a Teams post; announcement to teach colleagues Claude Code usage; announce a feature; document a lesson learned.
How do I install Teams Channel Post Writer in Claude Code?
Run `npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a claude-code`. Or copy the skill folder (teams-channel-post-writer in daymade/claude-code-skills) into .claude/skills/teams-channel-post-writer in your project. Claude Code loads it when a task matches its description.
How do I install Teams Channel Post Writer in Codex?
Run `npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a codex`. Or copy the skill folder (teams-channel-post-writer in daymade/claude-code-skills) into .agents/skills/teams-channel-post-writer in your project. Codex loads it when a task matches its description.
Can I use Teams Channel Post Writer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add daymade/claude-code-skills --skill teams-channel-post-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/teams-channel-post-writer, .gemini/skills/teams-channel-post-writer, .github/skills/teams-channel-post-writer and .opencode/skills/teams-channel-post-writer in your project.
What does Teams Channel Post Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: Teams Channel Post Writer is instructions for the agent only.
Does Teams Channel Post Writer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Teams Channel Post Writer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Teams Channel Post Writer use?
Teams Channel Post Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Teams Channel Post Writer use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 699 tokens, read only when the agent opens those files.
What are the alternatives to Teams Channel Post Writer?
Skills that share tags, products or a category with Teams Channel Post Writer: Voice Builder (charlie947/social-media-skills, 3.8k stars), Content Writer (chrispangg/deepagentsdk, 128 stars), Content Creator (thatrebeccarae/claude-marketing, 161 stars) and Content Creator (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Teams Channel Post Writer?
daymade (a GitHub user) maintains it in daymade/claude-code-skills, which has 1,448 GitHub stars. The repository holds 104 skills in this directory. The repository was last updated on October 10, 2026.
Source: daymade/claude-code-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.