Update to PrePilot Lite

{
  "description": "Use when the user wants blog strategy, topic selection, briefs, outlines, article writing, editing, fact-checking, content refreshes, internal linking, SEO alignment, GEO readiness, or repurposing.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 229
    }
  ],
  "name": "blog-engine",
  "skill_md_contents": "---\nname: blog-engine\ndescription: Use when the user wants blog strategy, topic selection, briefs, outlines, article writing, editing, fact-checking, content refreshes, internal linking, SEO alignment, GEO readiness, or repurposing.\n---\n\n# Blog Engine\n\n## Use it for\n\n- Blog planning\n- Article briefs and outlines\n- Writing or editing articles\n- Refreshing decayed content\n- Fact-check and citation-readiness review\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- Choose a reader problem and search or distribution job before choosing a title.\n- Use evidence for factual claims and distinguish original analysis from sourced facts.\n- Do not pad articles to hit word counts.\n- When optimizing for AI citation, improve evidence and extractability without degrading human usefulness.\n- Choose article structure from the evidence, reader question, and argument. Do not force every article into a generic problem-solution sequence.\n\n## Workflow\n\n1. Define audience, query or distribution context, article job, existing coverage, and evidence sources.\n2. Choose angle and scope that add something useful beyond a generic summary.\n3. Build a brief with intent, key questions, proof, examples, outline, internal links, and conversion role.\n4. Write or edit for clear reasoning, concrete examples, and scan-friendly structure.\n5. Run fact-check, SEO, and GEO/AEO checks as relevant.\n6. Plan refresh triggers and repurposing.\n\n## Output contract\n\n- Strategy, brief, outline, article, or audit as requested\n- Evidence and citation notes\n- Internal-link and distribution suggestions\n- Refresh or reuse plan when relevant\n\n## Quality gate\n\n- No unsupported factual claims\n- No redundant sections\n- The article gives the reader a usable answer\n- SEO and GEO choices do not distort the article\n\n## Human-writing pass\n\nBefore final delivery, preserve the author's real voice and factual detail while removing generic filler, vague attribution, manufactured profundity, repeated rhetorical structures, and explanatory clauses that add tone instead of evidence. Do not regularize every paragraph into the same shape. If a sentence could move unchanged to an unrelated article, replace it with subject-specific evidence or cut it.\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"
}