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.
84
78%
Does it follow best practices?
Impact
91%
1.62xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./teams-channel-post-writer/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted description that clearly defines a specific niche (educational Teams channel posts about Claude Code), lists concrete actions and deliverables, and provides explicit trigger conditions. It uses proper third-person voice throughout and includes natural keywords that users would employ when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating educational Teams channel posts, writing announcements, documentation, providing templates, writing guidelines, and structured approaches. Also specifies the domain clearly (Claude Code features, tools, best practices). | 3 / 3 |
Completeness | Clearly answers both 'what' (creates educational Teams channel posts, provides templates and writing guidelines for Claude Code knowledge sharing) and 'when' with explicit triggers ('Applies when writing posts, announcements...', 'Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'Teams channel posts', 'announcements', 'knowledge sharing', 'productivity tips', 'feature documentation', 'tip sharing', 'lessons learned', 'Claude Code'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining Teams channel posts specifically for Claude Code internal knowledge sharing. The intersection of Teams posts + Claude Code education + internal knowledge sharing is very specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-organized framework for writing Teams channel posts with good progressive disclosure to supporting files. However, it lacks concrete examples (no sample post, no 'Normal vs Better' demonstration) which significantly limits actionability. The workflow is clear but would benefit from explicit validation criteria and a revision feedback loop.
Suggestions
Add a concrete example of a completed post (or at least a substantial excerpt) showing the 'Normal vs Better' pattern and the expected output format, so Claude can see what a good result looks like.
Include a validation step in the workflow with specific pass/fail criteria (e.g., 'Does the post contain at least 3 concrete example prompts? Does it explain the underlying principle? Are all dates verified?') and an explicit revision loop.
Remove or condense the 'When to Use This Skill' section since it largely duplicates information Claude would already have from the skill's activation context, and trim the 'Key Principles' section which restates guidance already covered in the workflow steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation (e.g., the 'When to Use This Skill' section largely repeats what the description already conveys, and some principles like 'Verify Everything' and 'Show, Don't Just Tell' are things Claude already understands). However, it's not egregiously verbose—most sections carry useful structural information. | 2 / 3 |
Actionability | The skill provides a clear workflow and checklist structure, but lacks concrete executable examples. There are no actual example posts, no sample markdown output, and no copy-paste ready content. The guidance is specific in structure but abstract in substance—it tells Claude to 'show Normal vs Better patterns' without demonstrating one. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced and includes a research checklist, but lacks validation checkpoints. There's no step to verify the draft against quality criteria in a structured way (step 4 says 'review against the quality checklist' but doesn't define what passing looks like), and no feedback loop for revision if the draft doesn't meet standards. | 2 / 3 |
Progressive Disclosure | The skill appropriately structures content with a clear overview in the main file and well-signaled one-level-deep references to `references/writing-guidelines.md` and `assets/post-template.md`. Each reference includes a brief description of what it contains, making navigation easy. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- fernandezbaptiste/claude-code-skills
- Commit
4f0eae8
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.