Find the most effective way to present the product's Process — the named Mechanism that makes the offer feel different from every other claim in the category. TRIGGER when a piece or offer needs its distinctive Mechanism named or sharpened. DO NOT TRIGGER to build the whole offer (draft-offers), to plan a piece (plan-copy), or to find the piece's core idea (big-idea).
Scanned 9/5/2026
Install to Claude Code
npx -y skills add heyJordanParker/dotfiles --skill mechanism --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mechanism?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/heyjordanparker-mechanism)More formats (shields.io, HTML) on the badges page.
---
name: mechanism
description: Find the most effective way to present the product's Process — the named Mechanism that makes the offer feel different from every other claim in the category. TRIGGER when a piece or offer needs its distinctive Mechanism named or sharpened. DO NOT TRIGGER to build the whole offer (draft-offers), to plan a piece (plan-copy), or to find the piece's core idea (big-idea).
---
# Mechanism
One Process: name the product's real Process in the way that makes the offer feel like the only way to the result. Grounded in the product's facts, delivered as options the owner picks from — the owner owns how his product is presented. The Mechanism is the named version of the Process the Market sees; the Process itself lives in the product facts.
## 1. Ground the Mechanism in the real Process
Read the product's facts for what actually happens and in what order. The Mechanism is why it works, drawn from the true Process — never a label invented at the desk.
### Establish the causal chain before naming it
A Mechanism is the causal chain, not a label for the outcome. Trace it in the product's facts: what actually happens, in what order, and how it handles the awkward cases. The name is chosen AFTER that chain is established, to point at it. An outcome restated as a name fails — a name that just repeats what the product delivers names nothing.
### Keep the name inside the documented chain
The name may claim no more of the chain than the facts document. Where supporting parts do real work, the presentation names them too, or the claim narrows to what the named part alone does. A name that credits one part for a result the whole chain produces over-claims.
## 2. Present it to create pull, not to explain
Owner doctrine: copy is a trailer, not the reveal — do not spoil what is sold by giving the whole method away. Start with the Mechanism that leads to a result the reader wants; the reader should feel that everyone is using this new thing but them, not walk away with a how-to.
## 3. Earn belief before the how
Owner law: before the reader wants the how, they must believe the result is possible. The Mechanism lands only after possibility is established. At high market sophistication (stages 3–4) a distinctive Mechanism is what separates the offer from identical promises.
## 4. Run the shared idea process
Fan the ways to frame the Mechanism through the shared idea process (see ideate): brainstorm wide → fresh-context adversarial reviewers refute → survivors iterate against the criticism → 3–5 survivors reach the owner. Each survivor traces to the real Process.
Verification: each survivor traces to the real Process, presents as pull rather than full reveal, and reaches the owner as options through the ideate process.

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!