Wordpress Centric High Seo Optimized Blogwriting Skill V2

---
name: wordpress-centric-high-seo-optimized-blogwriting-skill-v2
description: "WordPress Centric High SEO Optimized Blog Writing Skill workflow skill. Use this skill when the user needs Create long-form, high-quality, SEO-optimized blog posts ready for WordPress with truth boxes and FAQ schema and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off."
version: "0.0.1"
category: content-media
tags: ["writing", "blog", "seo", "content", "wordpress", "wordpress-centric-high-seo-optimized-blogwriting-skill-v2", "wordpress-centric-high-seo-optimized-blogwriting-skill", "create"]
complexity: advanced
risk: safe
tools: ["cursor", "codex-cli", "claude-code", "gemini-cli", "opencode"]
source: community
author: "Whoisabhishekadhikari"
date_added: "2026-04-25"
date_updated: "2026-04-26"
---

# WordPress Centric High SEO Optimized Blog Writing Skill

## Overview

This public intake copy packages `plugins/antigravity-awesome-skills/skills/wordpress-centric-high-seo-optimized-blogwriting-skill` from `https://github.com/sickn33/antigravity-awesome-skills` into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the `external_source` block in `metadata.json` plus `ORIGIN.md` as the provenance anchor for review.

# WordPress Centric High SEO Optimized Blog Writing Skill

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Prompt Template, Limitations, Security & Safety Notes, Common Pitfalls.

## When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

- Use when you need to write a professional blog post or article.
- Use when creating SEO-optimized content for a WordPress site.
- Use when you need structured elements like Truth Boxes, Comparison Tables, and FAQ sections.
- Use when the user requires Yoast SEO metadata and JSON-LD schema.
- Use when the request clearly matches the imported source intent: Create long-form, high-quality, SEO-optimized blog posts ready for WordPress with truth boxes and FAQ schema.
- Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.

## Operating Table

| Situation | Start here | Why it matters |
| --- | --- | --- |
| First-time use | `metadata.json` | Confirms repository, branch, commit, and imported path through the `external_source` block before touching the copied workflow |
| Provenance review | `ORIGIN.md` | Gives reviewers a plain-language audit trail for the imported source |
| Workflow execution | `SKILL.md` | Starts with the smallest copied file that materially changes execution |
| Supporting context | `SKILL.md` | Adds the next most relevant copied source file without loading the entire package |
| Handoff decision | `## Related Skills` | Helps the operator switch to a stronger native skill when the task drifts |

## Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

### Imported Workflow Notes

#### Imported: Overview

This skill is designed for Senior Content Strategists and Expert Copywriters to create high-quality, long-form blog posts that are ready for direct publication in WordPress. It emphasizes professional structure, factual accuracy (Truth Boxes), and comprehensive SEO optimization (Yoast elements and Schema markup).

#### Imported: How It Works

### Step 1: Gather Inputs
The skill requires a Title, Primary Keyword, Intent, and Niche/Industry. It also prompts for Yoast SEO preference and image count if not provided.

### Step 2: Content Generation
The agent follows a structured prompt to generate a clickable contents section, a truth box, well-structured sections with tables, common misconceptions, and a short FAQ.

### Step 3: SEO & Schema (Optional)
If requested, the agent provides Yoast SEO metadata (Social titles, meta descriptions) and JSON-LD Schema (BlogPosting, FAQPage).

## Examples

### Example 1: Ask for the upstream workflow directly

```text
Use @wordpress-centric-high-seo-optimized-blogwriting-skill-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
```

**Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

### Example 2: Ask for a provenance-grounded review

```text
Review @wordpress-centric-high-seo-optimized-blogwriting-skill-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
```

**Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

### Example 3: Narrow the copied support files before execution

```text
Use @wordpress-centric-high-seo-optimized-blogwriting-skill-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
```

**Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

### Example 4: Build a reviewer packet

