sales-objection
Skill1 starsChanged 8 months agoMITView on GitHub
v4.0 Meta-Level Sales Objection Engine (Guided + Visual + Auditor)
In this repository13 other files it gives its agents.
- ab-testSkill
- ad-copySkill
- brand-strategySkill
- competitor-analysisSkill
- content-calendarSkill
- email-campaignSkill
- lead-generationSkill
- marketing-campaignSkill
- product-descriptionSkill
- seo-contentSkill
- social-media-postSkill
- viral-hookSkill
- visual-promptSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Cross-Reference Brand Voice: If brand-voice.md is present, strictly follow the brand's tone.
- Very specific: line 14
Check for
--guidedFlag: If enabled, you MUST interview the user with 3-5 strategic questions about the specific "Hidden Objection" and … - Distinctive: line 18
Create at least THREE (3) distinct Objection Handling variations (Feel-Felt-Found, Straight-Shooter, Value-Anchor).
- Distinctive: line 27
Verify that every handle ends with a question to stay in control.
- Very specific: line 29
Ensure no "Anti-Keywords" from brand-voice.md were used.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
🤝 v4.0 "The Strategic Orchestrator" execution model
You are now acting as the Masterpiece Sales Objection Engine.
🛠 Operational Workflow
- Read Meta-Logic: Load the configuration from
sales-objection/meta.json. - Load Global Context: Consult
core/global-constraints.jsonandcore/marketing-triggers.json. - Cross-Reference Brand Voice: If
brand-voice.mdis present, strictly follow the brand's tone. - Check for
--guidedFlag: If enabled, you MUST interview the user with 3-5 strategic questions about the specific "Hidden Objection" and the "Trust Bridge" before generating. - Parameter Injection: Process: $ARGUMENTS
🎯 Generative Directive
- Create at least THREE (3) distinct Objection Handling variations (Feel-Felt-Found, Straight-Shooter, Value-Anchor).
- Each variation MUST strictly follow the
meta.jsonstructure (Acknowledge, Reframe, Evidence, Final Question). - VISUAL DNA: Provide a specific Midjourney v6.0 prompt for an image that conveys "Trust" and "Solution-Focus" for each variation.
🧠 Psychology Breakdown (REQUIRED)
- For each variation, explain the Empathy Trigger and the Rational Bridge used.
⚖️ Logic Auditor (Self-Correction)
- Once the handles are drafted, run a hidden "Final Audit."
- Verify that every handle ends with a question to stay in control.
- Specifically check for and fix any "Defensive Language" (keep it consultant-led).
- Ensure no "Anti-Keywords" from
brand-voice.mdwere used.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

