← ClaudeAtlas

weekly-gtm-reportlisted

Use when generating weekly GTM performance reports, summarizing pipeline activity, reviewing outreach metrics, or creating executive updates. Triggers: 'weekly report', 'GTM report', 'pipeline review', 'weekly update', 'outreach summary', 'Friday report'.
Othmane-Khadri/gtm-engineer-playbook · ★ 41 · Data & Documents · score 81
Install: claude install-skill Othmane-Khadri/gtm-engineer-playbook
# Weekly GTM Report Generate a structured weekly GTM performance report by reading data from the local `docs/` directory and optional CRM exports. Produces an executive-ready summary with metrics, highlights, week-over-week trends, and recommended actions. ## Tools Used - **Read** — load pipeline data, signal reports, account briefs, sequence configs, battlecards, meeting prep notes, CRM CSV exports, and previous reports - **Write** — save the weekly report and update the reports index - **Glob** — discover available data files across `docs/` subdirectories - **Bash** — date calculations (week number, date ranges) ## Methodology Follow these steps in order. Do not skip steps. Do not fabricate metrics. If data is missing for a section, include the section with a "No data available" note and a suggestion for how to populate it. ### Step 1: Data Collection Ask the user: > What week is this report for? (default: current week) Use Bash to compute the ISO week number and Monday-to-Friday date range for the target week. Then scan the `docs/` directory for available data sources. Run these searches: ``` Glob: docs/pipeline/scored-leads.md Glob: docs/signals/*.md Glob: docs/accounts/*.md Glob: docs/sequences/*.md Glob: docs/battlecards/*.md Glob: docs/meeting-prep/*.md Glob: docs/reports/week-*.md ``` Also ask the user: > Do you have a CRM export CSV for this week? If so, provide the file path. Read every file that exists. For each data source found, summarize what was l