claude-plugin-wordpress-manager 2.9.1 → 2.12.0

package/skills/wp-content-generation/references/outline-patterns.md

@@ -0,0 +1,188 @@
+# Outline Patterns
+
+## Pattern 1: Standard Article
+
+For blog posts, opinion pieces, and informational content.
+
+```
+# [Title with Primary Keyword]
+
+## Introduction (~150 words)
+- Hook: surprising fact, question, or relatable scenario
+- Context: why this matters to the reader
+- Promise: what the reader will learn
+
+## [H2 Section 1: Main Topic] (~200-300 words)
+- Key point with supporting evidence
+- Example or data point
+- [Secondary keyword naturally placed]
+
+## [H2 Section 2: Subtopic] (~200-300 words)
+- Key point
+- Comparison or contrast
+- Practical application
+
+## [H2 Section 3: Subtopic] (~200-300 words)
+- Key point
+- Real-world example
+- Expert quote or data
+
+## [H2 Section 4: Practical Application] (~200-300 words)
+- How to apply the knowledge
+- Common mistakes to avoid
+- Tips for success
+
+## Conclusion (~150 words)
+- Summary of key takeaways
+- Final thought or call to action
+- Internal link to related content
+
+---
+Target: 1,200-1,500 words | 4-5 H2 sections | 2-3 internal links
+```
+
+## Pattern 2: Tutorial / How-To
+
+For step-by-step instructional content.
+
+```
+# How to [Achieve Outcome] — [Primary Keyword]
+
+## Introduction (~100 words)
+- What the reader will accomplish
+- Prerequisites (what they need before starting)
+- Estimated time
+
+## What You'll Need (~100 words)
+- Tools, accounts, or materials
+- Links to prerequisite resources
+
+## Step 1: [First Action] (~200 words)
+- Clear instruction
+- Screenshot or code snippet
+- Expected result
+
+## Step 2: [Second Action] (~200 words)
+- Clear instruction
+- Common pitfall to avoid
+- Expected result
+
+## Step 3: [Third Action] (~200 words)
+- Clear instruction
+- Pro tip or variation
+- Expected result
+
+## Step 4: [Verification] (~150 words)
+- How to confirm it worked
+- What success looks like
+
+## Troubleshooting (~200 words)
+### [Common Issue 1]
+- Symptom → Cause → Fix
+### [Common Issue 2]
+- Symptom → Cause → Fix
+
+## Next Steps (~100 words)
+- What to do after completing this tutorial
+- Link to advanced guide
+- CTA
+
+---
+Target: 1,500-2,000 words | 4-6 steps | Schema: HowTo
+```
+
+## Pattern 3: Listicle
+
+For "N best/top/ways" ranked or curated lists.
+
+```
+# [N] [Best/Top/Essential] [Subject] for [Audience/Purpose]
+
+## Introduction (~150 words)
+- Why this list matters
+- Selection criteria (how items were chosen)
+- Quick summary of top pick
+
+## 1. [Item Name] — [Key Differentiator] (~150-200 words)
+- What it is / why it's included
+- Key benefit or feature
+- Best for: [specific use case]
+- [Link or CTA]
+
+## 2. [Item Name] — [Key Differentiator] (~150-200 words)
+- [Same structure]
+
+## 3. [Item Name] — [Key Differentiator] (~150-200 words)
+- [Same structure]
+
+...
+
+## N. [Item Name] — [Key Differentiator] (~150-200 words)
+- [Same structure]
+
+## Comparison Table (~100 words)
+| Item | Key Feature | Best For | Price |
+|------|-------------|----------|-------|
+
+## How to Choose (~150 words)
+- Decision criteria
+- Recommendation based on use case
+
+## Conclusion (~100 words)
+- Top pick recap
+- CTA
+
+---
+Target: 1,000-1,800 words (depends on N) | N+3 H2 sections
+```
+
+## Pattern 4: FAQ / Q&A
+
+For frequently asked questions and knowledge base content.
+
+```
+# [Subject] FAQ: [N] Common Questions Answered
+
+## Introduction (~100 words)
+- What this FAQ covers
+- Who it's for
+
+### What is [subject]? (~100 words)
+- Clear, concise definition
+- Key characteristics
+
+### How does [subject] work? (~100 words)
+- Simple explanation
+- Core mechanism
+
+### How much does [subject] cost? (~100 words)
+- Pricing information
+- Value proposition
+
+### Is [subject] right for [audience]? (~100 words)
+- Ideal use cases
+- When to choose alternatives
+
+### How do I get started? (~100 words)
+- First steps
+- Link to getting started guide
+
+### [Additional question] (~100 words)
+- Answer
+
+## Still Have Questions? (~50 words)
+- Contact info or support link
+- CTA
+
+---
+Target: 800-1,200 words | 5-8 questions | Schema: FAQPage
+```
+
+## Outline Best Practices
+
+1. **Keyword placement:** Primary keyword in H1, secondary in 1-2 H2s
+2. **Section balance:** Each H2 section should be 150-300 words (not too short, not too long)
+3. **Internal links:** Plan 2-3 links during outline phase, not after
+4. **Schema alignment:** Choose the outline pattern that matches the target schema type
+5. **Reader flow:** Each section should lead naturally to the next
+6. **Standalone value:** Each H2 section should make sense if read in isolation (for featured snippets)

