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

77%

Does it follow best practices?

Impact

91%

1.62x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./teams-channel-post-writer/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

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

A well-structured, actionable instructional skill with a clear workflow and appropriately split references, verified against the real bundle files. The main weakness is redundancy between the workflow, Key Principles, and Resources sections that could be tightened to improve token efficiency.

Suggestions

Collapse the 'Key Principles' section into the corresponding workflow steps (or remove it), since 'Show, Don't Just Tell', 'Make it Actionable', and 'Verify Everything' already appear in steps 2-5 and the writing-guidelines checklist.

Trim the Resources section so it only signals what each bundle file covers and when to read it, rather than re-listing the writing-guidelines contents that are already summarized in step 4.

Add one short inline example post (or a representative 'Normal/Better' prompt pair) in the Draft step so the guidance is fully copy-paste ready without opening the template first.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but the 'Key Principles' section restates workflow guidance ('Show, Don't Just Tell', 'Make it Actionable', 'Verify Everything') and the Resources section re-describes the writing-guidelines file already referenced inline, matching anchor 3 'could be tightened'.	3 / 5
Actionability	As an instruction-only skill it gives concrete, executable guidance (numbered template-fill steps, an explicit research checklist, 'Normal vs Better' pattern, 3+ example prompts) and points to real template/guideline files; matches anchor 4 'mostly executable guidance... with minor gaps' since no inline example post is shown.	4 / 5
Workflow Clarity	A clear 5-step sequence (Understand, Plan, Draft, Apply Guidelines, Save) with a research checklist in step 1 and a review checkpoint in step 4; matches anchor 4 'clear sequence with most checkpoints present; minor validation gaps' rather than 5 because there is no explicit validate-fix-retry loop.	4 / 5
Progressive Disclosure	The body is an overview pointing to two real, one-level-deep bundle files (references/writing-guidelines.md and assets/post-template.md) with a dedicated Resources section; matches anchor 4 'good structure; references mostly clear' rather than 5 because the inline re-description of the guidelines file's contents adds slight redundancy.	4 / 5
	Total	15 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does and when it should activate, with multiple concrete actions and natural trigger terms. Minor specificity gaps prevent a perfect score on the capability and trigger dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Creates educational Teams channel posts', 'teach colleagues', 'announce new features', 'share productivity tips', 'document lessons learned', 'Provides templates, writing guidelines') matching anchor 4's 'several specific actions; minor gaps'; falls short of 5 because some actions describe post content rather than distinct skill capabilities.	4 / 5
Completeness	Explicitly answers both 'what' ('Creates educational Teams channel posts... Provides templates, writing guidelines, and structured approaches') and 'when' with two concrete trigger clauses ('Applies when writing posts, announcements...', 'Activates for content involving Teams posts...'), matching anchor 5.	5 / 5
Trigger Term Quality	Natural terms a user would say are well covered ('Teams posts', 'channel announcements', 'feature documentation', 'tip sharing', 'productivity tips'); matches anchor 4 'good keyword coverage; a few natural terms missing' and does not reach 5 only because no synonyms/extensions meaningfully apply.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Teams channel posts about Claude Code) with distinct triggers and consistent third-person voice, giving minimal overlap risk with other skills, matching anchor 5.	5 / 5
	Total	18 / 20 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
Path: teams-channel-post-writer/SKILL.md
Commit: b8556f2

Reviewed: 3 days 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.