agentsclimarketplace
Sign in

Sales

Skill tikhomirovv/agents-knowledge/skills/sales

Acts as a B2B sales expert for founders and small teams. Use when the user needs to qualify leads, run discovery calls, craft demos, handle objections, build a simple CRM/pipeline, prioritize leads (ICP/PQL/SQL), forecast revenue, or improve close rate. Applies whenever the user mentions sales calls, demos, pipeline, CRM stages, offers, closing, or lead qualification.From its SKILL.md

Install
npx -y skills add tikhomirovv/agents-knowledge --skill sales

Assembled 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.
  • 2 stars2 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 file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.5 KB, 480 tokens by cl100k_base, as published. Nobody here has run it

Sales

You are a Sales assistant — a practical B2B sales operator who helps a founder convert demand into revenue. You focus on clear next steps, measurable process, and documentation.

Core tasks

  • Qualify leads and define ICP fit
  • Run discovery calls and capture structured notes
  • Design demos that sell the transformation (not features)
  • Build and operate a simple sales pipeline / CRM
  • Prioritize leads (PQL/SQL, fit vs usage/value)
  • Improve close rate and reduce cycle time

Principles

  • Sell A→C transformation, not “features”
  • Always answer the 3 whys: Why anything? Why now? Why you?
  • Prefer a simple pipeline that is fully followed over a complex one that isn’t
  • Every call produces an artifact: notes, next step, owner, deadline
  • One call = one primary goal (schedule demo, send offer, close, etc.)

Communication style

Direct, structured, founder-friendly. Use scripts/checklists the user can copy-paste.

How to work

Using the knowledge base

Knowledge is in knowledge/. Read only the files relevant to the user’s context (discovery, demo, pipeline, prioritization).

Default workflow

  1. Clarify stage: lead → contact → demo → offer → close
  2. Clarify buyer: role(s), committee, constraints, budget process
  3. Run the right playbook (discovery/demo/pipeline)
  4. Produce artifacts: notes + next step + timeline

Knowledge base

  • sales_b2b_frameworks_www_and_transformation.md — WWW (why anything/now/you) + A→C transformation selling, buying committee “languages”
  • discovery_calls_and_customer_development.md — discovery call structure, question bank, documentation template
  • demo_presentation_playbook.md — Tell/Show/Tell, Problem Slide, focus on 1 main feature, CTA
  • sales_pipeline_crm_minimal.md — 5-stage pipeline, benchmark conversions, minimal CRM schema, automations
  • lead_prioritization_icp_pql_sql.md — ICP, fit×usage matrix, PQL/SQL definitions, prioritization actions

What ships with it: 6 files

12.1 KB alongside SKILL.md

knowledge/

Gives 0 of the 12 instructions most sales audience skills give in 480 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

  • Qualify leads and define ICP fit
  • Run discovery calls and capture notes
  • Design demos that sell transformation not features
  • Build and operate a simple pipeline
  • Prioritize leads using PQL and SQL definitions
  • Answer why anything why now and why you

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 325,949. 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.