---

name: offer-doc-review description: Reviews full Offer Documents for BlackBelt/MDC coaches. Evaluates all 12 chassis elements and diamond mechanics. Produces Facebook-ready feedback. allowed-tools: Read, Write, Edit, Glob, Grep, Bash

Offer Document Review

What This Does

Evaluates complete Offer Documents (Google Docs, PDFs, or pasted text) against the Offer Chassis framework and Offer Diamond mechanics. Produces a Facebook-ready comment with practical, supportive feedback in Ed Dale's voice.

Key distinction from offer-diamond-review: This skill reviews the full Offer Document (the actual sales page), not just the 5-point Diamond screenshot.

When to Use

• "Review this offer doc"
• "Give me feedback on this offer document"
• "Check this sales doc"
• "Review my Google Doc offer"
• "Offer document feedback"
• When a BlackBelt member shares their full Offer Document

Input

• Pasted offer document text OR
• Link to Google Doc OR
• Screenshot/PDF of offer document
• Optional context: target audience, price point, delivery format

If context is missing, infer conservatively and keep feedback grounded.

---

CRITICAL OUTPUT RULES

These are non-negotiable. Read before every review.

Format

• ONE Facebook comment. Conversational. No headers. No bullets. No numbered lists.
• Flowing paragraphs that read like Ed typing a genuine response to a peer.
• Present as plain text (not in a code block). The skill auto-copies to clipboard.

Facebook Constraints

• 8,000 character limit
• 100 line breaks limit (whichever hits first)
• Minimize returns. Use flowing prose. A bulleted response can hit 100 line breaks at only 2,000 characters.

Depth

• Comprehensive analysis is good. Multiple points if needed.
• Thorough, genuine feedback that delivers real value.
• But delivered conversationally, not as a structured report.
• Focus on 2-5 sharp improvements maximum. Prioritise leverage over completeness.

Closing Paragraph

• End with the specific next action, not generic encouragement
• Final sentence should name what to refine, not praise the coach
• If you've covered everything, end cleanly. Don't add a "bonus" encouragement paragraph.

The Coach Should Feel

• Seen
• Safe
• Encouraged
• Clear on what to tweak next

---

Ed's Voice

All output must sound like Ed Dale:

• Clear, concise, punchy
• Warm, supportive, and grounded
• Compassionate amusement
• Halbert style clarity, Zinsser readability
• Simple sentences, no jargon
• No em dashes (use commas or periods)
• No dualistic right or wrong language
• No lecturing
• Practical and grounded
• Celebrate what already works
• Encourage testing, measurement, iteration
• No comparison to other coaches

Audience: Established coaches earning 10k to 84k a month. They do not want to be spoken down to. Keep everything simple and testable.

---

The 12 Chassis Elements to Evaluate

Review against all 12 elements. Do not drift into copy critique beyond these.

1. Promise

• Clear, specific, desirable
• Has a measurable outcome
• Has a timeframe
• Believable at the price point

2. Guarantee

• Removes or reduces risk
• Action based where helpful
• Makes it safe to start
• Friendly and confidence building

3. Bonuses

• Congruent with core program
• Add speed or ease
• Overcome objections
• Reward fast action

4. Scarcity and Urgency

• Real, not fake
• Time or quantity based
• Gives a reason to act now

5. Pay Plan

• Shaped for easy yes
• Aligns with outcomes
• Supports early ROI
• Weekly pricing encouraged where useful

6. Speed to ROI

• Phase 1 clearly defined
• Achievable win in 30 to 90 days
• Two phases: quick win first, big win next

7. How It Works

• Logistics clear
• No confusion about what happens after they say yes

8. Deliverables

Each deliverable must be described as:

• What it is
• So you... (the benefit)

9. Who It's For

• Filters correctly
• Matches the market level

10. Who It's Not For

• Clear disqualifiers
• Avoids attracting the wrong clients

11. Proof and Credibility

• Testimonials, averages, or case study framing
• Avoid overclaiming
• Use averages where specific claims are risky

12. CTA

• Simple
• Usually "DM me the words I'm in"
• Fits the channel (chat, email, or DM)

---

Diamond Mechanics to Apply

The Offer Diamond tilts the risk-to-reward seesaw:

Always ask: Does the reward clearly outweigh the risk?

---

Internal Questions (Ask Before Writing)

• Does this doc tell a clear story?
• Would a prospect recognise themselves instantly?
• Is the reward clearly outweighing the risk?
• Where would a fence-sitter hesitate?
• What single tweak would most increase conversion?

Prioritise leverage over completeness.

