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.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/claude-code-skills --skill teams-channel-post-writer88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 its specific 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 excellent structure and workflow clarity with well-organized progressive disclosure to external resources. However, it suffers from being somewhat abstract—it describes what to do without showing concrete examples of actual post content, relying heavily on external template and guidelines files. The skill would benefit from inline examples demonstrating the 'Normal vs Better' pattern it recommends.
Suggestions
Add a concrete inline example showing a 'Normal vs Better' comparison for a Claude Code feature, rather than just describing the pattern
Include a brief sample of what a completed post section looks like (e.g., a real 'What it is' + 'How to use it' example) so users can see the expected output
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
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation (e.g., 'This skill activates when...' section restates the description) and could be tightened. The workflow steps are reasonably efficient but include some padding like 'Gather information about what to write about' before the actual checklist. | 2 / 3 |
Actionability | The skill provides structure and checklists but lacks concrete examples of actual post content. It references external files (post-template.md, writing-guidelines.md) for the actual actionable content rather than including executable examples directly. The 'Normal vs Better' pattern is mentioned but never demonstrated. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit checkpoints (research checklist with checkboxes, quality checklist reference in step 4). Each step has clear deliverables and the process flows logically from research through drafting to review and sharing. | 3 / 3 |
Progressive Disclosure | Content is well-organized with a clear overview, workflow steps, key principles, and resources section. External references (writing-guidelines.md, post-template.md) are one level deep and clearly 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.
- 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.