Marketing Kit

Marketing Kit helps you turn a marketing objective into researched, planned, reviewable work. It is for marketers, founders, and growth, content, or product teams that want repeatable workflows for understanding an audience, shaping a message, creating assets, coordinating campaigns, and learning from results while keeping approval with a person.

You install one Kit for your chosen assistant, then invoke the Skill that matches the outcome you need. The Kit also supplies specialized Agents, runtime automation, rules, and supporting files used by those workflows.

Is this the right Kit?

Choose Marketing Kit when the main outcome is marketing planning or execution, such as:

• Researching an audience, market, or competitor set;
• Defining positioning, brand direction, an offer, or a persona;
• Planning and drafting content, campaigns, funnels, or launch assets;
• Reviewing conversion paths and proposing focused experiments;
• Measuring results, diagnosing performance, and prioritizing improvements.

Marketing Kit does not replace current evidence, your brand and data-handling policies, platform review, or human judgment. It does not make generated claims accurate by default or authorize spending, publishing, contacting an audience, or changing a live account. For a narrow task with an approved brief, you can start with the relevant creation workflow instead of running every research and planning step.

A typical human-controlled workflow

Use this sequence when the objective still needs evidence and direction before execution:

1. Run ak:marketing-research to collect and organize relevant audience, market, and customer evidence.
2. Run ak:brand to turn approved evidence into positioning and messaging boundaries.
3. Run ak:marketing-planning to define deliverables, sequence, owners, and measures for the selected objective.
4. Review the plan. A person decides whether the claims, scope, risks, and proposed external actions are acceptable.
5. Run ak:cook only after approval to produce the bounded deliverables.

Keep account changes, publishing, outreach, and budget decisions as separate, explicit approvals. Some workflows can use external services only when the required integration, credentials, and current API behavior are available. A provider-oriented Skill in the package is not a promise that every named service is currently supported.

Practical multi-Skill recipes

• Plan a product launch: use ak:marketing-research for attributable audience evidence, ak:brand for approved messaging boundaries, and ak:launch-strategy for stages, owners, gates, and measurement. After review, use ak:content-marketing or ak:write for bounded drafts only.
• Build a content program: use ak:content-marketing to define pillars, briefs, owners, and review stages, then give an approved brief to ak:write. Treat publishing, redirects, outreach, and account changes as separate authorized actions.
• Hand a launch requirement to Engineer Kit: use ak:marketing-planning to record the reviewed evidence, claims, deliverables, dependencies, and success measures. Before switching sessions, use ak:handoff to preserve source pointers and open state. Engineer ak:plan can then turn the accepted product requirement into a technical plan before ak:cook implements it.

The cross-Kit recipe requires both Kits to be installed where their Skills are invoked. A Marketing plan or handoff does not authorize implementation, publication, deployment, audience contact, or spend.

What is included

The resolved Marketing package includes its complete Marketing Skill set, shared Agents and support, and Marketing-specific content. You install Marketing Kit once; the shared foundation is package composition, not another public Kit or a second install.

These are resolved package counts. Files nested inside a Skill, such as its references, templates, scripts, or assets, belong to that Skill rather than becoming separate catalog entries. The exported manual notification utility is not event-wired or enabled by default.

Runtime availability

Availability is capability-specific. A successful install does not imply that every runtime can activate every packaged component in the same way. Read Runtime adapters before choosing a non-default target or assuming parity.

Install and try Marketing Kit

Complete Onboarding first so ak is configured, you are signed in to AgentKit, and ak licenses shows your Marketing Kit grant. From a project you control, install the project-native Claude Code target:

ak kit init marketing --target claude-code

Review the destination and installation summary, then start a fresh Claude Code session in that project.

For your first workflow, use a small set of customer notes that contains no secrets and aim for drafts rather than a live campaign:

/ak:marketing-research Summarize the supplied customer interviews into three audience problems. Cite the evidence and mark uncertainty

Review the findings and remove any unsupported claim. When the evidence is acceptable, create a bounded plan:

/ak:marketing-planning Plan a one-page launch brief using only the approved audience findings

Read the proposed deliverable, claims, and success measures. If you approve the plan, continue:

/ak:cook Create the approved launch brief as drafts only. Do not publish or contact anyone

The workflow is complete only after you inspect the drafts, verify each claim against its source, and accept the result. For other scopes, Claude plugin delivery, Codex, Cursor, or Skill selection, use Installing kits for the exact supported options.

Explore next

• Kits, Skills, Agents, and Hooks explains how the package components work together.
• Runtime adapters compares Claude Code, Codex, and Cursor delivery boundaries.
• Installing kits covers project and user scope, Claude native and plugin delivery, Skill selection, refresh, and uninstall.
• Projects, artifacts, and checkpoints explains ownership, human checkpoints, and recovery snapshots.
• Kit installation problems provides a safe diagnostic path when installation or discovery fails.
• CLI reference provides exact command and flag syntax.