← PrePilot LiteCONTENT HISTORY

Update to PrePilot Lite

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user wants to write, rewrite, sharpen, or review marketing copy for landing pages, websites, ads, emails, product pages, sales pages, CTAs, scripts, or campaign assets.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 241
    }
  ],
  "name": "copywriting",
  "skill_md_contents": "---\nname: copywriting\ndescription: Use when the user wants to write, rewrite, sharpen, or review marketing copy for landing pages, websites, ads, emails, product pages, sales pages, CTAs, scripts, or campaign assets.\n---\n\n# Marketing Copywriting\n\n## Use it for\n\n- New copy\n- Rewrites\n- Message-to-copy translation\n- Headline and CTA work\n- Copy review before publishing\n\n## Operating rules\n\n- Use context already present in the conversation before asking for more input.\n- Separate known facts, reasonable assumptions, and unknowns. Do not present assumptions as evidence.\n- When the answer depends on current platform rules, market conditions, pricing, benchmarks, or competitors, verify them with current sources when tools are available.\n- Prefer concrete decisions, examples, and next actions over generic marketing advice.\n- Do not invent campaign performance, customer quotes, research findings, testimonials, rankings, or competitor claims.\n- Keep the requested market, language, funnel stage, audience awareness, budget, and channel constraints visible throughout the work.\n- Clarity beats cleverness when the two conflict.\n- Use customer language, concrete detail, and proof.\n- Write for the reader's awareness and next decision, not for the company's org chart.\n- Do not fabricate proof, urgency, scarcity, testimonials, or numbers.\n- Avoid generic AI phrasing, filler transitions, repetitive sentence shapes, and empty adjectives.\n- Choose the information and narrative structure from the material, reader, channel, and decision. Do not default to a generic problem-solution frame.\n\n## Workflow\n\n1. Identify the copy job, audience, awareness stage, source of traffic, offer, proof, objection, and desired action.\n2. Choose one primary message and supporting evidence.\n3. Draft the information hierarchy before polishing sentences.\n4. Write specific copy using the customer's language and the channel's constraints.\n5. Remove filler, claims without proof, duplicated ideas, and vague CTAs.\n6. Run the result through `marketing-quality` when it will be public or client-facing.\n\n## Output contract\n\n- Finished copy in the requested format\n- Optional alternatives only when they help a real decision\n- Notes on assumptions or missing proof when material\n\n## Quality gate\n\n- First screen or first lines make the value clear\n- Every strong claim has support or is softened\n- CTA describes a real next action\n- Copy sounds written for this audience, not a generic template\n\n## Human-writing pass\n\nFor public-facing prose, run a final editing pass that preserves the writer's point and voice while removing generic model patterns. Prefer the minimum effective edit. Check for portable filler that could be pasted into another company unchanged, vague authority claims, fake-insight setups, repeated sentence shapes, forced binary contrasts, stacked dramatic fragments, inflated significance, decorative formatting, unsupported specificity, and conclusions that only restate the piece. Keep useful rough edges when they belong to the writer.\n\n## Handoff\n\nIf the task is part of a larger marketing request, return the completed deliverable plus the evidence or decisions the next PrePilot skill needs. Do not repeat upstream analysis unless it changes the result.\n"
}

SHA-256 of public snapshot: 82f1838ac490714677bfeeb457f3c9fd29420a80b223b6c517364419ffa3eb98