Sales catchall
Skill Chipagosfinest/enterprise-team/enterprise-team/skills/sales-catchall
Routes sales requests to the correct specialist: account management, technical sales, business development, partnerships, or customer success. Triggers: sales strategy, close deal, demo, POC, partnership, customer retention, onboarding, expansion, lead generation, pipeline, revenue, quota, negotiation, proposal, RFP, customer health, churn.From its SKILL.md
npx -y skills add Chipagosfinest/enterprise-team --skill sales-catchallAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 308 tokens by cl100k_base, as published. Nobody here has run it
Sales Department
Routes sales work to the appropriate specialist role.
Routing Targets
| Role | Handles |
|---|---|
| account-executive | Sales cycles, deal negotiation, closing, relationship management, proposals |
| sales-engineer | Technical demos, POCs, technical validation, solution architecture for prospects |
| business-developer | New business opportunities, market expansion, lead generation, outbound |
| partnerships-manager | Strategic alliances, channel programs, co-marketing, integration partnerships |
| customer-success-manager | Retention, onboarding, health scores, renewals, expansion, churn prevention |
Examples
- "Close the deal with Acme Corp" -> account-executive
- "Build a technical demo for the enterprise prospect" -> sales-engineer
- "Find new leads in the fintech vertical" -> business-developer
- "Negotiate the integration partnership with Stripe" -> partnerships-manager
- "Reduce churn in our enterprise segment" -> customer-success-manager
- "Respond to this RFP" -> account-executive + sales-engineer
- "Set up onboarding for the new customer" -> customer-success-manager
Workflow
- Identify the stage of the sales cycle: prospecting, qualifying, demo, negotiation, close, or post-sale.
- Pre-sale technical work routes to sales-engineer; post-sale retention routes to customer-success-manager.
- For ambiguous sales requests, default to account-executive.
- For partner-related revenue, route to partnerships-manager.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most sales audience skills give in 308 tokens
Counted across 401 of the 401 authors here whose files we hold, read 2026-08-07
- Read product marketing context before asking questionsin 21 of 401, across 11 files
- Acknowledge competitor strengths honestlyin 18 of 401, across 7 files
- Start every page with a summaryin 15 of 401, across 4 files
- Use a single, low-friction call to actionin 15 of 401, across 7 files
- Create a single source of truth for each competitorin 14 of 401, across 3 files
- Make each follow-up email add new valuein 11 of 401, across 5 files
- Cut any sentence that does not drive a replyin 10 of 401, across 4 files
- Tie personalization directly to the problemin 10 of 401, across 4 files
- Write paragraph comparisons for each dimensionin 9 of 401, across 3 files
- Link between related competitor pagesin 9 of 401, across 3 files
- Keep subject lines short and lowercasein 9 of 401, across 3 files
- Define ideal customer profile from top customersin 9 of 401, across 3 files
Said here and by no other author read
- identify the stage of the sales cycle
- route pre-sale technical work to sales-engineer
- route post-sale retention to customer-success-manager
- default ambiguous requests to account-executive
- route partner-related revenue to partnerships-manager
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.