weekly-gtm-report
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'.
npx skills add majiayu000/claude-skill-registry --skill weekly-gtm-report --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 Gl
- Tools Used
- Methodology
- Step 1: Data Collection
- Step 2: Pipeline Summary
- Step 3: Outreach Activity
- Step 4: Signals Detected
- Step 5: Meetings and Research
- Step 6: Competitive Updates
- Step 7: Key Metrics Dashboard
- Step 8: Recommendations
- Step 9: Output
- Key Rules
What does the weekly-gtm-report skill do?
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'.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill weekly-gtm-report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.