package/skills/wp-content-generation/scripts/content_gen_inspect.mjs

@@ -0,0 +1,90 @@
+#!/usr/bin/env node
+/**
+ * content_gen_inspect.mjs — Detects prerequisites for AI content generation.
+ *
+ * Usage:
+ *   node skills/wp-content-generation/scripts/content_gen_inspect.mjs [--cwd=/path/to/project]
+ *
+ * Checks:
+ *   1. WP REST API access (WP_SITES_CONFIG) — required for publishing
+ *   2. GSC access — optional, enhances keyword research step
+ *   3. Existing content volume — for internal linking suggestions
+ *   4. Schema tools availability — for structured data step
+ */
+
+import { readFileSync, existsSync } from 'fs';
+import { resolve } from 'path';
+
+const args = process.argv.slice(2);
+const cwdFlag = args.find(a => a.startsWith('--cwd='));
+const cwd = cwdFlag ? resolve(cwdFlag.split('=')[1]) : process.cwd();
+
+const result = {
+  content_generation: {
+    ready: false,
+    capabilities: {
+      wp_rest_api: false,
+      gsc_keywords: false,
+      structured_data: false,
+    },
+    details: {},
+  },
+};
+
+// Check WP REST API access
+const sitesConfig = process.env.WP_SITES_CONFIG;
+if (sitesConfig) {
+  try {
+    const config = JSON.parse(sitesConfig);
+    const sites = Array.isArray(config) ? config : [config];
+    if (sites.length > 0) {
+      result.content_generation.capabilities.wp_rest_api = true;
+      result.content_generation.details.sites_count = sites.length;
+      result.content_generation.ready = true;
+
+      // Check for GSC credentials
+      const hasGsc = sites.some(s => s.gsc_credentials || s.gsc_service_account);
+      result.content_generation.capabilities.gsc_keywords = hasGsc;
+
+      // Structured data is available if REST API is available (sd_* tools use REST)
+      result.content_generation.capabilities.structured_data = true;
+    }
+  } catch {
+    result.content_generation.details.config_error = 'Invalid WP_SITES_CONFIG JSON';
+  }
+}
+
+// Pipeline steps availability
+result.content_generation.pipeline = {
+  '1_brief': { available: true, note: 'Always available (Claude-native)' },
+  '2_keyword_research': {
+    available: result.content_generation.capabilities.gsc_keywords,
+    note: result.content_generation.capabilities.gsc_keywords
+      ? 'GSC available — real keyword data for research'
+      : 'GSC not configured — will use semantic keyword suggestions',
+  },
+  '3_outline': { available: true, note: 'Always available (Claude-native)' },
+  '4_draft': { available: true, note: 'Always available (Claude-native)' },
+  '5_seo_optimize': { available: true, note: 'Always available (Claude-native + wp-content-optimization)' },
+  '6_structured_data': {
+    available: result.content_generation.capabilities.structured_data,
+    note: result.content_generation.capabilities.structured_data
+      ? 'sd_* tools available via REST API'
+      : 'Requires WP REST API access',
+  },
+  '7_publish': {
+    available: result.content_generation.capabilities.wp_rest_api,
+    note: result.content_generation.capabilities.wp_rest_api
+      ? 'create_content available via REST API'
+      : 'Requires WP REST API access — can generate draft locally',
+  },
+};
+
+// Summary
+if (!result.content_generation.ready) {
+  result.content_generation.details.note = 'WP REST API not configured. Can still generate content (Steps 1-5) but cannot publish or inject schema.';
+} else {
+  result.content_generation.details.note = 'Full pipeline available. All 7 steps can execute.';
+}
+
+console.log(JSON.stringify(result, null, 2));

