arrows-weekly-pipeline-review
Weekly pipeline review from Sales Skills by Arrows. Scans every open deal in the CRM, cross-checks email, calls and calendar for real activity, and builds a visual one-page report: what needs attention this week, what's closing, what's at risk and why, and the pipeline by stage. Sales leaders get a rollup by rep. Ready to share before a 1:1 or team pipeline meeting, and can run itself every Monday. Use this whenever someone says 'Run my weekly pipeline review', 'show me my pipeline', 'review my team's pipeline', asks what's closing or at risk across their deals, or wants a pipeline summary for a 1:1, forecast call or team meeting.
Install
With your agent
Install OMGSkills skill "arrowshq/arrows-sales-skills:arrows-weekly-pipeline-review" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/ArrowsHQ/arrows-sales-skills /tmp/arrows-sales-skills && ln -s /tmp/arrows-sales-skills/arrows-weekly-pipeline-review ~/.claude/skills/arrows-weekly-pipeline-reviewFrom README
Step 1: Read the profile Use the profile files if they're in the project. They tell you what "good" looks like for this person, so the review flags what matters to them rather than generic hygiene. arrows-sales-process.md: ## Pipeline stages gives the stage order, what has to be true to move on, and typical time in stage. ## Discovery and qualification gives the methodology (MEDDIC, SPICED, BANT or their own) and what's usually missing. Use these to judge whether a deal is really where its stage says. arrows-how-i-work.md: ## What slips tells you what to flag first. ## About me says rep, leader or both. arrows-how-we-work.md (leaders): ## What I want to see weekly shapes the rollup; ## Every rep, every deal is the checklist each rep's deals are measured against. No profile: run the review anyway with stages straight from the CRM, and use the shared context's one-line suggestion at the end. Step 2: Decide whose pipeline There are two versions of the same report.