Account Executive
aAAaqwq/AGI-Super-Team
Expert sales execution covering pipeline management, discovery, demos, negotiation, and deal closing.
Sales strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline management, sales enablement, and revenue operations.
Install Sales
$ npx skills add travisjneuman/.claude --skill sales -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install travisjneuman/.claude sales --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/travisjneuman/.claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sales .claude/skills/sales && 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 "sales" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/sales into .claude/skills/sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales", 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/travisjneuman/.claude/tree/master/skills/salesType 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 travisjneuman/.claude --skill sales -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install travisjneuman/.claude sales --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sales .agents/skills/sales && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sales" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/sales into .agents/skills/sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales", 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 travisjneuman/.claude --skill sales -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install travisjneuman/.claude sales --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sales .cursor/skills/sales && 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 "sales" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/sales into .cursor/skills/sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales", 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/travisjneuman/.claude.git --path skills/sales--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 travisjneuman/.claude --skill sales -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install travisjneuman/.claude sales --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sales .gemini/skills/sales && 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 "sales" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/sales into .gemini/skills/sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales", 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 travisjneuman/.claude salesInstalls 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 travisjneuman/.claude --skill sales -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sales .github/skills/sales && 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 "sales" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/sales into .github/skills/sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales", 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 travisjneuman/.claude --skill sales -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install travisjneuman/.claude sales --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sales .opencode/skills/sales && 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 "sales" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/sales into .opencode/skills/sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales", 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.
Facts
- Skill name
sales- GitHub stars
- 100
- Token cost
- ~2.2k tokens
- SKILL.md length
- 350 words
- Files
- 3 (incl. references)
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Sales strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline management, sales enablement, and revenue operations.
- Building sales processes
- SKILL.md covers Sales Methodologies, Pipeline Management, Sales Forecasting and Account Management, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Qualifying deals
What it does
Sales is an agent skill from travisjneuman/.claude. Sales strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline management, sales enablement, and revenue operations. Use when building sales processes, qualifying deals, managing pipelines, or improving close rates.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/sales-enablement.md` and `references/sales-methodologies.md`).
It sits in Sales & Support, covering Forecasting and time series, CRM management and Customer success. The repository describes itself as: The Ultimate Claude Code Toolkit: 180 skills, 10 agents, 29 commands, 7 hooks, and 81 marketplace repos (11,000+ community skills). Drop-in ~/.claude config with a generated… The licence is MIT.
When your agent uses it
- Building sales processes
- Qualifying deals
- Managing pipelines
- Improving close rates
Example prompts
- “Use the sales skill to sale strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline…”
- “/sales”
What it can do on your machine
Read from SKILL.md and the folder at commit 446a461. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sales loads about 2.2k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 350 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from travisjneuman/.claude at commit 446a461, republished under its MIT licence (© travisjneuman). 350 words, ~2,230 tokens.
Download SKILL.mdSave it as
.claude/skills/sales/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- sales
- description
- Sales strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline management, sales enablement, and revenue operations. Use when building sales processes, qualifying deals, managing pipelines, or improving close rates.
Sales Strategy Expert
Comprehensive sales frameworks for deal qualification, pipeline management, and revenue growth.
Sales Methodologies
Quick Reference
| Methodology | Core Focus | Best For |
|---|---|---|
| MEDDIC | Deal qualification rigor | Enterprise sales |
| SPIN | Question-based discovery | Complex solutions |
| Challenger | Insight-led selling | Competitive markets |
| Solution Selling | Problem-solving approach | Value-based sales |
For detailed methodology frameworks (MEDDIC, SPIN, Challenger, Solution Selling), see Sales Methodologies Reference.
Pipeline Management
Pipeline Metrics
| Metric | Formula | Benchmark |
|---|---|---|
| Pipeline Coverage | Pipeline / Quota | 3-4x |
| Win Rate | Won / (Won + Lost) | 20-30% |
| Average Deal Size | Revenue / Deals | Industry specific |
| Sales Cycle | Days from lead to close | Industry specific |
| Pipeline Velocity | (Opps x Win% x ACV) / Cycle Days | Increasing |
| Conversion Rates | By stage | Stage specific |
Pipeline Stages
| Stage | Definition | Exit Criteria | Probability |
|---|---|---|---|
| Qualification | Initial fit assessment | BANT qualified | 10% |
| Discovery | Deep dive on needs | Pain confirmed, stakeholders mapped | 20% |
| Solution | Present solution | Technical win | 40% |
| Proposal | Formal proposal | Budget confirmed | 60% |
| Negotiation | Terms discussion | Verbal commitment | 80% |
| Closed Won | Contract signed | Revenue booked | 100% |
Pipeline Review Framework
WEEKLY PIPELINE REVIEW:
OPPORTUNITIES TO REVIEW:
- Closing this period
- Slipped deals
- Large opportunities
- At-risk deals
- Newly created
QUESTIONS TO ASK:
1. What changed since last week?
2. What's the next step? When?
3. Who is the champion? Economic buyer?
4. What's the compelling event?
5. What could stop this deal?
6. What help do you need?
DEAL HEALTH INDICATORS:
Green: On track, strong champion, clear next steps
Yellow: Some concerns, requires attention
Red: Significant risk, may need intervention or removalSales Forecasting
Forecasting Methods
| Method | Approach | Best For |
|---|---|---|
| Weighted Pipeline | Sum of (Deal value x Probability) | Standard forecast |
| Stage-Based | Historical conversion by stage | Mature sales orgs |
| Judgment-Based | Rep/manager assessment | New markets |
| AI/ML | Predictive models | Large datasets |
| Hybrid | Multiple methods combined | Most accurate |
Show full SKILL.md (148 more words)Show less
Forecast Categories
| Category | Definition | Confidence |
|---|---|---|
| Closed | Contract signed | 100% |
| Commit | Will close this period | 90%+ |
| Best Case | Could close if everything goes well | 50-70% |
| Pipeline | In qualification stages | 10-40% |
| Upside | Potential but not forecasted | <10% |
Forecast Accuracy
ACCURACY METRICS:
Forecast Accuracy = 1 - |Actual - Forecast| / Forecast
TRACKING:
- By rep, team, region
- By forecast category
- Over time (trend)
- By deal size
IMPROVEMENT TACTICS:
- Deal inspection rigor
- Stage definitions clarity
- Consistent methodology
- Historical data analysis
- AI-assisted predictionsAccount Management
Account Segmentation
| Tier | Criteria | Coverage Model |
|---|---|---|
| Strategic | Highest revenue/potential | Named rep, dedicated CSM |
| Enterprise | Large accounts | Territory rep, shared CSM |
| Mid-Market | Growth accounts | Pool coverage, tech-touch CSM |
| SMB | Volume accounts | Inside sales, self-service |
Account Planning Template
ACCOUNT PLAN:
ACCOUNT OVERVIEW:
- Company profile
- Industry/market position
- Financial health
- Strategic priorities
RELATIONSHIP MAP:
- Organizational chart
- Key stakeholders
- Champions and detractors
- Influence map
BUSINESS UNDERSTANDING:
- Their strategic initiatives
- Pain points and challenges
- Competitive landscape
- Technology environment
OPPORTUNITY ASSESSMENT:
- Current spend with us
- Whitespace analysis
- Competitive presence
- Growth potential
STRATEGY:
- Account objectives
- Key initiatives
- Resource requirements
- Risk mitigation
ACTION PLAN:
| Initiative | Owner | Timeline | Status |
|------------|-------|----------|--------|
| | | | |Land and Expand Strategy
LAND:
- Entry point identification
- Low-friction starting point
- Prove value quickly
- Build relationships
EXPAND:
- Cross-sell opportunities
- Upsell pathways
- Geographic expansion
- Departmental expansion
EXPANSION TRIGGERS:
- New executive hire
- Budget cycle timing
- Company growth/expansion
- Competitive displacement
- Contract renewal
- New initiatives announcedRevenue Operations
RevOps Framework
REVOPS PILLARS:
PROCESS:
- Lead management
- Opportunity management
- Account management
- Renewal management
SYSTEMS:
- CRM administration
- Marketing automation
- Sales tools
- Analytics platforms
DATA:
- Data quality
- Reporting and analytics
- Dashboards
- Forecasting
STRATEGY:
- Go-to-market alignment
- Territory design
- Compensation design
- Performance managementSales Compensation
COMP PLAN DESIGN:
TARGET EARNINGS:
Base Salary + Variable (OTE)
TYPICAL MIX:
| Role | Base | Variable |
|------|------|----------|
| AE (Enterprise) | 50% | 50% |
| AE (Mid-Market) | 50% | 50% |
| SDR | 70% | 30% |
| AM/CSM | 70% | 30% |
VARIABLE COMPONENTS:
- Quota attainment (primary)
- Accelerators (above quota)
- SPIFs (special incentives)
- MBOs (objectives)
QUOTA SETTING:
- Top-down: Company target → Rep quotas
- Bottom-up: Territory potential → Rep quotas
- Hybrid: Balanced approachTerritory Design
TERRITORY PRINCIPLES:
BALANCE:
- Equal opportunity
- Similar workload
- Fair distribution
COVERAGE:
- No gaps
- Minimal overlap
- Clear boundaries
EFFICIENCY:
- Geographic logic
- Account alignment
- Growth potential
TERRITORY METRICS:
- Accounts per rep
- Revenue per territory
- Quota achievement variance
- Win rate varianceSales Analytics
Sales Dashboard KPIs
| Category | Metrics |
|---|---|
| Activity | Calls, meetings, emails, proposals |
| Pipeline | Created, coverage, velocity |
| Performance | Quota attainment, win rate, deal size |
| Productivity | Revenue per rep, time to productivity |
| Customer | Retention, expansion, NPS |
Rep Performance Analysis
PERFORMANCE METRICS:
LEADING INDICATORS:
- Activity volume
- Pipeline creation
- Meeting conversion
- Proposal volume
LAGGING INDICATORS:
- Revenue closed
- Quota attainment
- Win rate
- Average deal size
DIAGNOSTIC ANALYSIS:
If low activity → Motivation, time management
If low conversion → Skills, messaging
If low win rate → Qualification, competition
If low deal size → Targeting, value sellingReferences
- Sales Methodologies Reference - MEDDIC, SPIN, Challenger, Solution Selling details
- Sales Enablement Reference - Content framework, playbooks, training curriculum
See Also
© travisjneuman, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/sales of travisjneuman/.claude.
- SKILL.md
- references/sales-enablement.md
- references/sales-methodologies.md
Open the folder on GitHubat commit 446a461
Compare with similar skills
Sales 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 |
|---|---|---|---|---|---|---|
| Sales this skilltravisjneuman/.claude | 100 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Account ExecutiveaAAaqwq/AGI-Super-Team | 105 | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Pipeline ReviewTheCraigHewitt/skills | 159 | — | ~5.7k | Automated safety check: Pass | MIT | |
| SaaS Revenue Operations Analyzeralirezarezvani/claude-skills | 28k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| B2B Lead Generationminhnv0807/ai-business-skills | 609 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Revopssickn33/agentic-awesome-skills | 47k | 2 repos | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
Pipeline Review
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.
SaaS Revenue Operations Analyzer
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.
B2B Lead Generation
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
Revops
sickn33/agentic-awesome-skills
Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation.
Sales Pipeline
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…
More from travisjneuman/.claude
All 17 skills in this repoTest Specialist
travisjneuman/.claude
Test-writing patterns for JS/TS, Python, Go, and Rust (unit, integration, E2E, visual regression).
Codebase Documenter
travisjneuman/.claude
Write codebase documentation: READMEs, architecture docs, getting-started guides, API docs, and code comments.
Business Strategy
travisjneuman/.claude
Business strategy expertise for strategic planning, competitive analysis, market entry, M&A strategy, portfolio management, and strategic decision-making.
Data Science
travisjneuman/.claude
Data science and analytics expertise for statistical analysis, machine learning pipelines, data governance, business intelligence, predictive modeling, and analytics strategy.
Finance
travisjneuman/.claude
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions.
Health Wellness
travisjneuman/.claude
Workplace health and wellness expertise for employee wellness programs, mental health initiatives, ergonomics and safety, healthcare benefits strategy, and health analytics.
Related
Categories
Questions about Sales
What does Sales do?
Sales strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline management, sales enablement, and revenue operations. claude. Sales strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline management, sales enablement, and revenue operations.
When should I use Sales?
Sales fits situations like: building sales processes; qualifying deals; managing pipelines; improving close rates.
How do I install Sales in Claude Code?
Run `npx skills add travisjneuman/.claude --skill sales -a claude-code`. Or copy the skill folder (skills/sales in travisjneuman/.claude) into .claude/skills/sales in your project. Claude Code loads it when a task matches its description.
How do I install Sales in Codex?
Run `npx skills add travisjneuman/.claude --skill sales -a codex`. Or copy the skill folder (skills/sales in travisjneuman/.claude) into .agents/skills/sales in your project. Codex loads it when a task matches its description.
Can I use Sales in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add travisjneuman/.claude --skill sales -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sales, .gemini/skills/sales, .github/skills/sales and .opencode/skills/sales in your project.
What does Sales need to run?
SKILL.md names no scripts, command-line tools or credentials: Sales is instructions for the agent only.
Does Sales access the network?
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.
Is Sales safe to install?
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.
What licence does Sales use?
Sales is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sales use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Sales?
Skills that share tags, products or a category with Sales: Account Executive (aAAaqwq/AGI-Super-Team, 105 stars), Pipeline Review (TheCraigHewitt/skills, 159 stars), SaaS Revenue Operations Analyzer (alirezarezvani/claude-skills, 28k stars) and B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sales?
travisjneuman (a GitHub user) maintains it in travisjneuman/.claude, which has 100 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 9, 2026.
Source: travisjneuman/.claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.