openclaw-skills/teams-channel-post-writer/SKILL.md
Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.
npx skillsauth add seaworld008/commonly-used-high-value-skills teams-channel-post-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
This skill activates when creating Teams channel posts to:
Gather information about what to write about:
Research checklist:
Based on the writing guidelines in references/writing-guidelines.md, plan:
Start with the template in assets/post-template.md and fill in:
Review the draft against the quality checklist in references/writing-guidelines.md:
Save the final post to your team's documentation location with a descriptive filename like "Claude Code Tips.md" or "[Topic Name].md"
Always include concrete examples users can adapt. Use "Normal vs Better" comparisons to demonstrate improvements without making readers feel criticized.
Don't just describe features—explain the underlying best practices. For example, connect the Explore agent to "context offloading" principles in context engineering.
Be explicit about invocation patterns. Users should be able to copy/paste examples and immediately use them.
Always research release dates, verify feature behavior, and link to authoritative sources. Accuracy builds trust.
Comprehensive writing guidelines including:
Reference this file for detailed guidance on tone, structure, and quality standards.
Ready-to-use markdown template with placeholder structure for:
Copy this template as a starting point for new posts, then customize the content while maintaining the proven structure.
# Tip: Use Explore Agents for Faster Context Gathering
What it is:
- Explore agents let you parallelize repo discovery without bloating the main thread.
Normal:
- "Read these ten files and summarize them."
Better:
- "Spawn 3 focused explore passes: routing, data model, and tests. Return only risks and key files."
Why it helps:
- Keeps context lean
- Surfaces contradictions sooner
- Produces cleaner handoff notes
development
Enumerating failure modes via pre-mortem analysis. Systematically identifies failure scenarios for plans, designs, and features, scoring them with RPN/AP. Does not write code.
testing
Orchestrating specialist AI agent teams as a meta-coordinator. Decomposes requests into minimum viable chains, spawns each as an independent session in AUTORUN modes, and drives to final output. Use when a task spans multiple specialist domains, requires parallel agent execution, or needs hub-and-spoke routing across the skill ecosystem.
development
Converting document formats (Markdown/Word/Excel/PDF/HTML). Converts specs from Scribe and reports from Harvest into distributable formats; generates reusable conversion scripts. Use when converting documents, building accessibility-compliant PDFs, or creating Pandoc/LibreOffice pipelines.
testing
Curating cross-agent knowledge and guarding institutional memory. Extracts patterns from agent journals into METAPATTERNS.md, detects knowledge decay, propagates best practices, prevents organizational forgetting. Use when consolidating cross-agent insights, curating memory, or auditing knowledge decay.