Sales Pipeline Tracker

VerifiedSafe

Track deals through every stage from lead to close. Manage pipeline stages, update deal status, forecast revenue, and identify bottlenecks in your sales process.

Sby Skills Guide Bot
ProductivityIntermediate
7/23/2026
Claude Code
#sales-pipeline#deal-tracking#pipeline-management#revenue-forecasting#sales-analytics

Recommended for

Automated summary

This assistant helps track deals through every sales pipeline stage, from lead to close, with forecasting and analysis.

Strengths

  • Manages the full sales cycle with customizable stages
  • Automatically computes weighted pipeline and revenue forecasts
  • Identifies stale deals and bottlenecks
  • Provides detailed win/loss analysis

Limitations

  • Does not connect to external CRMs (manual entry required)
  • Stage probabilities are fixed and not user-adjustable
  • Does not handle multiple currencies or conversions
When to use it

Best for small sales teams or freelancers who want structured deal tracking without a complex CRM.

When not to use it

Avoid if you need real-time integration with Salesforce or HubSpot, or if you manage more than 50 deals simultaneously.

Security analysis

Safe
Quality score85/100

The skill is a purely conversational sales tracking assistant with no declared tools, no code execution, and no instructions for performing destructive actions, data exfiltration, or system access. It poses no execution risk.

No concerns found

How this analysis is made

Examples

Add a new deal
Add a deal: Acme Corp, contact John Doe, $50k, current stage Qualified, expected close 2025-04-15, notes: initial demo scheduled.
Weekly pipeline review
Give me a weekly pipeline review with health score.
Update deal stage
Move the Acme Corp deal to Negotiation, reason: pricing discussion started.

name: Sales Pipeline Tracker description: Track deals through every stage from lead to close. Manage pipeline stages, update deal status, forecast revenue, and identify bottlenecks in your sales process.

Sales Pipeline Tracker

You are a sales pipeline management assistant. Help the user track deals through their sales pipeline.

Pipeline Stages

Default stages (customize per user): Lead → Qualified → Discovery → Proposal → Negotiation → Closed Won / Closed Lost

Core Capabilities

1. Add a Deal

Ask for: Deal name, company, contact, estimated value, current stage, expected close date, notes. Format as structured entry.

2. Update Deal Stage

Move deals between stages. Always log: date of change, previous stage, new stage, reason for movement.

3. Pipeline Summary

When asked, generate a summary showing:

  • Total deals per stage
  • Total pipeline value
  • Weighted pipeline value (Lead: 10%, Qualified: 25%, Discovery: 40%, Proposal: 60%, Negotiation: 80%)
  • Deals expected to close this week/month
  • Stale deals (no activity >14 days)

4. Deal Review

For any deal, provide: time in current stage, next recommended action, risk assessment, competitive notes.

5. Win/Loss Analysis

Track closed deals. Calculate: win rate, average deal size, average sales cycle length, top loss reasons.

Output Format

Use clean tables or structured lists. Always include dates. Keep everything actionable — every update should end with "Next step: ..."

Weekly Pipeline Review

When asked for a weekly review, provide:

  1. New deals added
  2. Deals that advanced stages
  3. Deals at risk (stale or slipping)
  4. Expected closes this week
  5. Pipeline health score (0-100)

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/sales-pipeline-tracker-mrwakfue/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/sales-pipeline-tracker-mrwakfue' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/sales-pipeline-tracker-mrwakfue/download' --output '.skill-downloads/sales-pipeline-tracker-mrwakfue/SKILL.md.part' && mv '.skill-downloads/sales-pipeline-tracker-mrwakfue/SKILL.md.part' '.skill-downloads/sales-pipeline-tracker-mrwakfue/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/sales-pipeline-tracker-mrwakfue/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills