AGENT SKILL

conversion-map

Plan evaluation, trial, pricing decision, objections, buyer roles, and conversion triggers

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
conversion-map
type
analysis
version
v0.5
description
Plan evaluation, trial, pricing decision, objections, buyer roles, and conversion triggers
visual_tier
visual
argument-hint
[optional: app, segment, or conversion motion]
context_intake
deep
required_conventions
[ "alignment-page" ]

02 资源文件 2

03 SKILL.md 正文

Pack Availability Guard

Before telling the user to run a skill from another project-local pack, check .agents/project.json.enabled_packs. If the target pack is not enabled, recommend npx skillpacks install <pack> from the project shell, instead of the target skill.

Conversion Map

Invoke as $conversion-map.

Map how evaluators become customers, including the decision path from first value to commitment.

Process

0. Product-Path Scope Resolution

Resolve research scope by product path before using code or app structure as a hint:

  1. If $ARGUMENTS names a non-archived research/{slug}/ directory or a product-path ID whose scope_path points there, use that path. Treat {slug} as the product/app name, not the ICP, audience, or segment label.
  2. If $ARGUMENTS names only research/_archive/{slug}/ or a manifest entry with status: archived or legacy status: abandoned, stop and warn that the path is archived; do not write or update scoped outputs there.
  3. Read research/.progress.yaml when present. Normalize legacy active_path to active_paths on read and write back active_paths on manifest updates. Treat legacy abandoned as archived; exclude archived, abandoned, deferred, revisit_candidate, promoted, and any scope_path under research/_archive/ from active target selection.
  4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.
  5. If no active manifest target exists, list non-archived product directories under research/, excluding research/_archive/ and dot directories. Auto-select only when exactly one exists; ask when multiple exist.
  6. If no product directories exist, use flat research/ single-product mode.
  7. Detect monorepo/app/package structure only as a secondary hint. Suggest creating a missing research/{slug}/ product path when code clearly exposes an app, but do not require code or monorepo detection before using research/{slug}/.

When product path {slug} is active, read and write research under research/{slug}/, specs under specs/{slug}/, and treat top-level research/*.md files as flat-mode documents or cross-path summaries.

  1. Resolve product-path scope using research/{slug}/ when applicable.
  2. Read research/.progress.yaml when present. Normalize active_path (singular legacy) to active_paths (plural list) when reading; treat legacy abandoned as archived and exclude archived/deferred/revisit/promoted paths plus research/_archive/ scopes from active target selection. Scope the conversion map to the active product path by default.
  3. Require research/journey-map.md; if missing, recommend $journey-map.
  4. Load ICP, journey map, onboarding map, competitive analysis, monetization/GTM docs, specs, and feedback when present.
  5. Interview and recommend around: evaluation mode, trial/freemium/demo motion, buyer and user roles, proof required, conversion trigger, objections, pricing/packaging concerns, sales assist, procurement, timeline, and lost-deal reasons.
  6. Present the conversion model and unresolved assumptions before writing.
  7. Write research/conversion-map.md and research/conversion-map-interview.md in flat mode, or research/{slug}/conversion-map.md and research/{slug}/conversion-map-interview.md when product-path scope is active, after validation.

Output Shape

# Conversion Map

> Based on: research/journey-map.md
> Date: YYYY-MM-DD

## Summary
## Evaluation Path
## Buyer And Decision Roles
## Conversion Trigger
## Objections And Proof
## Pricing And Packaging Implications
## Drop-Offs And Recovery
## Product Gaps
## Next Steps

Alignment Page

Follow the shared alignment-page convention via the packaged convention resolver; output path is alignment/conversion-map-{topic}.html.

Constraints

  • Keep conversion separate from payment mechanics; use $transaction-map for checkout, payments, fulfillment, refunds, and receipts.
  • End with ## Next Steps, preferring $transaction-map, $monetization, $gtm, $experiment as context dictates.

Default Shipping Contract

Follow the shared shipping contract convention in CLAUDE.md.

04 同仓库更多 Skills