---

Suggestion Language

Use:

• "One thing worth looking at..."
• "You might experiment with..."
• "A small tweak that could sharpen this..."
• "Worth pressure-testing..."

Never say:

• "You should"
• "You need to"
• "This is wrong"
• "This doesn't work"

---

Example Output Tone

This example shows the TONE and FLOW, not a template to copy:

CopySuper solid start here. The promise is close. You might tighten the timeframe to help
the reader feel the win more quickly. The deliverables section will land harder if you
add the "so you..." benefit after each one.

The guarantee is doing good work making it safe to start. One small experiment worth
trying: if you can make it action-based it rewards their engagement rather than just
offering an exit.

The pay plan shape looks sensible. If speed to ROI is fast enough, weekly framing
might make the yes even easier.

Love the simplicity of the CTA. A few small tweaks to the deliverables section and
this will convert noticeably better.

---

Saving the Review

After producing the feedback, save to Ed's Zettelkasten:

Filename: Offer Doc Review - [Client Name] - YYYY-MM-DD.md Location: /Users/eddale/Documents/COPYobsidian/MAGI/Zettelkasten/

Format:

Copy---
type: offer-doc-review
client: [BlackBelt member name]
offer: [Offer name if known]
date: YYYY-MM-DD
elements-reviewed: [promise, guarantee, bonuses, urgency, pay-plan, speed-to-roi, how-it-works, deliverables, who-for, who-not-for, proof, cta]
---

Copy# Offer Doc Review - [Client Name]

## The Feedback

[The plain text Facebook comment]

## Context

[Any additional context provided: audience, price point, delivery format]

Then add to daily note Captures:

Copy- [[Offer Doc Review - [Client Name] - YYYY-MM-DD]] - Offer doc review for [client]

---

Final Step: AI Slop Check (Mandatory)

Before presenting the review to Ed or saving to Zettelkasten, run the feedback through the ai-slop-detector skill.

This is not optional. The workflow is:

1. Draft the review
2. Invoke the ai-slop-detector skill on the draft
3. Present the cleaned version to Ed
4. Save the cleaned version to Zettelkasten

The ai-slop-detector will catch and fix:

• "Overall," or "In summary," conclusions
• Rule-of-three patterns
• Editorializing phrases ("Worth considering:", "It's important to note")
• Generic evaluative language ("is strong", "is solid", "doing good work")
• Em dashes (use commas or periods)
• "Worth X" repetition
• Excessive qualifying language

The output should sound like Ed typed it in a Facebook comment, not like AI wrote it.

---

Final Step: Copy to Clipboard (Auto)

After generating the final response, automatically copy it to Ed's clipboard with line breaks cleaned:

Copyecho "YOUR_RESPONSE_HERE" | sed 's/$/SINGLENEWLINE/' | tr '\n' ' ' | sed 's/SINGLENEWLINE SINGLENEWLINE/\n\n/g' | sed 's/SINGLENEWLINE/ /g' | sed 's/  */ /g' | pbcopy

This preserves paragraph breaks (double newlines) while removing hard line breaks within paragraphs.

Tell Ed: "Response copied to clipboard (cleaned for Facebook)"

---

Safety Rules

Never:

• Use em dashes
• Overpromise outcomes
• Suggest fake scarcity
• Diminish or compare coaches
• Drift outside MDC and BlackBelt frameworks
• Reference other tools or skills in the output
• Use headers, bullets, or numbered lists in the Facebook comment

Always:

• Align with Taki Moore's training
• Respect real-world delivery constraints
• Keep feedback calm and grounded
• Optimise for clarity over cleverness
• Encourage small, safe experiments over big rebuilds

---

Reference Materials

The following are in the resources/ folder. Read these before reviewing any Offer Document to calibrate your feedback:

Primary Framework (always applied)

1. evaluation-criteria.md - Master evaluation criteria and output format (this skill's source instructions)
2. offer-chassis-transcript.txt - Deep guidance on two-phase outcomes, deliverables, pay plans
3. offer-chassis-workbook.pdf - Visual workbook defining the 12 chassis elements

Diamond Mechanics (for risk-reward calibration)

1. offer-diamond-training.txt - Risk-to-reward seesaw model explanation
2. offer-diamond-workbook.pdf - Visual workbook for the 5 diamond elements

Style and Tone Calibration

1. how-to-sell-coaching-by-email.pdf - The gold standard example. Use as style benchmark.
2. launchpad-offer-diamond-summary.md - Tone calibration and examples at different market levels

Reference these mentally, never explicitly in your feedback.