New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Weekly Prep Brief

by w95 in w95/awesome-claude-corporate-skills

Generate a comprehensive weekly briefing for all external calls in the next 7 days.

MITAuto-check passedSales & Support

Install Weekly Prep Brief

skills CLI
$ npx skills add w95/awesome-claude-corporate-skills --skill weekly-prep-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install w95/awesome-claude-corporate-skills weekly-prep-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/w95/awesome-claude-corporate-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/05-sales/weekly-prep-brief .claude/skills/weekly-prep-brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
weekly-prep-brief
GitHub stars
237
Token cost
~1.3k tokens
SKILL.md length
545 words
Files
2 (incl. references)
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

Generate a comprehensive weekly briefing for all external calls in the next 7 days.

  • Works in 4 steps: Get the Week's External Meetings → Confirm the Meeting List → Research Each Meeting → …
  • Weekly prep brief
  • SKILL.md covers Briefing Process, Output Format, When a Meeting Has Sparse Data and Quality Standards, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Weekly Prep Brief is an agent skill from w95/awesome-claude-corporate-skills. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/briefing-guide.md`).

It sits in Sales & Support. The repository describes itself as: 166 production-ready Claude AI skills organized by corporate role — executive leadership, finance, HR, marketing, sales, legal, operations, engineering, product, data, customer…. The licence is MIT.

When your agent uses it

  • Weekly prep brief
  • Prepare my week
  • What calls do I have this week
  • Any weekly planning request

Example prompts

  • “weekly prep brief”
  • “prepare my week”
  • “what calls do I have this week”
  • “/weekly-prep-brief”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Get the Week's External Meetings
  2. Confirm the Meeting List
  3. Research Each Meeting
  4. Synthesize the Weekly Brief

What it can do on your machine

Read from SKILL.md and the folder at commit 78dbc7c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Weekly Prep Brief loads about 1.3k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 545 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from w95/awesome-claude-corporate-skills at commit 78dbc7c, republished under its MIT licence (© w95). 545 words, ~1,337 tokens.

Download SKILL.mdSave it as .claude/skills/weekly-prep-brief/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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.

Weekly Prep Brief

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.

Briefing Process

Step 1: Get the Week's External Meetings

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:

  • Company name
  • Meeting date and time
  • External attendee names and email addresses

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.

Step 2: Confirm the Meeting List

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.

Step 3: Research Each Meeting

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:

  • Search "[company name]" news scoped to the last 7 days
  • For executive attendees, search their name for recent public posts or interviews
  • Only include findings that are genuinely noteworthy (funding, leadership changes, major press). Don't pad the brief with generic news.

Depth calibration:

  • For high-priority accounts (large accounts, open opportunities, renewal risk), produce full depth research
  • For lower-priority or short meetings, produce abbreviated snapshots (3–4 bullets each)
Show full SKILL.md (224 more words)Show less
Step 4: Synthesize the Weekly Brief

Compile all per-meeting research into a single structured document, sorted by meeting date/time.

Open with a brief week-level overview that flags:

  • Any accounts with urgent signals (at-risk, trial expiring, expansion opportunity)
  • Any meetings that need special preparation or executive involvement
  • Total external call count and estimated time commitment

Output Format

# 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]

When a Meeting Has Sparse Data

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.

Quality Standards

  • Keep each meeting section scannable — reps read these in the morning, often on mobile
  • Always sort by date/time ascending
  • Flag urgent situations prominently (risk, trial expiration, open opps) — don't bury them
  • If a meeting has very thin Common Room data, use the sparse-data format above — never fill the full template with guesses
  • Total brief should be readable in 10–15 minutes for a week with 4–6 meetings
  • Every fact must come from a tool call — no invented deal context, activity, or signals

Reference Files

  • references/briefing-guide.md — guidelines for structuring briefings, prioritization logic, and how to handle edge cases (cancelled meetings, new accounts with no data, etc.)

© w95, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in 05-sales/weekly-prep-brief of w95/awesome-claude-corporate-skills.

  • SKILL.md
  • references/briefing-guide.md

Open the folder on GitHubat commit 78dbc7c

Compare with similar skills

Weekly Prep Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Weekly Prep Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Weekly Prep Brief this skillw95/awesome-claude-corporate-skills237—~1.3kAutomated safety check: PassMIT
Cold Outbound Optimizerericosiu/ai-marketing-skills3.6k1 repos~1.7kAutomated safety check: PassMIT
Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore19540 repos~3.2kAutomated safety check: PassMIT
Amazon Buy Box Monitorbrowser-act/skills6.1k2 repos~1.6kAutomated safety check: PassMIT
Review Analysisliangdabiao/amazon-sorftime-research-MCP-skill9461 repos~2.5kAutomated safety check: PassNone
Deskcomm Extensaomelgarafael/DeskcommCRM4.5k—~2.7kAutomated safety check: PassMIT

Similar skills

  • Cold Outbound Optimizer

    ericosiu/ai-marketing-skills

    Design, analyze, and optimize cold outbound email campaigns for Instantly.

    3.6k GitHub starsUsed in 1 repo~1.7k tokens
    Sales & SupportAuto-check passed

  • Doc Coauthoring

    aws-samples/sample-strands-agent-with-agentcore

    Official

    Guide users through a structured workflow for co-authoring documentation.

    195 GitHub starsUsed in 40 repos~3.2k tokens
    Sales & SupportAuto-check passed

  • Amazon Buy Box Monitor

    browser-act/skills

    Pulls Amazon product details, competing seller prices and seller ratings for a given ASIN through the BrowserAct API, without browser automation.

    6.1k GitHub starsUsed in 2 repos~1.6k tokens
    Sales & SupportAuto-check passed

  • Review Analysis

    liangdabiao/amazon-sorftime-research-MCP-skill

    对亚马逊商品评论进行深度分析，自动识别产品痛点、分析退货原因，生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.

    946 GitHub starsUsed in 1 repo~2.5k tokens
    Sales & SupportAuto-check passed

  • Deskcomm Extensao

    melgarafael/DeskcommCRM

    Guia para criar uma extensão do DeskcommCRM — o pacote declarativo — em vez de abrir um PR no núcleo.

    4.5k GitHub stars~2.7k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Tourmind Booking

    tourmind-com/Tourmind-Booking-Skills

    MUST USE for any hotel or accommodation intent in any language, including hotel search, hotel recommendations, nearby accommodation, hostels, guesthouses, resorts, where-to-stay questions, room…

    1.7k GitHub stars~13k tokensUpdated 15 days ago
    Sales & SupportAuto-check passed

More from w95/awesome-claude-corporate-skills

All 39 skills in this repo

  • Data Context Extractor

    w95/awesome-claude-corporate-skills

    Generate or improve a company-specific data analysis skill by extracting tribal knowledge from analysts.

    237 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

  • Competitive Analysis

    w95/awesome-claude-corporate-skills

    Framework for competitive landscape analysis across any industry.

    237 GitHub starsUsed in 1 repo~4k tokens
    Auto-check passed

  • Account Research

    w95/awesome-claude-corporate-skills

    Research a company using Common Room data. An agent skill from w95/awesome-claude-corporate-skills.

    237 GitHub stars~1.5k tokensUpdated 7 mo ago
    Auto-check passed

  • Call Prep

    w95/awesome-claude-corporate-skills

    Prepare for a customer or prospect call using Common Room signals.

    237 GitHub stars~1.5k tokensUpdated 7 mo ago
    Auto-check passed

  • Compose Outreach

    w95/awesome-claude-corporate-skills

    Generate personalized outreach messages using Common Room signals.

    237 GitHub stars~1.4k tokensUpdated 7 mo ago
    Auto-check passed

  • SQL Queries

    w95/awesome-claude-corporate-skills

    Write correct, performant SQL across all major data warehouse dialects (Snowflake, BigQuery, Databricks, PostgreSQL, etc.).

    237 GitHub starsUsed in 3 repos~2.8k tokens
    Auto-check passed

Categories

Questions about Weekly Prep Brief

What does Weekly Prep Brief do?

Generate a comprehensive weekly briefing for all external calls in the next 7 days. Weekly Prep Brief is an agent skill from w95/awesome-claude-corporate-skills. Generate a comprehensive weekly briefing for all external calls in the next 7 days.

When should I use Weekly Prep Brief?

Weekly Prep Brief fits situations like: weekly prep brief; prepare my week; what calls do I have this week; any weekly planning request.

How do I install Weekly Prep Brief in Claude Code?

Run `npx skills add w95/awesome-claude-corporate-skills --skill weekly-prep-brief -a claude-code`. Or copy the skill folder (05-sales/weekly-prep-brief in w95/awesome-claude-corporate-skills) into .claude/skills/weekly-prep-brief in your project. Claude Code loads it when a task matches its description.

How do I install Weekly Prep Brief in Codex?

Run `npx skills add w95/awesome-claude-corporate-skills --skill weekly-prep-brief -a codex`. Or copy the skill folder (05-sales/weekly-prep-brief in w95/awesome-claude-corporate-skills) into .agents/skills/weekly-prep-brief in your project. Codex loads it when a task matches its description.

Can I use Weekly Prep Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add w95/awesome-claude-corporate-skills --skill weekly-prep-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weekly-prep-brief, .gemini/skills/weekly-prep-brief, .github/skills/weekly-prep-brief and .opencode/skills/weekly-prep-brief in your project.

What does Weekly Prep Brief need to run?

SKILL.md names no scripts, command-line tools or credentials: Weekly Prep Brief is instructions for the agent only.

Does Weekly Prep Brief access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Weekly Prep Brief safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Weekly Prep Brief use?

Weekly Prep Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Weekly Prep Brief use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 473 tokens, read only when the agent opens those files.

What are the alternatives to Weekly Prep Brief?

Skills that share tags, products or a category with Weekly Prep Brief: Cold Outbound Optimizer (ericosiu/ai-marketing-skills, 3.6k stars), Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Amazon Buy Box Monitor (browser-act/skills, 6.1k stars) and Review Analysis (liangdabiao/amazon-sorftime-research-MCP-skill, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Weekly Prep Brief?

w95 (a GitHub user) maintains it in w95/awesome-claude-corporate-skills, which has 237 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on February 26, 2026.

Source: w95/awesome-claude-corporate-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.