Wordpress Centric High SEO Optimized Blogwriting Skill V2

wordpress-centric-high-seo-optimized-blogwriting-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-blogwriting-skill 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} 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 SEO SECTION (PLACE AT THE TOP) Provide the following: Focus Keyphrase SEO Title Slug Meta Description Social Title Social Description Include this exact line: Data accurate as of [Current Month & Year] based on market research SCHEMA MARKUP Add clean JSON-LD for: BlogPosting FAQPage Use placeholder URLs if needed 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 Truth Box Introduction [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 3 to 5 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: Clean and well-structured SEO optimized Human-sounding Professional quality Ready to copy and paste into WordPress

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Limitations.

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 the request clearly matches the imported source intent: the user asks to write a blog post, article, or SEO content. This applies a professional structure, truth boxes, click-bait-free accurate information, and outputs direct WordPress-ready content.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

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: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Examples

Example 1: Ask for the upstream workflow directly

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

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

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

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.

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.

• 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.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

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

• @wiki-page-writer-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @wiki-qa-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @wiki-researcher-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @wiki-vitepress-v2 - 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.