teams-channel-post-writer
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.
What this skill does
# 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 in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.