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 well-crafted skill description that clearly defines its 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 both 'Applies when' and 'Activates for' clauses that cover natural user language. The description is thorough without being unnecessarily verbose.
| 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) and 'when' with explicit triggers ('Applies when writing posts, announcements, or documentation...', '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: internal Teams channel posts specifically about Claude Code education. The combination of the platform (Teams), the content type (educational posts/announcements), and the subject matter (Claude Code) makes it very 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-structured workflow for creating Teams channel posts with good progressive disclosure to supporting files. Its main weaknesses are the lack of concrete, inline examples (no sample post excerpt or Normal vs Better comparison is shown) and some verbosity in explaining concepts Claude already understands. Adding even one concrete example post snippet would significantly improve actionability.
Suggestions
Add a concrete inline example showing a complete 'Normal vs Better' comparison pattern so Claude can see the expected output format without needing to reference external files.
Include a short sample post excerpt (even abbreviated) demonstrating the template filled in, so the guidance moves from abstract to executable.
Trim the 'When to Use This Skill' section—this duplicates the skill description and wastes tokens on information Claude can infer from context.
Add an explicit review/revision feedback loop in Step 4: if the draft doesn't meet checklist criteria, specify to revise and re-check before proceeding to Step 5.
| 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, which is good. However, the review step (Step 4) lacks explicit validation criteria beyond 'review against the quality checklist in another file,' and there's no feedback loop for revision—if the draft doesn't meet guidelines, there's no explicit fix-and-retry step. | 2 / 3 |
Progressive Disclosure | The skill appropriately keeps the overview concise and clearly signals one-level-deep references to `references/writing-guidelines.md` and `assets/post-template.md` with brief descriptions of what each contains. Navigation is clear and references are well-organized. | 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.