agentsclimarketplace
Sign in

Advise sales revenue skills

Skill the-long-ride/skill-master/skills/advise-sales-revenue-skills

Use when a human wants to design, evaluate, or improve AI agent skills for sales, revenue, account planning, prospecting, deal research, CRM hygiene, outreach, pipeline review, or customer-facing sales workflowsFrom its SKILL.md

Install
npx -y skills add the-long-ride/skill-master --skill advise-sales-revenue-skills

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

  • 1 stars1 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

5.0 KB, 969 tokens by cl100k_base, as published. Nobody here has run it

Sales And Revenue Skill Advisor

Overview

Advisor for designing, evaluating, and improving AI agent skills in the sales & revenue domain. Use this skill to turn a vague skill idea into a compact skill blueprint, not to perform the domain work itself.

When To Use

Use when a human asks to design, review, improve, migrate, publish, or validate an AI agent skill for sales & revenue. Use when trigger quality, workflow shape, failure recovery, output format, references, scripts, or validation need improvement. Do not use when the human wants the agent to directly perform the sales & revenue task instead of designing the skill.

Inputs And Tools

  • User's skill idea, draft SKILL.md, target runtime, example prompts, and any existing references, scripts, or assets.
  • Repository skill files, routing metadata, and validation reports when improving an existing repository.
  • Read-only inspection first; ask before edits, publishing, running commands, or spawning agents.

Workflow

  • Separate skill-design advice from target-domain execution.
  1. Identify the sales workflow: prospecting, account research, outreach drafting, call prep, CRM update, pipeline review, proposal support, or renewal.
  2. Define the source systems: CRM, email, calendar, call transcript, account notes, product docs, pricing, and approved messaging.
  3. Separate draft generation from sending, updating, or committing customer-facing actions.
  4. Define personalization rules, factual grounding, and approval requirements.
  5. Specify validation for account facts, deal stage, next steps, and contact details.
  6. Return a sales-skill blueprint with guardrails and examples.

Category Standards

  • Keep the skill compact enough to trigger reliably and load without flooding context.
  • Prefer reusable reference files and scripts for heavy domain-specific details.
  • Ground account claims in CRM or supplied sources.
  • Never fabricate customer facts, budgets, competitors, or commitments.
  • Treat external outreach as draft-only unless explicit approval exists.
  • Respect do-not-contact, territory, and account ownership rules.
  • Include next-step and CRM hygiene checks.
  • Keep tone aligned with approved sales messaging.

Verification

  • Run at least two realistic prompts: one that should trigger the skill and one that should not.
  • Check that the skill asks for missing inputs before giving brittle advice.
  • Confirm failure modes include recovery behavior, not only warnings.
  • Confirm validation commands or manual checks are safe for the target runtime.

Checklist

  • Examples show concrete input and expected output.
  • Verification can be repeated by a human or another agent.
  • Trigger description names sales, revenue, CRM, account, prospecting, deal, outreach, or pipeline.
  • Workflow defines source-of-truth systems.
  • Skill distinguishes internal prep from external communication.
  • Failure modes cover stale CRM data, missing contact info, policy conflicts, and accidental sending.
  • Output format matches the sales artifact.
  • Validation includes a hallucination-resistance prompt.

Nice To Have

  • Trigger collision notes for adjacent skills.
  • PASS/PARTIAL/FAIL verification rubric.
  • CRM field map.
  • Approved outreach templates.
  • Qualification framework reference.
  • Account research checklist.
  • Objection and competitor battlecard references.

Example Skill Ideas

  • Account brief builder skill.
  • Sales call prep skill.
  • CRM cleanup skill.
  • Renewal risk summary skill.

Examples

Input: "Help me design a skill for sales & revenue workflows that reviews drafts and flags missing evidence." Output: A compact skill blueprint with trigger description, ordered workflow, resources, failure recovery, validation prompts, and output format.

Input: "This sales & revenue skill triggers too often and gives generic advice." Output: A revision plan that narrows triggers, moves heavy details to references, adds examples, and defines repeatable verification.

Failure Modes

  • CRM data is stale: mark uncertainty and ask for confirmation before using it externally.
  • Contact rules are unclear: avoid outreach and request ownership or consent details.
  • Pricing or discounting is requested: require approved pricing source and human review.
  • Customer commitment is ambiguous: quote the source or label it as unconfirmed.

Human Verification

Score the revised skill before calling it ready:

Discovery: PASS | PARTIAL | FAIL
Content: PASS | PARTIAL | FAIL
Verification: PASS | PARTIAL | FAIL
Critical gaps:
1. <gap>
Required fixes:
1. <fix>
Decision: READY | NEEDS REVISION

Output Format

Return:

Skill concept: <name>
Sales workflow: <workflow>
Trigger description draft: <Use when...>
Source systems:
- <source>
Guardrails:
- <rule>
Validation:
- <check>
Failure recovery:
- <mode and recovery>

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

  • separate skill design from domain execution
  • identify the specific sales workflow
  • define the relevant source systems
  • separate draft generation from customer actions
  • define factual grounding and approval requirements
  • specify validation for account facts

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.