Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Map expressed buyer concerns to factual answers, supporting evidence and improvements to the offer.
--- name: objection-destroyer description: Turn objections into reasons to buy by shifting beliefs instead of pushing harder. Use when people hesitate, conversions are lower than expected, or the offer is strong but not selling. Uncovers surface and hidden objections, maps belief shifts, attaches proof, and generates reusable DM-ready responses — outputs OBJECTIONS.md. --- # Skill: Objection Destroyer (Belief Shift Engine) ## Purpose Turn objections into reasons to buy. This skill: - uncovers hidden resistance - translates doubt into clarity - shifts beliefs instead of pushing harder - increases trust and conversions Goal: remove every internal “no” before it appears. --- ## When to Use Activate this skill when: - people hesitate but don’t say why - conversions are lower than expected - buyers say “I’ll think about it” - the offer is strong but still not selling - objections repeat in DMs or calls - trust feels low --- ## Inputs This skill works with: - an `OFFER.md` - a pitch or sales page - customer feedback - sales call notes - known objections (or none → infer them) --- ## Core Outcome The assistant produces: - a list of visible and hidden objections - the belief behind each objection - a reframed belief (belief shift) - proof or mechanism to support the new belief - objection-handling statements ready to use --- ## Assistant Behavior ### 1. Identify surface objections List obvious objections: Common: - “It’s too expensive” - “I don’t have time” - “This won’t work for me” - “I need to think about it” - “I can do it myself” --- ### 2. Uncover hidden objections Go deeper. Each objection hides a belief. Example: - “Too expensive” → “I’m not sure it’s worth it” - “No time” → “This will take too much effort” - “I’ll think about it” → “I don’t trust this yet” Map: Objection → Hidden belief --- ### 3. Categorize objections Group into: #### Value - not worth the price #### Trust - won’t work - lacks proof #### Effort - too hard - too complex #### Time - takes too long #### Identity - “this is not for me” #### Risk - fear of failure or loss --- ### 4. Create belief shifts Replace limiting beliefs with stronger ones. Format: Old belief → New belief Example: - “This is risky” → “This is a safe, guided path” - “This takes too long” → “I can see results quickly” Rules: - simple - believable - grounded in reality --- ### 5. Attach proof to each belief A belief without proof fails. Use: - testimonials - case studies - examples - logic - demonstration - mechanism explanation Format: Belief shift → Proof --- ### 6. Rewrite as selling points Turn objections into persuasive statements. Format: Objection → Reframe → Proof Example: - “I don’t have time” → “This is designed to save you time” → “Most users get their first result in under 30 minutes using the template” --- ### 7. Integrate into offer Place objection handling in: - sales page - pitch - content - FAQs - DMs Make it proactive, not reactive. --- ### 8. Strengthen weak areas If objections repeat, improve the offer: - add proof - simplify process - reduce effort - clarify outcome - improve guarantee --- ### 9. Prioritize key objections Focus on: - top 3–5 objections - highest impact on buying decision Avoid overloading. --- ### 10. Create reusable responses Generate: - short answers (DMs) - medium answers (landing page) - long explanations (sales page) --- ## Output Format ```md # OBJECTIONS.md ## 1. Surface Objections 1. Objection 2. Objection 3. Objection ## 2. Hidden Beliefs - Objection → Underlying belief ## 3. Objection Categories - Value - Trust - Effort - Time - Identity - Risk ## 4. Belief Shifts - Old belief → New belief ## 5. Proof Mapping - Belief shift → Proof ## 6. Objection Handling Statements ### Objection 1 - Objection: - Reframe: - Proof: ### Objection 2 - Objection: - Reframe: - Proof: ### Objection 3 - Objection: - Reframe: - Proof: ## 7. Top Objections to Address - Priority list ## 8. Integration Points - Where to use each response ## 9. Offer Improvements Needed - What to fix in the offer ## 10. Short Responses (DM-ready) - Quick replies ``` ⸻ Decision Rules Go deeper when: • objections sound generic • users are vague • “I’ll think about it” appears often Add proof when: • trust is low • claims feel strong • results seem uncertain Reframe when: • objection is emotional • logic alone is not enough Fix the offer when: • objection is valid • friction is real • results are unclear ⸻ Before vs After Example Before • “It’s too expensive” After • “This replaces months of trial and error and helps you get your first result fast, which makes the investment small compared to the outcome” ⸻ Style Guidelines • be clear and direct • avoid defensive tone • focus on belief, not argument • keep it simple • support claims with proof ⸻ Success Criteria The skill works when: • objections are addressed before they arise • buyers feel understood • trust increases • hesitation decreases • conversions improve
Map expressed buyer concerns to factual answers, supporting evidence and improvements to the offer.
The structured plan or review specified in the original, with evidence and open questions.
Confirm task inputs, follow the source workflow and apply the explicit M11 qualifications below.
Offer, actual buyer questions or call notes, and verifiable evidence for proposed answers.
Hidden beliefs are hypotheses to check with the buyer, not facts. A budget or time constraint may be literal and valid. Respect a clear no; address weaknesses rather than reframing them away. Sample 30-minute results and savings claims are illustrative and must not become sales evidence. Draft replies only; no outreach is sent.
Use Buyer Objection Clarification for [BUSINESS/TASK]. Ask for missing inputs: Offer, actual buyer questions or call notes, and verifiable evidence for proposed answers. Return the source output format and label evidence, assumptions and validation steps. Hidden beliefs are hypotheses to check with the buyer, not facts. A budget or time constraint may be literal and valid. Respect a clear no; address weaknesses rather than reframing them away. Sample 30-minute results and savings claims are illustrative and must not become sales evidence. Draft replies only; no outreach is sent.
Overriding a refusal, mind-reading hidden motives or fabricating testimonials and response statistics.
M11 added task routing, German terms, scope and evidence requirements while preserving original authorship. Hidden beliefs are hypotheses to check with the buyer, not facts. A budget or time constraint may be literal and valid. Respect a clear no; address weaknesses rather than reframing them away. Sample 30-minute results and savings claims are illustrative and must not become sales evidence. Draft replies only; no outreach is sent.
MIT License Copyright (c) 2026 Alessandro Smedile Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.