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.
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./execution-skills/skills/pm-weekly-brief/SKILL.mdQuality
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 skill description that clearly articulates specific data sources (Slack, calendar, Drive), a concrete output (personal PM summary), a time scope (last 7 days), and an explicit usage trigger (end of week). It uses third person voice and natural keywords throughout. Minor improvement could include additional trigger terms like 'weekly recap' or 'standup notes' but overall this is well-crafted.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: reading Slack mentions, calendar events, and recently modified Drive documents, then synthesizing them into a personal PM summary. These are clear, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both what (read Slack mentions, calendar events, Drive documents and synthesize into a PM summary) and when ('Use at the end of each week to capture what happened before it fades'), providing an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Slack mentions', 'calendar events', 'Drive documents', 'weekly summary', 'PM summary'. These are terms a user would naturally use when requesting this kind of recap. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of Slack, calendar, Drive, weekly cadence, and PM-specific summary creates a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured prompt template for generating a weekly PM brief, but it lacks the actionable specifics needed for reliable execution — no MCP tool call examples, no step-by-step data retrieval workflow, and no validation or error handling for when data sources return incomplete results. The concept is clear but the implementation guidance is too abstract for Claude to execute reliably without additional context.
Suggestions
Add explicit MCP tool call examples (e.g., specific Slack, Calendar, and Drive function names and parameters) so Claude knows exactly how to retrieve data from each source.
Define a sequential workflow: 1) fetch Slack mentions, 2) fetch calendar events, 3) fetch Drive activity, 4) validate each returned non-empty, 5) synthesize into brief — with error handling if a source fails.
Remove the opening flavor paragraph ('By Friday you've had 30 meetings...') to save tokens — Claude doesn't need motivational framing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph ('By Friday you've had 30 meetings, 200 Slack messages...') is unnecessary flavor text that Claude doesn't need. The setup table and tips are reasonably lean, but the overall content could be tighter. | 2 / 3 |
Actionability | The prompt template is concrete and copy-paste ready, which is good. However, there are no actual MCP tool calls, API commands, or executable code — it relies on Claude inferring how to use Slack/Calendar/Drive MCPs without specifying function names, parameters, or authentication patterns. | 2 / 3 |
Workflow Clarity | There is no sequenced workflow — it's a single prompt template with no steps for how to query each data source, no validation that data was retrieved successfully, and no error handling if an MCP connection fails or returns empty results. For a multi-source aggregation task, this lacks critical checkpoints. | 1 / 3 |
Progressive Disclosure | For a skill of this size and scope, the content is well-organized with clear sections (Prompt Template, Setup, Placeholders, Tips). No bundle files are needed, and the cross-reference to 'stakeholder-update' is a single-level pointer. Structure is appropriate. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- amplitude/builder-skills
- Commit
221ffaa
- 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.