Skills

Wayland Close Rebuild

Diagnose a weak sales close and rebuild it as a full Cascade Close (Stack to Vision to...

Install

npx skills add FerroxLabs/wayland --skill wayland-close-rebuild -g -a claude-code -y
Repository
FerroxLabs/wayland616
Category
Business
Updated
5d ago
License
Apache-2.0
Context cost
Lightabout 946 tokens
Runs scripts
No, instructions only

What it does

Diagnose a weak sales close and rebuild it as a full Cascade Close (Stack to Vision to Math to Safety Net to Door, plus P.S. and P.P.S.). Use when the user has an existing close that under-converts and wants it diagnosed and rebuilt against the Three Locks and every buyer type. Do NOT use when the user needs a whole sales letter (use wayland-full-sales-asset) or only a headline (use wayland-headline-lab).

Interactive rebuild of a sales close. The Cascade Close converts every buyer type because it sequences proof against the Three Locks: Stack hits Want, Vision and Math hit Trust, Safety Net hits Excuse. Skip a beat and you lose that buyer type. Diagnose the existing close, then rebuild it as a full Stack to Vision to Math to Safety Net to Door sequence with P.S. and P.P.S. Review with the user at each beat.

Step 1: Gather the existing close (uses: convert-close)

Ask the user to paste the existing close: the section running from "and that's why I created..." through the buy buttons and P.S. If they do not have one yet, ask for the offer brief instead and plan to write the close from scratch. Capture exactly what they provide; do not invent a close.

  • Input: user-supplied existing close, or offer brief if no close exists
  • Output: the existing close text (or offer brief) captured for diagnosis
  • Key focus: get the real close text before diagnosing anything

Step 2: Infer the buyer-type mix (uses: convert-temperature)

From the close text, infer which buyer types this close must convert across the five: Logical, Emotional, Skeptical, Aspirational, Hesitant. State the inferred mix and the reasoning. The Cascade Close addresses all five, but the emphasis shifts with the mix. Show the inference and let the user confirm or override.

  • Input: the existing close from Step 1
  • Output: the inferred buyer-type mix with reasoning, confirmed by the user
  • Key focus: name the buyer mix so the rebuild can weight the right beats

Step 3: Diagnose the close against the Cascade beats (uses: convert-audit)

Audit the existing close in close-diagnosis mode against the buyer mix. Identify which Cascade beats (Stack, Vision, Math, Safety Net, Door, P.S., P.P.S.) are missing and which are weak, mapping each gap to the Lock and buyer type it fails. Show the diagnosis to the user.

Read the whole SKILL.md on GitHub

More in Business