📦 deps(thirdparty): update snapshots
This commit is contained in:
ci[bot]
+226
-159
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: wordpress-centric-high-seo-optimized-blogwriting-skill
|
||||
description: "Create long-form, high-quality, SEO-optimized blog posts ready for WordPress with truth boxes and FAQ schema."
|
||||
description: "Generate clean, human-sounding, SEO-optimized WordPress blog posts with optional Yoast metadata, JSON-LD schema markup, and image SEO planning. Supports modular batch output."
|
||||
category: content
|
||||
risk: safe
|
||||
source: self
|
||||
@@ -9,266 +9,333 @@ date_added: "2026-04-12"
|
||||
author: Whoisabhishekadhikari
|
||||
tags: [writing, blog, seo, content, wordpress]
|
||||
tools: [claude, cursor, gemini]
|
||||
version: 1.0.3
|
||||
version: 1.1.0
|
||||
---
|
||||
|
||||
# WordPress Centric High SEO Optimized Blog Writing Skill
|
||||
# WordPress SEO Blog Writing Skill
|
||||
|
||||
## 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).
|
||||
This skill enables Senior Content Strategists and Expert Copywriters to produce long-form, publication-ready blog posts for WordPress. It enforces professional structure, factual rigor, and comprehensive SEO optimization — including Yoast metadata and JSON-LD schema markup.
|
||||
|
||||
---
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
- 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.
|
||||
- Writing a professional blog post or article for WordPress
|
||||
- Creating SEO-optimized content targeting a specific keyword and intent
|
||||
- Structuring content with Truth Boxes, Comparison Tables, and FAQ sections
|
||||
- Generating Yoast SEO metadata and JSON-LD schema markup
|
||||
|
||||
---
|
||||
|
||||
## Inputs Required
|
||||
|
||||
| Field | Required | Description |
|
||||
|---|---|---|
|
||||
| Title | Yes | The blog post headline |
|
||||
| Primary Keyword | Yes | The target SEO keyword |
|
||||
| Intent | Yes | Informational, Commercial, or Transactional |
|
||||
| Niche / Industry | Yes | The subject area or vertical |
|
||||
| Yoast SEO | Ask if missing | Whether to include Yoast metadata |
|
||||
| Image Count | Ask if missing | Number of images to plan SEO for |
|
||||
| Brand | Optional | Brand name for tone alignment |
|
||||
| Target Audience | Optional | Intended reader profile |
|
||||
| Key Themes / Context | Optional | Specific locations, products, or pain points |
|
||||
|
||||
---
|
||||
|
||||
## 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 1 — Gather Inputs
|
||||
Collect all required fields. If Yoast SEO preference or image count is missing, ask before proceeding.
|
||||
|
||||
### 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 2 — Generate Content
|
||||
Produce a structured, long-form blog post following the content rules and format below.
|
||||
|
||||
### Step 3: SEO & Schema (Optional)
|
||||
If requested, the agent provides Yoast SEO metadata (Social titles, meta descriptions) and JSON-LD Schema (BlogPosting, FAQPage).
|
||||
### Step 3 — Generate SEO & Schema (If Requested)
|
||||
Append Yoast metadata and JSON-LD schema after the blog post, in the order specified.
|
||||
|
||||
---
|
||||
|
||||
## Prompt Template
|
||||
|
||||
FINAL MASTER PROMPT (Refined & Generalized Version)
|
||||
```text
|
||||
You are a Senior Content Strategist, Expert Copywriter, and Subject Matter Expert
|
||||
in the provided niche.
|
||||
|
||||
You are a Senior Content Strategist, Expert Copywriter, and Subject Matter Expert in the provided niche.
|
||||
Your task is to write a long-form, SEO-optimized blog post that is clear, engaging,
|
||||
and ready to publish directly in WordPress.
|
||||
|
||||
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}
|
||||
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
|
||||
|
||||
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}
|
||||
Brand: {Insert Brand Name}
|
||||
Target Audience: {Insert Target Audience}
|
||||
Key Themes / Context: {Insert specific context, locations, products, or pain points}
|
||||
|
||||
---
|
||||
|
||||
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 available:
|
||||
- Review at least 10 reliable sources to ensure accuracy and depth.
|
||||
|
||||
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.
|
||||
If web browsing is unavailable:
|
||||
- Disclose the limitation immediately.
|
||||
- Do not claim a specific source count.
|
||||
- Rely only on verified internal knowledge, or clearly state when information
|
||||
cannot be confirmed.
|
||||
|
||||
---
|
||||
|
||||
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
|
||||
- Use simple, natural, human language.
|
||||
- Avoid robotic or AI-like tone.
|
||||
- Keep sentences short and paragraphs concise.
|
||||
- Do not use long dashes, unnecessary symbols, or brackets.
|
||||
- Do not number headings.
|
||||
- Maintain clean, consistent formatting throughout.
|
||||
- Prioritize readability and scannability.
|
||||
|
||||
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
|
||||
ACCURACY RULES
|
||||
|
||||
- Do not guess or fabricate data.
|
||||
- Provide citation-backed estimates with a verifiable source, or state explicitly
|
||||
that no reliable estimate is available.
|
||||
- Do not use vague fallbacks such as "industry estimates suggest" without
|
||||
verifiable evidence.
|
||||
- Avoid fake or unreliable sources.
|
||||
- Keep all information practical, realistic, and current.
|
||||
|
||||
---
|
||||
|
||||
CONTENTS SECTION
|
||||
|
||||
Create a clickable contents section with:
|
||||
Generate a clickable table of contents using this structure:
|
||||
|
||||
Contents
|
||||
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
|
||||
Introduction
|
||||
[Core Topic Section 1 — e.g., Overview or Key Concepts]
|
||||
[Core Topic Section 2 — e.g., Deep Dive or Analysis]
|
||||
[Core Topic Section 3 — e.g., Practical Application or Steps]
|
||||
[Comparison or Alternatives Section]
|
||||
[Industry or Market Context]
|
||||
Common Misconceptions
|
||||
FAQ
|
||||
Conclusion
|
||||
|
||||
Do not use hyphen bullets
|
||||
Do not use hyphen bullets in the final output.
|
||||
|
||||
---
|
||||
|
||||
MAIN BLOG STRUCTURE
|
||||
|
||||
Main Title
|
||||
Main Title
|
||||
|
||||
Introduction
|
||||
Introduction
|
||||
|
||||
Truth Box
|
||||
Truth Box
|
||||
|
||||
[Core Topic Section 1]
|
||||
[Relevant Table 1 — e.g., Key Features, Pros/Cons, Pricing, or Summary]
|
||||
|
||||
[Core Topic Section 1]
|
||||
[Core Topic Section 2]
|
||||
[Relevant Table 2 — e.g., Data, Comparison, or Checklist]
|
||||
|
||||
[Relevant Output Table 1 - e.g., Key Features, Pros/Cons, Pricing, or Summary]
|
||||
[Core Topic Section 3]
|
||||
|
||||
[Core Topic Section 2]
|
||||
[Comparison / Alternatives Section]
|
||||
|
||||
[Relevant Output Table 2 - e.g., Data, Comparison, or Checklist]
|
||||
Common Misconceptions
|
||||
|
||||
[Core Topic Section 3]
|
||||
FAQ
|
||||
|
||||
[Comparison/Alternatives Section]
|
||||
Conclusion
|
||||
|
||||
Common Misconceptions
|
||||
|
||||
FAQ
|
||||
|
||||
Conclusion
|
||||
---
|
||||
|
||||
TRUTH BOX
|
||||
|
||||
Create a table with 5 strong insights relevant to the topic.
|
||||
A table with 5 strong, topic-relevant insights.
|
||||
|
||||
Example columns:
|
||||
Key Point | Insight
|
||||
Columns: Key Point | Insight
|
||||
|
||||
TABLE USAGE
|
||||
---
|
||||
|
||||
Use clean tables where helpful, such as:
|
||||
TABLES
|
||||
|
||||
Features or Pricing comparison
|
||||
Pros & Cons
|
||||
Industry or category comparisons
|
||||
Step-by-step summaries
|
||||
Use clean markdown tables where they add clarity, such as:
|
||||
- Feature or pricing comparisons
|
||||
- Pros and cons
|
||||
- Industry or category breakdowns
|
||||
- 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
|
||||
Include 3 common myths about the topic with clear, simple corrections.
|
||||
|
||||
---
|
||||
|
||||
FAQ SECTION
|
||||
Add 5 real user questions relevant to the intent and target keywords.
|
||||
Keep answers short and clear
|
||||
|
||||
Include 5 real user questions relevant to the topic, intent, and target keywords.
|
||||
Keep answers short and direct.
|
||||
|
||||
---
|
||||
|
||||
IMAGE SEO SECTION
|
||||
|
||||
Include {User Requested Count} images
|
||||
Plan SEO for {User Requested Count} images.
|
||||
|
||||
For each image, provide:
|
||||
- Alt Text (at least one must include the primary keyword)
|
||||
- Title
|
||||
- Caption
|
||||
- Description
|
||||
- Placement in the post
|
||||
|
||||
Alt Text
|
||||
Title
|
||||
Caption
|
||||
Description
|
||||
Placement
|
||||
Always include one Featured Image.
|
||||
|
||||
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
|
||||
Before delivering the output, confirm:
|
||||
- No unnecessary symbols
|
||||
- No numbered headings
|
||||
- No long dashes
|
||||
- Content is readable and well-paced
|
||||
- Formatting is WordPress-ready and consistent
|
||||
```
|
||||
|
||||
The final output must be generated in this order:
|
||||
1. The full blog post (from Main Title to Conclusion)
|
||||
---
|
||||
|
||||
## Output Order
|
||||
|
||||
In default (non-batch) mode, deliver output in this sequence:
|
||||
|
||||
1. Full blog post (Main Title through Conclusion)
|
||||
2. SEO Section (if requested)
|
||||
3. Schema Markup (if requested)
|
||||
|
||||
The content must be:
|
||||
When a batch mode is selected, return only the requested component(s).
|
||||
|
||||
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.*
|
||||
## Batch Output Options
|
||||
|
||||
Provide the following:
|
||||
Use batch mode when the user requests individual components separately.
|
||||
|
||||
Focus Keyphrase
|
||||
SEO Title
|
||||
Slug
|
||||
Meta Description
|
||||
Social Title
|
||||
Social Description
|
||||
### Batch 1 — Blog Post Only
|
||||
Full blog post from title to conclusion. No SEO metadata, schema, or image SEO.
|
||||
|
||||
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.
|
||||
### Batch 2 — SEO Metadata
|
||||
Yoast SEO elements only:
|
||||
- Focus keyphrase
|
||||
- SEO title
|
||||
- Slug
|
||||
- Meta description
|
||||
- Social title
|
||||
- Social description
|
||||
- Suggested internal links
|
||||
- Suggested external link types
|
||||
|
||||
If no reliable market sources were provided or reviewed, omit the line instead of implying research was performed.
|
||||
### Batch 3 — Image SEO
|
||||
Image SEO assets only:
|
||||
- Featured image concept
|
||||
- Supporting image concepts
|
||||
- Alt text, title, caption, description, and placement for each
|
||||
|
||||
SCHEMA MARKUP
|
||||
*Only provide this section if the user requested Yoast/SEO schema.*
|
||||
### Batch 4 — Schema Markup
|
||||
JSON-LD schema only:
|
||||
- `BlogPosting` schema
|
||||
- `FAQPage` schema
|
||||
|
||||
Add clean JSON-LD for:
|
||||
---
|
||||
|
||||
BlogPosting
|
||||
FAQPage
|
||||
## SEO Section (Yoast)
|
||||
|
||||
Use placeholder URLs if needed
|
||||
*Generate only if the user requested Yoast SEO elements.*
|
||||
|
||||
## Examples
|
||||
Provide:
|
||||
- Focus Keyphrase
|
||||
- SEO Title
|
||||
- Slug
|
||||
- Meta Description
|
||||
- Social Title
|
||||
- Social Description
|
||||
|
||||
### 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.)
|
||||
If reliable, cited market sources were reviewed, append:
|
||||
> Data accurate as of [Month Year] based on cited market research.
|
||||
|
||||
If no reliable sources were reviewed, omit this line entirely.
|
||||
|
||||
---
|
||||
|
||||
## Schema Markup
|
||||
|
||||
*Generate only if the user requested schema markup.*
|
||||
|
||||
Provide clean JSON-LD for:
|
||||
- `BlogPosting`
|
||||
- `FAQPage`
|
||||
|
||||
Use placeholder URLs where actual URLs are unavailable.
|
||||
|
||||
---
|
||||
|
||||
## 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.
|
||||
- Write short, direct sentences.
|
||||
- Use `|` markdown syntax for clean, readable tables.
|
||||
- Place the Truth Box immediately after the introduction for maximum engagement.
|
||||
- Use `#`, `##`, and `###` for headings — never number them.
|
||||
- Avoid hyphen bullets in the contents section.
|
||||
|
||||
---
|
||||
|
||||
## 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.
|
||||
- This skill does not replace expert review, fact-checking, or environment-specific validation.
|
||||
- Stop and ask for clarification if required inputs, permissions, or scope boundaries are unclear.
|
||||
- Use this skill only for tasks that match the scope described above.
|
||||
|
||||
## 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.
|
||||
## Security and Safety Notes
|
||||
|
||||
- This skill is limited to content generation. It does not execute shell commands or mutate system state.
|
||||
- Ensure any generated JSON-LD is properly escaped before use in a programmatic context.
|
||||
|
||||
---
|
||||
|
||||
## 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.
|
||||
**Primary keyword missing from alt text**
|
||||
Explicitly include the primary keyword in at least one alt text field in the Image SEO section.
|
||||
|
||||
**AI-sounding or repetitive tone**
|
||||
Revisit the Writing Rules. Shorten sentences, vary structure, and remove filler phrases.
|
||||
|
||||
---
|
||||
|
||||
## Related Skills
|
||||
|
||||
- `@seo-plan` - Use for high-level SEO strategy before writing.
|
||||
- `@seo-content` - For broader SEO content optimization across different platforms.
|
||||
- `@copywriting` - General professional writing and marketing copy.
|
||||
- `@seo-plan` — High-level SEO strategy before writing
|
||||
- `@seo-content` — Broader SEO content optimization across platforms
|
||||
- `@copywriting` — General professional writing and marketing copy
|
||||
Reference in New Issue
Block a user