package/skills/wp-content-repurposing/SKILL.md

@@ -38,6 +38,7 @@ Content repurposing is the systematic transformation of canonical WordPress cont
    - "email" / "newsletter" / "digest" → Email newsletter (Section 2)
    - "atomize" / "break down" / "content calendar" → Content atomization (Section 3)
    - "character limits" / "platform specs" / "image sizes" → Platform specifications (Section 4)
+   - "auto-transform" / "automatic conversion" / "template pipeline" → Auto-Transform Pipeline (Section 5)
 
 2. **Run detection first:**
    ```bash
@@ -76,6 +77,14 @@ See `references/platform-specs.md`
 - Hashtag and link strategies
 - Posting frequency recommendations
 
+### Section 5: Auto-Transform Pipeline
+See `references/auto-transform-pipeline.md`
+- Automated blog post → multi-platform output
+- Template system for consistent formatting
+- Integration with LinkedIn (`li_create_post`), Twitter (`tw_create_tweet`, `tw_create_thread`), Buffer (`buf_create_update`), Mailchimp (`mc_set_campaign_content`)
+- Platform-specific formatting rules and character limits
+- See `references/transform-templates.md` for ready-to-use templates
+
 ## Reference Files
 
 | File | Content |
@@ -84,6 +93,8 @@ See `references/platform-specs.md`
 | `references/email-newsletter.md` | Newsletter digest, drip sequences, subject lines |
 | `references/content-atomization.md` | Atomization workflow, content calendar, repurposing matrix |
 | `references/platform-specs.md` | Character limits, image sizes, posting frequency |
+| `references/auto-transform-pipeline.md` | Pipeline architecture: fetch → extract → template → output |
+| `references/transform-templates.md` | Ready-to-use templates: blog→tweet, thread, LinkedIn, email |
 
 ## Recommended Agent
 
@@ -95,3 +106,5 @@ See `references/platform-specs.md`
 - **`wp-headless`** — headless content delivery for multi-channel architectures
 - **`wp-woocommerce`** — product content for e-commerce repurposing
 - **wp-social-email** — publish repurposed content to social and email channels
+- **`wp-linkedin`** — direct LinkedIn publishing for transformed content
+- **`wp-twitter`** — direct Twitter/X publishing for transformed content

package/skills/wp-content-repurposing/references/auto-transform-pipeline.md

@@ -0,0 +1,128 @@
+# Auto-Transform Pipeline
+
+## Overview
+
+The auto-transform pipeline converts WordPress content into platform-ready outputs with minimal manual intervention. It follows a 4-stage architecture: **Fetch → Extract → Template → Output**.
+
+Each stage is composable — you can run the full pipeline for hands-free distribution or stop at any stage for review and manual adjustments.
+
+## Pipeline Flow
+
+```
+┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐
+│  FETCH   │───▶│ EXTRACT  │───▶│ TEMPLATE │───▶│  OUTPUT  │
+│          │    │          │    │          │    │          │
+│ wp_get_  │    │ title    │    │ platform │    │ li_*     │
+│ post     │    │ excerpt  │    │ rules    │    │ tw_*     │
+│ wp_list_ │    │ headings │    │ char     │    │ buf_*    │
+│ posts    │    │ key pts  │    │ limits   │    │ mc_*     │
+│          │    │ image    │    │ tone     │    │ sg_*     │
+│          │    │ tags     │    │ hashtags │    │          │
+└──────────┘    └──────────┘    └──────────┘    └──────────┘
+```
+
+### Stage 1: Fetch
+
+Retrieve source content from WordPress using REST tools.
+
+| Tool | Use Case |
+|------|----------|
+| `wp_get_post` | Single post by ID |
+| `wp_list_posts` | Recent posts for batch processing |
+| `wp_get_page` | Static page content |
+| `wc_get_product` | WooCommerce product for e-commerce social |
+
+Extract from the response: `title.rendered`, `excerpt.rendered`, `content.rendered`, `featured_media`, `categories`, `tags`.
+
+### Stage 2: Extract
+
+Parse the raw content into atomic elements for templating.
+
+**Extraction rules:**
+- **Title**: Strip HTML entities, keep under 100 chars
+- **Excerpt**: First 2-3 sentences if no excerpt set, strip HTML
+- **Headings**: All H2/H3 from content (used for thread splitting)
+- **Key points**: Sentences containing numbers, statistics, or strong claims
+- **Featured image**: Resolve `featured_media` ID to URL via `wp_get_media`
+- **Tags**: Map to hashtags (lowercase, no spaces, `#` prefix)
+- **Categories**: Use for tone/audience targeting
+
+**Tag-to-hashtag conversion:**
+```
+"Zero Calorie" → #zerocalorie
+"Cactus Water" → #cactuswater
+"Health Tips"  → #healthtips
+```
+
+### Stage 3: Template
+
+Apply platform-specific formatting rules from `transform-templates.md`.
+
+**Template selection logic:**
+| Target Platform | Content Length | Template |
+|----------------|---------------|----------|
+| Twitter/X | Short (< 5 key points) | Single tweet |
+| Twitter/X | Long (≥ 5 key points or ≥ 3 H2s) | Thread |
+| LinkedIn | Any | Feed post (default) or Article (if > 2000 words) |
+| Buffer | Per-profile | Adapts to connected profiles |
+| Email | Any | Snippet with CTA |
+
+### Stage 4: Output
+
+Dispatch to distribution channels using MCP tools.
+
+| Channel | Tool | Requires Confirmation |
+|---------|------|-----------------------|
+| LinkedIn post | `li_create_post` | No |
+| LinkedIn article | `li_create_article` | Yes (safety hook) |
+| Twitter single | `tw_create_tweet` | No |
+| Twitter thread | `tw_create_thread` | No |
+| Buffer queue | `buf_create_update` | No |
+| Mailchimp campaign | `mc_create_campaign` + `mc_update_campaign_content` + `mc_send_campaign` | Yes (safety hook) |
+| SendGrid email | `sg_send_email` | Yes (safety hook) |
+
+## Configuration
+
+### Batch Processing
+
+For multi-post transforms (e.g., "repurpose the last 5 posts"):
+
+1. Fetch posts: `wp_list_posts` with `per_page=5`, `orderby=date`
+2. Loop: Extract → Template → Output per post
+3. For Buffer: space scheduling with `scheduled_at` (30-minute intervals)
+4. Report: Summary table with post title, channels, status
+
+### Tone Adaptation
+
+| Platform | Tone | Adjustments |
+|----------|------|-------------|
+| Twitter/X | Casual, punchy | Short sentences, emojis OK, hook first |
+| LinkedIn | Professional | Industry language, data-driven, insights |
+| Email | Friendly, direct | Personal tone, clear CTA, benefit-focused |
+| Buffer (multi) | Per-profile defaults | Adapts to connected platform |
+
+## Integration Points
+
+This pipeline integrates with the distribution tools added in v2.10.0:
+
+- **LinkedIn**: `li_create_post`, `li_create_article`, `li_get_analytics`
+- **Twitter/X**: `tw_create_tweet`, `tw_create_thread`, `tw_get_metrics`
+- **Buffer**: `buf_create_update`, `buf_get_analytics`
+- **Mailchimp**: `mc_create_campaign`, `mc_update_campaign_content`, `mc_send_campaign`
+- **SendGrid**: `sg_send_email`
+
+Always check service availability before pipeline execution:
+```
+hasLinkedIn() → li_* tools available
+hasTwitter()  → tw_* tools available
+hasBuffer()   → buf_* tools available
+hasMailchimp() → mc_* tools available
+hasSendGrid() → sg_* tools available
+```
+
+## Safety
+
+- **Never auto-send** emails or campaigns — always require user confirmation
+- **Preview before publish** — show formatted output before dispatching to any channel
+- **Rate limiting** — respect platform API rate limits (Twitter: 300 tweets/3h, LinkedIn: 100 posts/day)
+- **Duplicate detection** — check recent posts on platform before publishing identical content