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.
88
85%
Does it follow best practices?
Impact
91%
1.62xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 its purpose (educational Teams posts about Claude Code), provides specific actions and deliverables (templates, guidelines, structured approaches), and includes explicit trigger conditions. The description effectively distinguishes itself through the combination of platform (Teams), audience (colleagues), and subject matter (Claude Code features and best practices).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Creates educational Teams channel posts', 'writing posts, announcements, or documentation', 'announce new features, share productivity tips, document lessons learned', 'Provides templates, writing guidelines, and structured approaches'. | 3 / 3 |
Completeness | Clearly answers both what ('Creates educational Teams channel posts', 'Provides templates, writing guidelines') AND when ('Applies when writing posts...', 'Activates for content involving Teams posts, channel announcements'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Teams posts', 'channel announcements', 'feature documentation', 'tip sharing', 'knowledge sharing', 'Claude Code', 'best practices', 'productivity tips'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Teams channel posts + Claude Code education + internal knowledge sharing. Unlikely to conflict with generic documentation or communication skills due to the specific platform and subject matter focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has strong structural organization and workflow clarity, with appropriate progressive disclosure to external reference files. However, it lacks concrete, copy-paste-ready examples within the skill itself—the actionable content is deferred to external templates. The skill would benefit from including at least one complete example post or concrete prompt patterns inline.
Suggestions
Include at least one concrete example of a 'Normal vs Better' comparison directly in the skill rather than only referencing the template
Add a brief inline example of what a completed post section looks like (e.g., a sample 'What it is' + 'How to use it' snippet)
Remove or condense the 'When to Use This Skill' section—the bullet points largely repeat what's already clear from the overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation (e.g., 'This skill activates when...' section lists obvious use cases) and could be tightened, but overall avoids excessive verbosity and doesn't over-explain concepts Claude already knows. | 2 / 3 |
Actionability | Provides a clear workflow and references templates/guidelines, but lacks concrete examples within the skill itself. The actual templates and examples are deferred to external files, making the skill more of a pointer than executable guidance. | 2 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit checkpoints including a research checklist with verification items. Steps are well-sequenced and include validation (step 4 reviews against quality checklist) before final output. | 3 / 3 |
Progressive Disclosure | Excellent structure with overview, workflow, key principles, and resources clearly separated. References to external files (writing-guidelines.md, post-template.md) are one level deep and well-signaled with descriptions of what each contains. | 3 / 3 |
Total | 10 / 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
- daymade/claude-code-skills
- Commit
392d34c
- 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.