instrument-data-to-all…
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when…
Generate a comprehensive weekly briefing for all external calls in the next 7 days. Triggers on 'weekly prep brief', 'prepare my week', 'what calls do I have this week', 'Monday prep', or any weekly planning request.
$ npx -y skills add anthropics/knowledge-work-plugins --skill weekly-prep-brief --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/weekly-prep-briefContext preview
The summary Claude sees to decide when to auto-load this skill.
Generate a comprehensive weekly briefing for all external calls in the next 7 days. Triggers on 'weekly prep brief', 'prepare my week', 'what calls do I have this week', 'Monday prep', or any weekly planning request.
name: weekly-prep-brief description: "Generate a comprehensive weekly briefing for all external calls in the next 7 days. Triggers on 'weekly prep brief', 'prepare my week', 'what calls do I have this week', 'Monday prep', or any weekly planning request."
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: 1. **Account research** — full account snapshot using the account-research skill 2. **Contact research** — profile for each external attendee using the contact-research skill
Common Room data is the primary source. After CR research, run a quick **recency check** for each company — this is supplementary, not primary:
Depth 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.
Plugins that turn Claude into a specialist for your role, team, and company. Built for Claude Cowork, also compatible with Claude Code.
Repo: anthropics/knowledge-work-plugins
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when…
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data. Use when analyzing RNA-seq, WGS/WES, or ATAC-seq data—either local FASTQs or…
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific…
Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI,…
Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive…
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery,…