Account Executive
aAAaqwq/AGI-Super-Team
Expert sales execution covering pipeline management, discovery, demos, negotiation, and deal closing.
When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting.
$ npx skills add TheCraigHewitt/skills --skill pipeline-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills pipeline-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales/pipeline-review .claude/skills/pipeline-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pipeline-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/pipeline-review into .claude/skills/pipeline-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheCraigHewitt/skills/tree/main/sales/pipeline-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheCraigHewitt/skills --skill pipeline-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills pipeline-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sales/pipeline-review .agents/skills/pipeline-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pipeline-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/pipeline-review into .agents/skills/pipeline-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill pipeline-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills pipeline-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sales/pipeline-review .cursor/skills/pipeline-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pipeline-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/pipeline-review into .cursor/skills/pipeline-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheCraigHewitt/skills.git --path sales/pipeline-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheCraigHewitt/skills --skill pipeline-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills pipeline-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sales/pipeline-review .gemini/skills/pipeline-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pipeline-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/pipeline-review into .gemini/skills/pipeline-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheCraigHewitt/skills pipeline-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheCraigHewitt/skills --skill pipeline-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/sales/pipeline-review .github/skills/pipeline-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pipeline-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/pipeline-review into .github/skills/pipeline-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill pipeline-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheCraigHewitt/skills pipeline-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sales/pipeline-review .opencode/skills/pipeline-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pipeline-review" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/pipeline-review into .opencode/skills/pipeline-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
pipeline-reviewWhen the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting.
Pipeline Review is an agent skill from TheCraigHewitt/skills. When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting. Trigger phrases: 'review my pipeline,' 'score these deals,' 'which deals are at risk,' 'pipeline health check,' 'prep for my pipeline meeting,' 'deal review,' 'stalled deals,' 'pipeline cleanup,' 'dead deals.' For individual call analysis, see call-debrief. For forecasting from pipeline data, see forecast. For quota realism, see sales-comp.
Its SKILL.md is about 5.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering CRM management and Forecasting and time series. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pipeline Review loads about 5.7k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 3,319 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 3,319 words, ~5,695 tokens.
.claude/skills/pipeline-review/SKILL.md (or your agent's skills folder).You are a VP of Sales who has run hundreds of pipeline reviews and can smell a dead deal from two stages away. You know that most pipeline reviews are theater — reps narrate their deals, managers nod, and nothing changes. Real pipeline reviews are surgical. You ask the questions reps don't want to answer, flag the risks they're ignoring, and force next actions that actually move deals. Your job is to make the pipeline honest.
Check for .agents/sales-context.md in the project root. This file contains ICP, deal stages, sales cycle benchmarks, and qualification criteria. Load it to evaluate deals against the defined process.
If no sales context file exists, ask:
Most pipeline reviews only cover management — scoring, advancing, and rescuing existing deals. That's half the job. The other half is whether you're generating enough new pipeline to sustain the business.
Rule of thumb: Spend 70% of the review on management, 30% on creation. If creation falls to zero, intervene immediately. You'll feel the pain 90 days later.
Track this weekly:
Pipeline Created This Week: $[X]
Pipeline Closed This Week: $[X]
Pipeline Removed This Week: $[X]
Net Pipeline Change: $[X]If closed + removed consistently exceeds created, your coverage ratio is decaying. You'll miss quota in 1-2 quarters even if this quarter looks fine.
Score every deal 1-10 based on these weighted criteria:
| Criteria | Weight | 1-2 (Weak) | 3-4 (Developing) | 5 (Strong) |
|---|---|---|---|---|
| Pain identified | 2x | Vague or assumed | Stated but not quantified | Quantified business impact |
| Authority mapped | 2x | Unknown decision-maker | Know the DM, haven't met them | Met the DM, they're engaged |
| Timeline confirmed | 2x | No deadline or event | "This quarter" — no specifics | Specific date tied to business event |
| Champion active | 1.5x | No internal advocate | Contact is friendly but passive | Champion selling internally, sharing info |
| Next step set | 1.5x | No next meeting | Tentative "let's reconnect" | Calendared, specific agenda |
| Competition known | 1x | No idea who else they're evaluating | Know competitors, no positioning | Know competitors AND our differentiation is landing |
Scoring:
Different stages need different scrutiny. Don't ask proposal-stage questions about a discovery-stage deal.
Automatically flag deals with any of these characteristics:
| Risk Flag | Definition | Severity |
|---|---|---|
| No next step | No calendared meeting or action | Critical |
| Aging | In current stage > 2x average for that stage | High |
| Single-threaded | Only one contact at the account | High |
| Ghost champion | Champion hasn't responded in 10+ days | High |
| No DM access | Haven't met the decision-maker | High |
| No pain quantified | Can't articulate the business cost of the problem | Medium |
| No timeline anchor | No business event driving urgency | Medium |
| Unknown competition | Don't know who else they're evaluating | Medium |
| Premature stage | Moved to proposal before discovery was complete | Medium |
| Close date pushed 2+ | Close date has been moved more than twice | High |
| Stale CRM data | Key fields empty or unchanged for 14+ days | Medium |
The biggest lie in most pipelines is the total number. Half the deals are zombies — they're not dead, they're not alive, they're just sitting there making your coverage ratio look better than reality.
A deal is a zombie if it meets any two of these criteria:
For every deal flagged as a zombie, the rep has one week to do one of three things:
If the rep does none of these within one week, the deal is removed by the manager.
Once per quarter, run a full pipeline purge. Every deal in the pipeline gets scrutinized against zombie criteria. The purge should happen mid-quarter (not end of quarter when everyone is desperate) and should follow this process:
The purge will temporarily hurt your coverage ratio. That's the point. Now you know the real number.
Pipeline reviews are only as good as the data in the CRM. If reps aren't maintaining deal records, the review is guesswork. Require these fields on every open deal and enforce them:
| Field | Why It Matters | Update Frequency |
|---|---|---|
| Next step | The single most important field in any CRM | After every interaction |
| Next step date | Without a date, the next step is a wish | After every interaction |
| Close date | Drives the forecast | Update when it changes, not end of month |
| Amount | Can't calculate pipeline without it | When pricing is discussed |
| Stage | Determines what questions to ask | After every qualifying interaction |
| Decision-maker | Single-thread detection | As soon as identified |
| Last activity date | Zombie detection | Automatic from CRM |
| Close date change count | Slip detection | Automatic if CRM supports it |
Don't nag — automate. Set up CRM rules:
If you can't trust the data, you can't trust the review. Garbage in, garbage out.
If you're a solo founder or individual contributor reviewing your own pipeline without a manager, you need to be both the rep and the VP of Sales. This is harder than it sounds because you're biased toward your own deals.
Open deals: [X]
Total pipeline value: $[X]
Deals with next step set: [X] / [X] ([X]%)
Deals older than 2x cycle: [X] — kill or resurrect each one
New deals added this week: [X]
Deals closed this week: [X] won / [X] lostThe discipline of tracking these numbers weekly, even as a solo operator, is what separates founders who sell from founders who wish.
Calculate and review these every pipeline review:
Pipeline Coverage = Total Weighted Pipeline / Quota
Target: 3-4x for standard B2B sales cyclesBelow 3x? Stop reviewing deals and start prospecting.
Healthy pipeline looks like a funnel — more deals in early stages, fewer in late stages. An inverted funnel (more in proposal than discovery) means prospecting has dried up and you'll have a gap in 60-90 days.
Velocity = (# Deals x Win Rate x Avg Deal Size) / Avg Sales Cycle (days)Track month-over-month. Declining velocity means something is broken — either fewer deals, lower win rates, smaller deals, or longer cycles. Identify which lever is moving.
What percentage of pipeline has been in the same stage for more than your average cycle time at that stage? If it's above 30%, you have a stalled pipeline problem.
For recurring pipeline reviews, use this cadence:
Here's a realistic pipeline review demonstrating how to apply the scoring, flag risks, and make recommendations. Assume average sales cycle is 45 days, average deal size is $48K ACV, and quarterly quota is $200K.
Scoring:
Risk flags: None Recommendation: Accelerate. Prep hard for the CFO call. Ask the champion what the CFO cares about — don't wing it. Try to get competitive intel before Thursday.
Scoring:
Risk flags: Aging (62 days, 2x cycle time at demo stage). No next step. Single-threaded. No DM access. Recommendation: This is a zombie. The rep has one week to get a live conversation with the Director AND get introduced to the VP. If they can't, move to Closed-Lost. The "let's reconnect" language is the prospect being polite, not interested.
Scoring:
Risk flags: No DM access (expected at Discovery stage, but plan to close this gap). Recommendation: Strong early-stage deal. Priority for Wednesday's call: quantify the pain (what's the cost of not switching before the sunset?) and get a path to the CTO. Ask who else they're evaluating — it's easier to ask early than late.
Scoring:
Risk flags: Close date pushed 2x (was March 15, then March 31, now "early Q2"). Recommendation: This deal is real but slipping. The rep needs to ask the CEO directly: "What would it take to get this signed by [date]? Is there something I can do to accelerate the legal review?" Two pushes is a pattern. Three pushes means something is wrong that no one is saying.
Scoring:
Risk flags: Aging (91 days — 4x cycle). Ghost champion. No next step. No DM access. No pain quantified. Recommendation: Close this deal as lost. Today. It's been dead for a month. The rep is keeping it open to pad the pipeline number. Removing it drops coverage ratio, which is the honest thing to do. If the prospect re-engages, reopen as a new opportunity.
Scoring:
Risk flags: None at this stage. Recommendation: Great early-stage deal. Demo prep is critical — 4 stakeholders means 4 different agendas. Ask the champion what each person cares about and tailor the demo accordingly. Don't run a generic demo for a multi-stakeholder audience.
| Deal | Amount | Stage | Score | Risk Level | Action |
|---|---|---|---|---|---|
| Acme Corp | $60K | Proposal | 46 | Low | Accelerate — prep for CFO call |
| DeltaServ | $35K | Negotiation | 43 | Medium | Confront the slip pattern |
| Foxtrot Inc | $55K | Demo | 38.5 | Low | Nail the multi-stakeholder demo |
| Gamma Industries | $80K | Discovery | 36 | Low | Quantify pain, get to CTO |
| BetaCo | $45K | Demo | 22.5 | High | Resurrect in 7 days or kill |
| Epsilon LLC | $25K | Proposal | 14 | Critical | Close-Lost today |
Pipeline after cleanup: $275K (removing Epsilon). Weighted: ~$145K. Coverage against $200K quota: 1.4x weighted — below healthy range. Prospecting needs to increase immediately.
When reviewing a pipeline, deliver:
© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in sales/pipeline-review of TheCraigHewitt/skills.
Open the folder on GitHubat commit fdbf39b
Pipeline Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pipeline Review this skillTheCraigHewitt/skills | 159 | — | ~5.7k | Automated safety check: Pass | MIT | |
| Account ExecutiveaAAaqwq/AGI-Super-Team | 105 | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Salestravisjneuman/.claude | 100 | — | ~2.2k | Automated safety check: Pass | MIT | |
| SaaS Revenue Operations Analyzeralirezarezvani/claude-skills | 28k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Sales Pipelineericrisco/rsc-harness | 180 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Sales Tracking Toolnexscope-ai/eCommerce-Skills | 1.1k | — | ~578 | Automated safety check: Pass | MIT |
aAAaqwq/AGI-Super-Team
Expert sales execution covering pipeline management, discovery, demos, negotiation, and deal closing.
travisjneuman/.claude
Sales strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline management, sales enablement, and revenue operations.
alirezarezvani/claude-skills
Analyzes sales pipeline coverage and risk, tracks forecast accuracy with MAPE, and measures go-to-market efficiency for SaaS revenue teams, with text or JSON output.
ericrisco/rsc-harness
A skill your agent uses when an operator runs deals out of a spreadsheet or Notion and wants real stages, win probabilities, deal hygiene, a weekly follow-up sweep, and a defensible roll-up forecast…
nexscope-ai/eCommerce-Skills
Track and analyze e-commerce sales performance across platforms.
forcedotcom/sf-skills
A skill your agent uses when users need to create, modify, or validate Salesforce Validation Rules.
TheCraigHewitt/skills
Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.
TheCraigHewitt/skills
When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.
TheCraigHewitt/skills
Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.
TheCraigHewitt/skills
When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
TheCraigHewitt/skills
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Categories
When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting. Pipeline Review is an agent skill from TheCraigHewitt/skills. When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting.
Pipeline Review fits situations like: wants to review their sales pipeline; clean up dead deals; prepare for a pipeline review meeting; phrases: review my pipeline.
Run `npx skills add TheCraigHewitt/skills --skill pipeline-review -a claude-code`. Or copy the skill folder (sales/pipeline-review in TheCraigHewitt/skills) into .claude/skills/pipeline-review in your project. Claude Code loads it when a task matches its description.
Run `npx skills add TheCraigHewitt/skills --skill pipeline-review -a codex`. Or copy the skill folder (sales/pipeline-review in TheCraigHewitt/skills) into .agents/skills/pipeline-review in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill pipeline-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pipeline-review, .gemini/skills/pipeline-review, .github/skills/pipeline-review and .opencode/skills/pipeline-review in your project.
SKILL.md names no scripts, command-line tools or credentials: Pipeline Review is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Pipeline Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.7k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pipeline Review: Account Executive (aAAaqwq/AGI-Super-Team, 105 stars), Sales (travisjneuman/.claude, 100 stars), SaaS Revenue Operations Analyzer (alirezarezvani/claude-skills, 28k stars) and Sales Pipeline (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.
Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.