6DuckLearn Skills

go to market

Use for product launches, PR angles, campaign calendars, and approval-gated marketing drafts across online channels for software or physical products.

marketing Tags: go-to-market, product-marketing, launch, campaign, community-draft, approval-gate, codex-workflow

Go-To-Market Agent

Use this skill when you need to turn a product, feature, or useful workflow into honest launch positioning, channel drafts, and an execution checklist.

This is a curated, model-agnostic skill template. It can be used with Codex or another LLM runtime that supports reusable instructions, but it does not publish, schedule, or send anything by itself.

Problem This Skill Solves

Many launch drafts mix product facts, guesses, audience pain, and unsupported claims in one answer. That makes the output hard to trust and risky to post.

This skill separates the campaign work into positioning, proof, channel fit, claim review, and approval-required next actions.

Inputs

  • Product, feature, or workflow
  • Target user and job-to-be-done
  • Launch stage: idea, beta, shipped, or iteration
  • Evidence: demo, docs, shipped behavior, internal run, customer quote, or hypothesis
  • Channels: blog, community, X, LinkedIn, email, PR, or landing page
  • Constraints: claims to avoid, tone, region, pricing, compliance, and approval owner

Step-by-Step Onboarding Guide

  1. Paste the product or feature summary.
  2. Name the target user and the workflow problem they already feel.
  3. Add the strongest evidence you have, even if it is only a demo or internal run.
  4. Choose one or two channels instead of asking for every channel at once.
  5. Ask Codex to run this skill and produce a draft GTM workflow.
  6. Review the claim ledger before any public posting.
  7. Approve, revise, or reject each public-facing asset manually.

Example Use Case

Target user: an indie builder who repeats launch and community copy every week.

Workflow:

  1. Give Codex a feature note, source links, and the target audience.
  2. Use this skill to create a campaign brief.
  3. Ask for one community post draft and one blog outline.
  4. Require a claim ledger for every sentence that mentions results, traffic, adoption, revenue, or customer proof.
  5. Keep public copy marked draft until a human approves it.

Expected artifact: a launch brief with positioning, audience pain, proof level, 1-3 approval-required drafts, do-not-post-if rules, and next actions.

Workflow

  1. Identify product type, audience, launch stage, channels, offer, and constraints.
  2. Write core positioning: audience, pain, promise, proof, and why now.
  3. Produce a campaign brief with launch narrative, channel plan, and success metrics.
  4. Draft channel posts in the voice and format that fit each platform.
  5. Add a short execution calendar and review checklist.
  6. Mark anything public or externally sent as approval-required before execution.

Output Contract

Return:

  • campaign brief
  • audience and pain point
  • positioning statement
  • proof and confidence level
  • channel plan
  • 1-3 draft assets, not a spam batch
  • claim ledger
  • approval status
  • next action checklist

Guardrails

  • Do not publish, schedule, or send externally without explicit approval.
  • Do not invent customer quotes, endorsements, awards, availability, pricing, usage, revenue, or adoption.
  • Do not claim guaranteed reach, growth, traffic, or revenue.
  • If product evidence is thin, frame the campaign as a test or hypothesis.
  • Keep private data, credentials, and unreleased customer details out of public copy.

Related skills

  • domain product research — Use for product, company, competitor, and moat research grounded in 6DuckLearn data, local memory, and explicit evidence lanes.
  • pkm synthesis — Use for turning saved notes, research, memory, and prior decisions into a clear synthesis with themes, contradictions, carry-forward insights, and next actions.
  • detailed canvas builder — Build a detailed, conversion-ready canvas spec from a rough idea. Use when the task is to turn a campaign, storefront, event, product, or community concept into a structured bilingual canvas with clear sections, states, CTA logic, and trust/policy blocks.
  • shopline storefront widget builder — Build interactive SHOPLINE Shop Builder widgets that improve conversion, drive upsells, and grow your customer base. Covers game mechanics (spin wheel, scratch card, lottery), urgency tools (countdown timer, shipping bar), and marketing widgets (email popup, coupon banner, referral). Always runs intention analysis before generating code.
  • product launch announcement — Create exciting product launch announcements that generate buzz and drive signups
  • interview script — Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.