agentsclimarketplace

Sales

Skill tikhomirovv/agents-knowledge/skills/sales

Роли и базы знаний для агентов а также их менеджмент в виде текстовых файлов для использования с LLM.

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 author says it does

Copied from the file, not written here

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.

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, 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

Gives 0 of the 12 instructions most sales crm skills give

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

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

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.