| name | professional-blog-posting-engine |
| description | Produce publication-ready business blog and SEO article packages from a concrete brief, including strategy, outline, article, metadata, internal links, schema recommendation, image brief, promotion copy, and QA. Use for full professional articles; do not use for short posts, generic rewriting, or research without an article deliverable. |
Professional blog posting
Create useful, human-sounding articles that satisfy the reader’s intent. Do not manufacture experience, quotes, statistics, citations, clients, or authority.
Required brief
Confirm the topic, audience, business/brand, search intent, desired outcome, geographic scope when relevant, source material, voice, target site, and call to action. Research unstable claims and competitors before drafting.
Workflow
- Normalize the brief. State audience, intent, angle, evidence, conversion goal, constraints, and unanswered questions.
- Plan the article. Choose a defensible thesis, reader journey, headings, proof points, and internal-link opportunities.
- Draft. Lead with the reader’s problem or desired outcome. Give each section a distinct job. Use concrete language, varied sentence rhythm, useful examples, and natural keyword placement.
- Enrich. Add title/meta alternatives, internal-link recommendations, schema guidance, a featured-image brief, and channel-appropriate promotion copy only when requested by the output contract.
- Verify. Check factual claims, unsupported certainty, search-intent fit, repetition, awkward keyword use, links, tone, and call-to-action alignment.
Quality boundaries
- Prefer clarity and evidence over arbitrary word count.
- Do not pad sections or restate the introduction.
- Do not claim first-hand experience unless supplied by the user.
- Mark assumptions and facts that need owner confirmation.
- Cite current authoritative sources when accuracy depends on changing information.
- Keep SEO subordinate to usefulness and natural prose.
- Match regulated or legal/financial subjects with appropriate caution and source quality.
Output
Unless the user asks for article-only output, provide a compact strategy summary, SEO package, complete article, internal-link plan, schema recommendation, image brief, promotion assets, and QA notes. Omit empty sections rather than filling them with generic text.
Read details only when needed
- Read detailed-guide.md for templates, scoring, enrichment fields, and the full output contract.
- Read the applicable file under
examples/ only when the requested publishing workflow matches it.
The finished article should be ready for an editor to verify and publish, not a keyword-stuffed draft that still needs structural rescue.
