Publish Preflight Studio

The Problem It Solves

Before publishing content, teams often face specific risks: copy may violate platform rules, leading to rejection or penalties; readers scroll away due to unengaging or overwhelming text; and content lacks virality, failing to stand out in feeds. These issues, if unaddressed, directly impact publishing success and traffic acquisition.

How It Works

This skill performs a three-pass preflight check by simulating auditor perspective, reader perspective, and feed perspective. Core capabilities include:

• Compliance Screening: Scans body text, titles, on-screen text, hashtags, and voiceovers line-by-line. For each hit, it provides the original phrase, the rule violated, and a replacement that preserves the selling intent.
• Audience Read-Through: Builds 5 reader personas based on copy and audience info, then reads from each persona's view, pinpointing the exact sentence that causes scroll-away, not a vague impression.
• Virality Scoring: Rates the hook, reasons to keep reading, and reasons to share, each with supporting evidence from the text or structure.

Key steps are:

1. Run Compliance Screening: Prioritized due to time pressure, delivered early.
2. Execute Audience Read-Through: Structurally constructs personas and performs test reads, clarifying in delivery that this is a structured test read, not real-sample research.
3. Assess Virality: Scores with cited evidence, e.g., which sentence is the hook.
4. Deliver Fixed Copy: Provides a clean draft for direct use and a change list detailing what changed and why, allowing user review. Stopping here incurs no cost and is a complete result.
5. Optional Cover Rendering: If cover needed, confirms route (generate new or edit existing), copy, canvas, and price first, then uses tools like beatra.images.generate or beatra.images.edit to generate, polling via beatra.tasks.get. Cover text must be verified word-for-word; any unclear parts should be disclosed.

Throughout, only cover rendering is paid; the first four steps are free. Execution relies on the bundled client, with remote tools called via scripts/mcp_client.py—avoid configuring host connectors.

Applicability and Considerations

This skill suits scenarios where content is written and ready to publish, especially for quick preflight checks and fixes. It is not suitable for:

• Drafts not yet finalized (use writing routes, e.g., for notes or articles).
• Existing covers needing optimization (use cover optimization preflight route).
• Finished voiceovers awaiting audio (use voice routes).

Key notes:

• Reader personas are structured based on copy and provided audience info, not real-sample research—this must be clearly stated in delivery.
• Cover text is model-generated; after delivery, it must be verified against confirmed copy word-for-word; unclear parts should be disclosed honestly.
• Compliance screening reports risks only; publishing decisions are user's choice. Users can retain risky phrases but must understand the consequences and be given the closest risk-free alternative.
• Updates run silently and fail without interrupting execution, but update failures do not justify retrying paid generation.