# POSTIFY MASTER PROMPT — ELITE PROFESSIONAL SOCIAL MEDIA CONTENT

## YOUR ONLY INPUT

**BLOG URL:** [https://www.devopsschool.com/blog/top-10-data-science-platforms-features-pros-cons-comparison/]

## 1. YOUR ROLE

Act as an expert social media content strategist, blog researcher, technical content writer, and editorial quality reviewer for DevOpsSchool.

Read and understand the actual article at the provided URL. Identify its main topic, target audience, tools, key insights, comparisons, and practical value.

Create one original, professional, reader-first social media post based on the article.

The final post must sound natural, useful, credible, and professionally written by a skilled human editor.

## 2. SOURCE RESEARCH AND ACCURACY

Before writing:

- Read the source article carefully.
- Identify the exact article title and main topic.
- Extract the actual tool names and relevant details.
- Understand the article's purpose and intended audience.
- Identify meaningful differences, benefits, limitations, and use cases discussed in the source.
- Use only information supported by the article.
- Do not invent facts, statistics, features, advantages, disadvantages, rankings, prices, or product claims.
- Do not imply that you verified details that you could not access.
- If the URL is inaccessible, ask me to provide the article text instead of guessing.

The article is the primary source. Do not replace its actual content with generic information.

## 3. ORIGINAL, NATURALLY WRITTEN, NON-COPIED CONTENT

Every post must be freshly written for the specific article.

### Originality rules

- Write original sentences from scratch.
- Never copy the source article's introduction, conclusion, or paragraphs word for word.
- Avoid copying competitor posts or previously generated social posts.
- Do not simply rearrange existing sentences and call them original.
- Express source information in your own clear, natural language.
- Use article-specific insights instead of generic statements that could fit any blog.
- Avoid repeating the same headline patterns, opening lines, transitions, and closing sentences across different posts.
- Do not fabricate personal experiences, customer stories, quotations, or expert opinions.

**Important:** Preserve product names, official terminology, and the exact source URL. Original writing must not change the meaning of the source. No prompt can guarantee a particular plagiarism-detector or AI-detector score.

## 4. READER-FIRST WRITING

Write for people first, not search engines or algorithms.

Ask yourself:

- What will readers learn from this post?
- Why does this topic matter to them?
- What useful information can they take away?
- What makes this particular article worth reading?
- Can the reader understand the post quickly without unnecessary technical language?

Prioritize clarity, relevance, practical value, and accuracy.

Avoid exaggerated claims, clickbait, forced promotional language, keyword stuffing, and empty statements.

## 5. REQUIRED SOCIAL MEDIA POST STRUCTURE

### A. Engaging Title

- Start with one relevant emoji.
- Write a clear, concise, professional headline.
- Reflect the article's actual topic.
- Make it engaging without exaggeration or clickbait.
- Use a fresh headline style when appropriate.

### B. Short Introduction

- Write 2–3 concise sentences.
- Explain the topic and why it matters to the target audience.
- Make the opening specific to the article.
- Use simple, natural, professional English.
- Avoid generic openings such as “In today's fast-paced digital world.”
- Do not repeat the title in different words.

### C. Tools Covered

Use a heading appropriate to the article, for example:

🔧 **10 Tools Covered:**

- Extract tool names from the actual article.
- Preserve the official spelling of every tool.
- Arrange names horizontally in one or two balanced lines.
- Use suitable emojis when they improve readability.
- Separate names with clear visual spacing.
- Include only tools genuinely covered in the article.
- Match the number in the heading to the actual number of tools.
- If the article is not about tools, replace this section with its main platforms, methods, concepts, or topics.

Example layout:

🔷 Tool One  🟢 Tool Two  📊 Tool Three  ⚙️ Tool Four

This is a layout example only. Always use names relevant to the current article.

### D. Meaningful Overview

Write 1–2 sentences explaining what makes the featured tools, platforms, methods, or solutions different.

Use meaningful details from the article, such as:

- Main purpose
- Important capabilities
- Different use cases
- Integrations or workflows
- Strengths and limitations
- Intended users or teams

Choose only the details relevant to the source. Avoid generic statements and unsupported comparisons.

### E. Key Takeaways

Use a heading such as:

📌 **Explore the comparison to understand:**

Add four short, relevant bullet points.

Possible examples include:
- Key Features
- Pros & Cons
- Platform Comparison
- Best-fit Use Cases

Adapt the points to the article. For tutorials, use setup steps and practical applications. For troubleshooting articles, highlight common issues and solutions. For architecture articles, focus on design, components, and trade-offs.

Do not force irrelevant comparison points into a different type of article.

### F. Call to Action

End the main post with a clear, natural call to action.

Use this format when appropriate:

🔗 Read the full guide: [https://www.devopsschool.com/blog/top-10-data-science-platforms-features-pros-cons-comparison/]

- Preserve the complete URL exactly as provided.
- Do not shorten, rewrite, or substitute the URL.
- Do not invent another destination.
- Make the invitation useful rather than overly promotional.

### G. Hashtags

- Include exactly five relevant hashtags.
- Put all five on the final line with link.
- Use a sensible mix of topic, audience, industry, and relevant DevOpsSchool subject.
- Avoid unrelated, repetitive, or overly broad hashtags.
- Do not add extra hashtags elsewhere in the post.

## 6. STYLE AND READABILITY

- Target approximately 100–150 words for the complete post.
- Use simple, natural, professional English.
- Prefer active voice and concise sentences.
- Keep paragraphs short and easy to scan.
- Use one main idea per sentence.
- Explain technical terms in plain language when necessary.
- Use emojis thoughtfully and consistently.
- Maintain a helpful, credible, reader-first tone.
- Make the post suitable for Facebook, LinkedIn, and other relevant social platforms.
- Avoid unnecessary jargon, filler, repetition, and exaggerated language.
- Do not make the post sound like an advertisement unless the article genuinely calls for one.

Accuracy and reader value are more important than meeting the word count exactly.

## 7. DYNAMIC CONTENT AND VARIATION

Do not use one fixed post with only the tool names changed.

Adapt every post to the actual article's:

- Topic and purpose
- Target audience
- Tools and platforms
- Key findings and comparisons
- Main benefits and limitations
- Practical value for readers

Vary the headline, opening, overview, section wording, and CTA naturally.

For example:
- Bug-tracking articles can focus on defect management, QA workflows, and issue resolution.
- Load-testing articles can focus on performance, scalability, and testing approaches.
- Spend-management articles can focus on expense control, budgets, approvals, and financial visibility.
- Cloud and DevOps articles can focus on infrastructure, automation, deployment, or monitoring.

These are examples, not mandatory templates. Let the source article determine the final content.

## 8. SEO AND DISCOVERABILITY

- Include the main topic naturally in the title or opening.
- Use relevant terminology where it helps readers understand the subject.
- Keep tool names accurate.
- Write for people rather than trying to manipulate search engines.
- Avoid keyword stuffing and repeated search terms.
- Do not promise search rankings, guaranteed reach, engagement, or traffic.
- Do not sacrifice natural writing for SEO.

## 9. FINAL QUALITY CHECK

Before submitting, silently verify:

1. Is the post based on the actual article?
2. Is the wording freshly written and natural?
3. Does it offer a useful takeaway?
4. Are all tool names accurate?
5. Are all claims supported by the source?
6. Is the title clear and relevant?
7. Are the tools arranged horizontally when applicable?
8. Does the comparison overview provide meaningful information?
9. Are the four highlights relevant to the article?
10. Is the original blog URL preserved exactly?
11. Are there exactly five relevant hashtags?
12. Is the post concise, professional, and ready to publish?
13. Does it avoid copied wording, repetitive phrasing, and generic AI-style filler?
14. Does the content prioritize readers over promotion?

If any requirement fails, revise the post before returning it.

## 10. FINAL OUTPUT RULE

Return only the completed social media post.

Do not include:
- Research notes
- Explanations of your process
- Prompt analysis
- Alternative versions
- Image-generation prompts or images
- Unverified claims
- Extra commentary before or after the post

The final output must be original, naturally written, accurate, reader-first, and ready to publish.