agentsclimarketplace

Enable sales cs

Skill alexe-ev/product-plugins/gtm/skills/enable-sales-cs

Skill library for AI agents — 15 product domains, 121 skills. Tells the agent what to ask, how to reason, and what to output.

Install
npx -y skills add alexe-ev/product-plugins --skill enable-sales-cs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 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.

What its author says it does

Copied from the file, not written here

Structure sales and customer success enablement materials and collaboration workflows. Use this skill when a team needs to prepare sales and CS for a launch, feature update, or positioning change.

SKILL.md

2.2 KB, 438 tokens by cl100k_base, as published. Nobody here has run it

Enable Sales & CS

Purpose

Help product teams create effective enablement for sales and customer success so they can accurately represent and support the product.

Skill type

Conceptual skill

Use this skill when

  • A product launch requires sales and CS to be prepared
  • Sales is pitching incorrectly or with outdated messaging
  • CS is escalating questions that product should have documented
  • A new feature needs internal rollout materials before external launch

Do not use this skill when

  • The goal is customer-facing marketing messaging (use develop-positioning-messaging)
  • The product isn't ready for internal enablement yet

Required inputs

  • Feature or product being enabled
  • Target sales or CS audience (AE, SDR, CSM, support)

Optional inputs

  • Positioning and messaging documents
  • Common objections heard in sales
  • CS support patterns and escalations
  • Demo environment access

Upstream context

Works best when:

  • Positioning is defined
  • Product is launch-ready or in beta

Downstream handoff

Output can feed:

  • plan-product-launch (enablement is part of the launch checklist)
  • analyze-churn-retention (CS insights feed back into product)

Instructions

  1. Define what sales and CS need to know: positioning, value prop, use cases, objections.
  2. Write a product overview brief (1-pager).
  3. Write an objection handling guide.
  4. Define what to demo and how.
  5. Identify escalation paths for complex questions.
  6. Define feedback loops from sales and CS back to product.

Output

Provide:

  • Product brief for internal use (positioning, key messages, use cases)
  • Objection handling guide
  • Demo flow outline
  • Escalation paths
  • FAQ (common questions with answers)
  • Feedback loop process from CS/sales to product

Risks / caveats

  • Enablement materials that aren't used are wasted — design for how teams actually work
  • Sales will sell what they can explain, not what is technically correct — simplify ruthlessly
  • CS escalations are a product signal — close the feedback loop

Gives 0 of the 12 instructions most sales crm skills give in 438 tokens

Counted across 361 of the 361 authors here whose files we hold, read 2026-08-06

  • Read product marketing context before writing if it existsin 22 of 361, across 14 files
  • keep the ask low-frictionin 16 of 361, across 7 files
  • Call RUBE_SEARCH_TOOLS firstin 15 of 361, across 5 files
  • personalize every outbound messagein 13 of 361, across 4 files
  • confirm connection status is activein 13 of 361, across 4 files
  • Keep forwardable blurbs under 100 wordsin 13 of 361, across 4 files
  • State if personalization context is missingin 13 of 361, across 4 files
  • Cut any sentence that does not drive a replyin 13 of 361, across 4 files
  • Use proof instead of adjectivesin 12 of 361, across 3 files
  • Use a single, low-friction call to actionin 12 of 361, across 4 files
  • Calibrate tone to the specific audiencein 12 of 361, across 3 files
  • Make each follow-up email add new valuein 12 of 361, across 6 files

Said here and by no other author read

  • define positioning, value prop, use cases, and objections
  • write a product overview brief
  • write an objection handling guide
  • define what to demo and how
  • identify escalation paths for complex questions
  • define feedback loops back to product

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.