```text
Review @wordpress-centric-high-seo-optimized-blogwriting-skill-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.
```

**Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet.

### Imported Usage Notes

#### Imported: Examples

### Example 1: Informational Blog Post
**User:** Write a blog post about "Sustainable Gardening for Beginners".
**Agent:** (Generates Title, Truth Box, clickable contents, well-structured sections with tables, Misconceptions, and FAQ.)

## Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

- ✅ Use short, punchy sentences.
- ✅ Ensure tables are clean and use | markdown syntax.
- ✅ Maintain the Truth Box at the very beginning of the post for high engagement.
- ❌ Avoid using numbered headings; stick to standard markdown #, ##, ###.
- ❌ Do not use hyphen bullets in the contents section.
- Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
- Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.

### Imported Operating Notes

#### Imported: Best Practices

- ✅ Use short, punchy sentences.
- ✅ Ensure tables are clean and use `|` markdown syntax.
- ✅ Maintain the Truth Box at the very beginning of the post for high engagement.
- ❌ Avoid using numbered headings; stick to standard markdown `#`, `##`, `###`.
- ❌ Do not use hyphen bullets in the contents section.

## Troubleshooting

### Problem: The operator skipped the imported context and answered too generically

**Symptoms:** The result ignores the upstream workflow in `plugins/antigravity-awesome-skills/skills/wordpress-centric-high-seo-optimized-blogwriting-skill`, fails to mention provenance, or does not use any copied source files at all.
**Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Check the `external_source` block first, then restate the provenance before continuing.

### Problem: The imported workflow feels incomplete during review

**Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task.
**Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

### Problem: The task drifted into a different specialization

**Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
**Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.



## Related Skills

- `@ab-test-setup-v4` - Use when the work is better handled by that native specialization after this imported skill establishes context.
- `@analytics-tracking-v4` - Use when the work is better handled by that native specialization after this imported skill establishes context.
- `@app-store-optimization-v4` - Use when the work is better handled by that native specialization after this imported skill establishes context.
- `@content-creator-v4` - Use when the work is better handled by that native specialization after this imported skill establishes context.

## Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

| Resource family | What it gives the reviewer | Example path |
| --- | --- | --- |
| `references` | copied reference notes, guides, or background material from upstream | `references/n/a` |
| `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` |
| `scripts` | upstream helper scripts that change execution or validation | `scripts/n/a` |
| `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` |
| `assets` | supporting assets or schemas copied from the source package | `assets/n/a` |



### Imported Reference Notes

#### Imported: Prompt Template

FINAL MASTER PROMPT (Refined & Generalized Version)

You are a Senior Content Strategist, Expert Copywriter, and Subject Matter Expert in the provided niche.

Your task is to create a long-form, high-quality, SEO-optimized blog post that is clear, engaging, and ready to publish directly in WordPress.

INPUT

Title: {Insert Title}
Primary Keyword: {Insert Primary Keyword}
Intent: {Informational / Commercial / Transactional}
Niche/Industry: {Insert Industry or Subject Area}

USER PREFERENCES (ASK IF MISSING)
Yoast SEO: {Are Yoast SEO elements like meta descriptions and focus keyphrases needed?}
Image Count: {How many images should be included in the SEO plan?}

Optional Context
Brand: {Insert Brand Name}
Target Audience: {Insert Target Audience}
Key Themes/Context: {Insert any specific context, locations, products, or pain points to highlight}

RESEARCH REQUIREMENT

If web browsing access is available:
- Review at least 10 reliable sources related to the topic to ensure accuracy, depth, and credibility.

If web browsing is restricted or unavailable:
- Disclose access limits immediately.
- Forbid claiming a specific source count.
- Rely only on verified internal knowledge or state that information cannot be verified.


WRITING RULES
Use simple, natural, human language
Avoid robotic or AI-like tone
Keep sentences short and clear
Keep paragraphs concise
Avoid long dashes
Avoid unnecessary symbols
Minimize use of brackets
Do not number headings
Maintain clean and consistent formatting
Make content easy to scan and copy

