mcpField
T
trial-conversion-sales-assist-review

trial-conversion-sales-assist-review

github.com/sylphxaiMarketing & growth138 installsUpdated today
Repository

About trial-conversion-sales-assist-review

A skill for product and growth teams that turns trial-conversion and sales-assist questions into plans with owners, decision rules, metrics, and recovery paths. It emphasizes fit- and intent-based routing rather than sending every trial to sales.

Key features

  1. 01Classifies trial and buyer states
  2. 02Defines PQL scoring and routing
  3. 03Plans messages and upgrade offers
  4. 04Sets experiment metrics and guardrails
  5. 05Produces plans, schemas, and checklists

Use cases

  1. 01Designing PQL qualification and handoff
  2. 02Planning trial nudges and upgrade offers
  3. 03Setting trial extension and suppression rules

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill trial-conversion-sales-assist-review

After installing, type/trial-conversion-sales-assist-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/trial-conversion-sales-assist-patterns.md

Details

From the project README

Trial Conversion Sales Assist Review

Use this skill to convert trial conversion, product-qualified lead, sales-assist, activation, upgrade prompt, and nurture questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify trial model, activation events, value milestones, user/account identity, firmographic fit, usage signals, buying intent, routing capacity, pricing page path, and current conversion friction.
  2. Read references/trial-conversion-sales-assist-patterns.md.
  3. Classify users as not activated, self-serve ready, PQL, sales-assist, enterprise intent, procurement-ready, nurture, extension-needed, or bad-fit.
  4. Define PQL scoring, routing rules, message triggers, upgrade offers, demo/CS handoff, trial extension policy, suppression, experiment metrics, and support path.
  5. Produce trial conversion plan, state machine, decision table, event schema, conversion checklist, and experiment/guardrail plan.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not route every trial to sales; protect sales capacity and user trust with fit and intent thresholds.
  • Do not use misleading scarcity, hidden cancellation, surprise billing, or aggressive outreach as conversion tactics.
  • Do not optimize conversion without tracking activation quality, retention, refunds, support load, and complaint signals.
  • Do not contact users in ways that violate consent, privacy, regional rules, or enterprise account ownership.

Output format

Trial conversion context:
Audience / source of truth / risk boundary:

Sales-assist conversion plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Signals, routing, nudges, and guardrails:
- <trigger> -> <policy, metric, edge case, support note>

Comments

Markdown supported