用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/thiagofernandes1987-create/APEX --skill weekly-prep-brief命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | weekly-prep-brief |
| description | "condition: CRM ou enrichment tool indisponível" |
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.)Track —
Use this skill when the task requires weekly prep brief capabilities.
基于 SOC 职业分类