Marketing Deliverable Auto-Save & Repo Sync

What it does

Marketing Deliverable Auto-Save & Repo Sync is a Cursor skill: a SKILL.md playbook that AgenticKit installs at .cursor/skills/marketing-auto-save. Cursor's agent loads it when the task matches the skill description, instead of stuffing the same rules into every chat.

Standards for Cursor marketing agents to automatically persist generated landing copy, launch strategies, and email sequences into docs/marketing/.

Auto-saving copy and launch assets into docs/marketing/ markdown files. The file is domain knowledge, not a slash macro. You do not type it. The agent reads it when the job is marketing auto save.

Why it exists

Default Cursor has no memory of how your team ships positioning, copy, and launch assets. Founders paste the same conventions into chat, then watch the model drift on the next turn. This skill exists so those conventions live on disk and load only when relevant.

It ships in the Marketing Kit. It is wired to the Direct Response Copywriter (copywriter) and Product Launch Coordinator (launch-coordinator) agents. It is wired to /landing-page: High-Converting Landing Page Copy Architect, /launch: Product Launch Strategy & Multi-Channel Kit, and /email-sequence: Customer Onboarding & Drip Email Sequence. That graph is the point: the skill is the standard, the agent is the role, the command is the trigger.

When to use it

• Use Marketing Deliverable Auto-Save & Repo Sync when the work is specifically about auto-saving copy and launch assets into docs/marketing/ markdown files.
• Load it before a long session that will touch this surface more than once. A one-line edit does not need the full playbook.
• Use it when you are writing something a buyer will see: landing copy, launch posts, SEO pages, or positioning docs.

When not to use it

• Do not treat the skill as a replacement for a slash command. Skills teach. Commands run a pipeline.
• Do not paste the whole SKILL.md into chat. If Cursor is not loading it, fix the description or invoke the matching command.
• Do not use it to generate spam or spray the same launch post across every channel.

Example workflow

1. Install the Marketing Kit so .cursor/skills/marketing-auto-save lands in the repo.
2. Open a new Cursor agent chat pointed at the files this skill governs.
3. Ask the Direct Response Copywriter (copywriter) to read the skill, or run /landing-page: High-Converting Landing Page Copy Architect.
4. Review the first artifact against the practices below. If it violates one, stop and correct the file. Do not prompt 'just finish it'.
5. Commit the skill-guided files with the rest of the slice so the next session inherits the same standard.

Example usage

Example prompt: "Read .cursor/skills/marketing-auto-save and apply it to this change. Do not invent extra conventions."

Or trigger the pipeline: /landing-page: High-Converting Landing Page Copy Architect. That command is written to load this skill.

Check the output against: Automatically output generated copy into structured markdown files in docs/marketing/

Example output

• The skill itself does not write a single output file. It changes what the agent is allowed to produce in positioning, copy, and launch assets.
• When you run /landing-page: High-Converting Landing Page Copy Architect, expect repo files plus notes under docs/, not a chat-only answer.

Best practices

• Automatically output generated copy into structured markdown files in docs/marketing/
• Keep marketing deliverables under git version control alongside application code
• Organize marketing assets by category: /docs/marketing/launch, /docs/marketing/copy
• Reference previously generated positioning docs when running subsequent commands

Common mistakes

• Ignoring "Automatically output generated copy into structured markdown files in docs/marketing/" and hoping a later prompt will clean it up.
• Copying the skill into .cursor/rules as always-on. That burns context and fights Cursor's load-on-match design.
• Running two overlapping skills that contradict each other in the same turn.
• Publishing generated copy without a human pass. The skill is a playbook, not a publisher.