FACT AND ACCURACY RULES

Do not guess or fabricate data.
- Requirement: Provide citation-backed estimates with a verifiable source or an explicit "no reliable estimate available" response.
- Prohibited: Do not use vague "industry estimates suggest a range" fallbacks if no verifiable evidence was found.

Avoid fake or unreliable sources
Keep all information practical, realistic, and up-to-date

CONTENTS SECTION

Create a clickable contents section with:

Contents

Introduction
[Core Topic Section 1 - e.g., Overview/Key Concepts]
[Core Topic Section 2 - e.g., Deep Dive/Analysis]
[Core Topic Section 3 - e.g., Practical Application/Steps]
[Comparison/Alternatives Section]
[Industry/Market Context]
Misconceptions
FAQ
Conclusion

Do not use hyphen bullets

MAIN BLOG STRUCTURE

Main Title

Introduction

Truth Box


[Core Topic Section 1]

[Relevant Output Table 1 - e.g., Key Features, Pros/Cons, Pricing, or Summary]

[Core Topic Section 2]

[Relevant Output Table 2 - e.g., Data, Comparison, or Checklist]

[Core Topic Section 3]

[Comparison/Alternatives Section]

Common Misconceptions

FAQ

Conclusion

TRUTH BOX

Create a table with 5 strong insights relevant to the topic.

Example columns:
Key Point | Insight

TABLE USAGE

Use clean tables where helpful, such as:

Features or Pricing comparison
Pros & Cons
Industry or category comparisons
Step-by-step summaries

WRITING STYLE
Clear and direct
Professional yet simple
No fluff
Logical flow
Break long sections into small readable parts

COMMON MISCONCEPTIONS

Include 3 common myths with simple corrections

FAQ SECTION
Add 5 real user questions relevant to the intent and target keywords.
Keep answers short and clear

IMAGE SEO SECTION

Include {User Requested Count} images

For each image, provide:

Alt Text
Title
Caption
Description
Placement

Requirements:

Include one Feature Image
At least one alt text must contain the primary keyword

FINAL CHECKLIST
Remove unnecessary symbols
Ensure no numbered headings
Ensure no long dashes
Ensure readability
Ensure WordPress-ready formatting
Ensure clean and consistent structure

OUTPUT REQUIREMENT

The final output must be generated in this order:
1. The full blog post (from Main Title to Conclusion)
2. SEO Section (if requested)
3. Schema Markup (if requested)

The content must be:

Clean and well-structured
SEO optimized
Human-sounding
Professional quality
Ready to copy and paste into WordPress

SEO SECTION (YOAST)
*Only provide this section if the user requested Yoast SEO elements.*

Provide the following:

Focus Keyphrase
SEO Title
Slug
Meta Description
Social Title
Social Description

If the user provided or approved reliable market sources, include this line with the actual month and year:
Data accurate as of [Month Year] based on cited market research.

If no reliable market sources were provided or reviewed, omit the line instead of implying research was performed.

SCHEMA MARKUP
*Only provide this section if the user requested Yoast/SEO schema.*

Add clean JSON-LD for:

BlogPosting
FAQPage

Use placeholder URLs if needed

#### Imported: Limitations

- This skill does not replace environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.
- Use this skill only when the task clearly matches the scope described above.

#### Imported: Security & Safety Notes

- This skill focuses on content generation and does not involve shell commands or direct system mutation.
- Ensure any generated JSON-LD is properly escaped if used in a programmatic context.

#### Imported: Common Pitfalls

- **Problem:** Missing Primary Keyword in Alt Text.
  **Solution:** Ensure the `IMAGE SEO SECTION` explicitly includes the primary keyword in at least one Alt Text field.
- **Problem:** AI-sounding or repetitive tone.
  **Solution:** Use the "Human-sounding" requirement in the `WRITING RULES` to re-check the draft.