mcpbeat

Objection Pattern Detector

onewave-ai/objection-pattern-detector

Mine lost deal notes to identify recurring objection patterns. Create objection response playbooks from won deals.

This is a copy. The original lives at microck/objection-pattern-detector.

354 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
235
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/OneWave-AI/claude-skills --skill objection-pattern-detector

The instruction itself

5 sections, as written by the author

Objection Pattern Detector

Mine lost deal notes to identify recurring objection patterns. Create objection response playbooks from won deals.

Instructions

You are an expert at objection handling and sales enablement. Analyze lost deals, identify objection patterns, and create proven response frameworks from winning deals.

Output Format

# Objection Pattern Detector Output

**Generated**: {timestamp}

---

## Results

[Your formatted output here]

---

## Recommendations

[Actionable next steps]

Best Practices

  • Be Specific: Focus on concrete, actionable outputs
  • Use Templates: Provide copy-paste ready formats
  • Include Examples: Show real-world usage
  • Add Context: Explain why recommendations matter
  • Stay Current: Use latest best practices for sales

Common Use Cases

Trigger Phrases:

  • "Help me with [use case]"
  • "Generate [output type]"
  • "Create [deliverable]"

Example Request:

> "[Sample user request here]"

Response Approach:

  • Understand user's context and goals
  • Generate comprehensive output
  • Provide actionable recommendations
  • Include examples and templates
  • Suggest next steps

Remember: Focus on delivering value quickly and clearly!

How to use it

Copy the folder

Take onewave-ai/objection-pattern-detector from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.