# Conversion Strategy

> Use when the user needs to diagnose and reduce friction across high-value conversion paths; route here only when this decision boundary is the clear owner.

- Skill: `immamdouhaboammar/conversion-strategy` (Agent Skill, multi-file: 10 files)
- Install (CLI): `npx skillmds@latest add immamdouhaboammar/conversion-strategy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/immamdouhaboammar/conversion-strategy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: imMamdouhaboammar (https://skillmd.com/u/immamdouhaboammar)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/immamdouhaboammar/conversion-strategy

---


# Conversion Strategy

## Job

Diagnose and reduce friction across high-value conversion paths

Own this request only when **conversion intervention** is the clear decision boundary. If ownership is ambiguous or several functions compete, route to `marketing-council`. If the user explicitly asks for dependent work across functions, use `../../scripts/dynamic_router.py` to build a bounded DAG.

## Operating contract

1. Read `references/skill-spec.json` first for activation, invariants, workflow freedom, evidence rules, handoffs, and completion conditions.
2. Use `references/decision-model.md` when framing or challenging the decision.
3. Check `references/failure-modes.md` before finalizing a recommendation.
4. Render the response against `references/output-contract.md`.
5. Use packaged shared references or current external research only when they are load-bearing. Never present inference as evidence.

## Evidence discipline

Classify material claims as fact, inference, assumption, or unknown. Prefer supplied primary evidence. Verify current platform, policy, product, pricing, or market claims when freshness affects the recommendation. Do not fabricate research, tool calls, metrics, customer language, or causal proof.

## Routing

- Focused request: stay inside this Skill.
- Ambiguous or cross-functional ownership: hand to `marketing-council`.
- Explicit dependency chain: use `../../scripts/dynamic_router.py`.
- After Skill ownership is known, theory/agent selection may use `../../scripts/neural_router.py`; neural nodes never replace Skill routing.

## Execution connections

- Primary specialist: `../../agents/response-strategist.md`
- Skeptical counterweight: `../../agents/marketing-skeptic.md`
- Domain challenge gate: `../../hooks/causal-mechanism-check.md`
- Evidence gate: `../../hooks/evidence-gate.md`
- Keep these as decision inputs, not automatic authority. The Skill owns the final evidence-bound synthesis.


## Neural connections

- Owning Skill: `conversion-strategy`
- Decision boundary: `conversion intervention`
- Neural graph: `../../neural/graph.json`
- Neural router: `../../scripts/neural_router.py`
- Theory and specialist selection happens only after Skill ownership; neural nodes never replace Skill routing.
- Use the local `references/skill-spec.json` evidence policy and invariants to reject neural recommendations that are unsupported by the request evidence.

## Completion gate

Complete only when the decision is explicit, evidence and inference are separated, a credible alternative was considered, outputs are rendered, material uncertainty is stated, and measurement plus reversal evidence are defined.

Local behavioral evaluations live in `evals/activation.yml`, `evals/behavior.yml`, `evals/pressure.yml`, and `evals/regression.yml`.