pm-weekly-brief

Read your Slack mentions, calendar events, and recently modified Drive documents from the last 7 days and synthesize them into a short personal PM summary. Use at the end of each week to capture what happened before it fades.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A compact, well-structured, and highly actionable single-purpose skill whose prompt template is concrete and copy-paste ready. The only real weakness is minor narrative padding in the intro and Tips that could be trimmed without losing clarity.

Suggestions

Tighten the intro paragraph ('By Friday you've had 30 meetings, 200 Slack messages...') to a single sentence that states the purpose without restating the description, to lift conciseness to the top anchor.

Consider trimming the Tips section to the single highest-value tip, since the rest is soft advice rather than executable guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but includes light narrative padding ('By Friday you've had 30 meetings, 200 Slack messages, and a handful of docs updated') that restates the description with color Claude does not strictly need, plus a Tips section with soft advice.	2 / 3
Actionability	The prompt template is copy-paste ready with concrete section instructions, specific rules ('Keep the whole brief under 400 words'), a concrete output filename pattern ('PM-Brief-YYYY-MM-DD.md'), and an explicit return-link step.	3 / 3
Workflow Clarity	As a single-task skill under 50 lines, its read-three-sources-then-synthesize flow is unambiguous and well-sequenced with explicit fallback handling ('Nothing notable this week'); no destructive or batch operation requires validation checkpoints.	3 / 3
Progressive Disclosure	The body is short and self-contained with well-organized sections (Prompt Template, Setup, Placeholders, Tips); no bundle files exist, and per the rubric's simple-skill rule a well-organized short skill qualifies for the top score.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 well-crafted description that clearly states what the skill does, when to use it, and lists natural trigger phrases, making it highly discoverable and distinct. Its only weakness is the use of second-person voice ('your', 'you'), which the rubric penalizes on specificity.

Suggestions

Rewrite the description in third person ('Reads Slack mentions, calendar events, and recently modified Drive documents... and synthesizes them...') to avoid the second-person voice penalty and recover the specificity score.

Dimension	Reasoning	Score
Specificity	The description lists several concrete data sources and a clear synthesis action ('Read your Slack mentions, calendar events, and recently modified Drive documents from the last 7 days and synthesize them into a short personal PM summary'), but it is written in second person ('your', 'you'), which the rubric penalizes by reducing the specificity score by one.	2 / 3
Completeness	It explicitly answers both what ('synthesize them into a short personal PM summary') and when ('Use at the end of each week to capture what happened before it fades'), plus a full trigger list, matching the 'Use when...' anchor.	3 / 3
Trigger Term Quality	The suggest_when field provides multiple natural phrases users would actually say ('weekly brief', 'week in review', 'summarize my week', 'what happened this week', 'PM summary'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The personal PM week-in-review niche pulling from Slack, calendar, and Drive, combined with specific triggers like 'PM summary' and 'week in review', makes it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: amplitude/builder-skills
Commit: 22b0634

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.