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.

1.62x

Quality

—

Does it follow best practices?

Impact

91%

1.62x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with a clear workflow and excellent progressive disclosure via real, well-signaled bundle files. Its main weaknesses are redundancy that inflates length and a lack of a complete worked example to anchor the actionable guidance.

Suggestions

Remove redundancy: cut the Key Principles section (it restates the workflow and quality checklist) and merge the Resources section into the inline references rather than re-describing each file's contents.

Add one complete, filled-in example Teams post in references/ or assets/ so the '3+ concrete prompts' and 'Normal vs Better' guidance is demonstrated rather than only prescribed.

Trim 'When to Use This Skill' so it does not restate the frontmatter triggers verbatim, keeping the body focused on how to execute the task.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concept-overexplaining, but carries redundancy: the Key Principles section restates workflow guidance ('Show, Don't Just Tell', 'Verify Everything'), the Resources section re-describes files already cited inline, and 'When to Use' overlaps the frontmatter triggers.	2 / 3
Actionability	Provides a concrete 9-section fill-in structure, a copy-paste template skeleton, and checklists, but includes no complete worked example post and several directives remain abstract ('Explain the underlying principle', 'Provide 3+ realistic, concrete prompts' without a demonstration).	2 / 3
Workflow Clarity	A clearly sequenced 5-step process (Understand, Plan, Draft, Apply Guidelines, Save) backed by a research checklist and a referenced quality checklist; this is content authoring rather than a destructive/batch operation, so the checklists suffice as validation checkpoints.	3 / 3
Progressive Disclosure	SKILL.md is an overview pointing to two real, one-level-deep, clearly signaled bundle files (references/writing-guidelines.md and assets/post-template.md), both verified to exist, with easy navigation and no nested reference chains.	3 / 3
	Total	10 / 12 Passed

Description

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.

The description is strong: third-person, specific, with explicit what/when triggers and natural keywords. It clearly communicates a distinct niche and is unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in third person ('Creates educational Teams channel posts', 'Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles'), matching the anchor for naming several specific actions.	3 / 3
Completeness	Explicitly answers both what ('Creates educational Teams channel posts... Provides templates, writing guidelines, and structured approaches') and when ('Applies when writing posts, announcements... Activates for content involving Teams posts...'), satisfying the explicit-trigger anchor.	3 / 3
Trigger Term Quality	Covers natural terms a user would say ('Teams posts, channel announcements, feature documentation, tip sharing', 'announcements', 'productivity tips', 'lessons learned'), giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	A clear niche (internal Teams channel posts about Claude Code usage) with distinct triggers ('Teams posts, channel announcements'), making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: daymade/claude-code-skills
Commit: e5ac7ba

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.