Generate a single comprehensive weekly briefing that covers every external customer or prospect call in the next 7 days, with per-meeting account and contact research from Common Room.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionweekly-prep-briefExecute the skills CLI command in your project's root directory to begin installation:
Fetches weekly-prep-brief from anthropics/knowledge-work-plugins and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate weekly-prep-brief. Access via /weekly-prep-brief in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
11.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
11.0K
stars
Generate a single comprehensive weekly briefing that covers every external customer or prospect call in the next 7 days, with per-meeting account and contact research from Common Room.
Option A — Calendar connected:
Use the ~~calendar connector to fetch all meetings scheduled in the next 7 days (or a user-specified range). Filter to keep only external meetings — those with attendees from outside your organization. Discard internal-only meetings, one-on-ones with colleagues, and recurring internal syncs.
Identify for each external meeting:
Option B — No calendar connected: Ask the user: "To build your weekly prep brief, I'll need your upcoming external calls. Please list them: company name, date/time, and attendee names."
Accept freeform input and parse it into a structured list before proceeding.
Present the identified meetings to the user for confirmation before beginning research:
"Here are the external calls I found for this week. Let me know if anything's missing or should be excluded:
- [Company] — [Day], [Time] — [Attendees]
- ..."
This prevents wasted research on cancelled or incorrect meetings.
For each confirmed external meeting, run in parallel where possible:
Common Room data is the primary source. After CR research, run a quick recency check for each company — this is supplementary, not primary:
"[company name]" news scoped to the last 7 daysDepth calibration:
Compile all per-meeting research into a single structured document, sorted by meeting date/time.
Open with a brief week-level overview that flags:
# Weekly Prep Brief — Week of [Date]
## Week Overview
[2–4 bullets: key themes, flagged priorities, call count]
---
## [Monday / Tuesday / etc.]
### [Company Name] — [Time]
**Attendees:** [Names and titles]
**Meeting type:** [Discovery / QBR / Renewal / Expansion / etc. — inferred if possible]
**Company Snapshot**
[4–5 bullets: account status, top signals, recent activity]
**Attendee Profiles**
- **[Name]** ([Title]): [2–3 bullets on their signals, persona, conversation angle]
- [Repeat per attendee]
**Top Signals This Week**
[2–3 most relevant signals for this specific call]
**This Week's News** [If notable news found]
[Only genuinely noteworthy findings — funding, leadership changes, major press]
**Recommended Objectives**
[1–2 sentences: what to accomplish in this meeting]
---
[Repeat per meeting, sorted by date/time]
If Common Room returns limited data for a particular meeting's account or attendees, use a compressed format for that meeting instead of the full template:
### [Company Name] — [Time] ⚠️ Limited Data
**Attendees:** [Names and titles if known]
**Data available:** [What Common Room actually returned]
**Web Search Results**
[Findings from web search — company news, attendee LinkedIn profiles]
**Note:** Common Room has limited data on this account. The rep may want to check directly in CR or gather context from colleagues before this call.
Do not generate a full meeting prep section (company snapshot, signal highlights, talking points, recommended objectives) from sparse data. A short honest section is more useful than a fabricated full one.
references/briefing-guide.md — guidelines for structuring briefings, prioritization logic, and how to handle edge cases (cancelled meetings, new accounts with no data, etc.)Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend weekly-prep-brief for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
weekly-prep-brief is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
weekly-prep-brief has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in weekly-prep-brief — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
weekly-prep-brief has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: weekly-prep-brief is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: weekly-prep-brief is focused, and the summary matches what you get after install.
We added weekly-prep-brief from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: weekly-prep-brief is focused, and the summary matches what you get after install.
We added weekly-prep-brief from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 47