claude-plugin-wordpress-manager 2.3.1 → 2.6.0

package/skills/wp-search-console/references/indexing-management.md

@@ -0,0 +1,182 @@
+# Indexing Management
+
+## Overview
+
+Indexing management ensures that Google discovers, crawls, and indexes your WordPress pages correctly. The GSC MCP tools provide URL inspection for individual pages and sitemap management for bulk discovery. Together, these tools help you monitor crawl coverage, diagnose indexing issues, and control which pages appear in search results.
+
+## URL Inspection
+
+### Inspect a single URL
+
+```
+Tool: gsc_inspect_url
+Params:
+  site_url: "https://example.com/"
+  inspection_url: "https://example.com/blog/wordpress-seo-guide/"
+Returns:
+  indexStatusResult:
+    verdict: "PASS"                    # PASS | NEUTRAL | FAIL
+    coverageState: "Submitted and indexed"
+    robotsTxtState: "ALLOWED"
+    indexingState: "INDEXING_ALLOWED"
+    lastCrawlTime: "2026-02-25T10:30:00Z"
+    pageFetchState: "SUCCESSFUL"
+    crawledAs: "MOBILE"
+  mobileUsabilityResult:
+    verdict: "PASS"
+  richResultsResult:
+    detectedItems: [...]
+```
+
+### Understanding inspection results
+
+Key fields in the response:
+
+| Field | Values | Meaning |
+|-------|--------|---------|
+| `verdict` | PASS / NEUTRAL / FAIL | Overall indexing status |
+| `coverageState` | Various | Detailed coverage status |
+| `robotsTxtState` | ALLOWED / DISALLOWED | Whether robots.txt blocks the URL |
+| `indexingState` | INDEXING_ALLOWED / INDEXING_NOT_ALLOWED | Whether meta robots/noindex blocks indexing |
+| `pageFetchState` | SUCCESSFUL / SOFT_404 / NOT_FOUND / REDIRECT | Crawl outcome |
+| `crawledAs` | MOBILE / DESKTOP | Which crawler accessed the page |
+
+### Common coverage states
+
+- **Submitted and indexed** — page is in the index and appearing in search results
+- **Crawled - currently not indexed** — Google crawled it but chose not to index (quality or duplicate concern)
+- **Discovered - currently not indexed** — Google knows about it but has not crawled it yet
+- **Excluded by 'noindex' tag** — the page has a noindex directive
+- **Blocked by robots.txt** — robots.txt prevents crawling
+- **Page with redirect** — the URL redirects to another page
+- **Soft 404** — the page returns 200 but Google treats it as a 404
+
+## Sitemap Management
+
+### List sitemaps
+
+```
+Tool: gsc_list_sitemaps
+Params:
+  site_url: "https://example.com/"
+Returns: Array of sitemaps with:
+  path: "https://example.com/sitemap_index.xml"
+  lastSubmitted: "2026-02-20T08:00:00Z"
+  isPending: false
+  isSitemapsIndex: true
+  lastDownloaded: "2026-02-25T06:00:00Z"
+  warnings: 0
+  errors: 0
+  contents:
+    - type: "web"
+      submitted: 150
+      indexed: 142
+```
+
+### Submit a sitemap
+
+```
+Tool: gsc_submit_sitemap
+Params:
+  site_url: "https://example.com/"
+  sitemap_url: "https://example.com/sitemap_index.xml"
+```
+
+Submit after:
+- Initial site setup
+- Adding a new sitemap (e.g., a video sitemap or news sitemap)
+- Changing sitemap URL structure
+- Major content additions (100+ new pages)
+
+### Delete a sitemap
+
+```
+Tool: gsc_delete_sitemap
+Params:
+  site_url: "https://example.com/"
+  sitemap_url: "https://example.com/old-sitemap.xml"
+```
+
+Delete when:
+- A sitemap URL has changed (submit the new one, delete the old)
+- A sitemap contains only 404/removed pages
+- Consolidating multiple sitemaps into one
+
+## Monitoring Crawl Coverage
+
+### Bulk URL inspection workflow
+
+For auditing multiple pages, iterate through URLs from your WordPress site:
+
+1. **Get WordPress pages** using `wp_list_posts` with `status: "publish"`
+2. **Inspect each URL** using `gsc_inspect_url` for each published page
+3. **Categorize results** by `coverageState`:
+   - Indexed: `verdict === "PASS"`
+   - Not indexed: `verdict === "FAIL"` or `verdict === "NEUTRAL"`
+4. **Report findings** with counts per coverage state
+
+```
+# Example workflow
+Step 1: wp_list_posts status="publish" per_page=100 → Array of posts with links
+Step 2: For each post.link → gsc_inspect_url inspection_url=post.link
+Step 3: Group by coverageState → { indexed: 85, not_indexed: 12, errors: 3 }
+```
+
+### Sitemap vs index comparison
+
+Compare sitemap-submitted URLs against indexed URLs to find coverage gaps:
+
+1. **List sitemaps** with `gsc_list_sitemaps` to get submitted/indexed counts
+2. **Calculate coverage rate**: `indexed / submitted * 100`
+3. **Investigate gaps**: If coverage is below 90%, inspect non-indexed URLs individually
+
+## Handling Indexing Issues
+
+### Crawled but not indexed
+
+This means Google fetched the page but deemed it unworthy of indexing. Common causes:
+- **Thin content**: Page has very little unique content
+- **Duplicate content**: Substantially similar to another indexed page
+- **Low quality**: Content does not meet quality thresholds
+
+**Actions:**
+1. Inspect the URL with `gsc_inspect_url` to confirm the status
+2. Review the page content — add depth, unique value, or original research
+3. Check for duplicate content — use canonical tags to consolidate
+4. After improving, request re-indexing (not available via API; use Search Console UI)
+
+### Discovered but not indexed
+
+Google knows the URL exists but has not crawled it. This often indicates:
+- **Crawl budget**: The site has too many pages relative to its authority
+- **Internal linking**: The page is poorly linked from other pages
+- **Priority**: Google does not consider the page important enough to crawl
+
+**Actions:**
+1. Improve internal linking to the page from high-authority pages
+2. Add the URL to the sitemap if it is not already included
+3. Reduce crawl waste by blocking thin/utility pages with `noindex`
+
+### Blocked by robots.txt
+
+```
+# Check if the URL is blocked
+Tool: gsc_inspect_url
+Params:
+  inspection_url: "https://example.com/admin-page/"
+
+# If robotsTxtState is "DISALLOWED", review the robots.txt file
+```
+
+Ensure your `robots.txt` is not accidentally blocking important content pages.
+
+## Best Practices
+
+- **Sitemap freshness**: WordPress SEO plugins (Yoast, Rank Math) auto-generate sitemaps; submit the index sitemap once and let the plugin manage updates
+- **Inspection frequency**: Do not over-inspect; GSC has API quotas. Batch inspections for weekly or monthly audits
+- **New content**: After publishing a significant post, inspect it after 48-72 hours to verify crawling
+- **Redirect chains**: Avoid chains of 3+ redirects; they slow crawling and may cause indexing issues
+- **Status codes**: Regularly check for soft 404s — pages that return 200 but appear empty or error-like to Googlebot
+- **Canonical tags**: Ensure every page has a self-referencing canonical or points to the preferred version
+- **Crawl budget**: For large sites (10,000+ pages), prioritize indexing of high-value pages by improving internal linking and reducing index bloat
+- **Mobile-first**: Google uses mobile crawling by default; ensure `crawledAs: "MOBILE"` succeeds for all important pages

package/skills/wp-search-console/references/keyword-tracking.md

@@ -0,0 +1,181 @@
+# Keyword Tracking
+
+## Overview
+
+Keyword tracking uses GSC search analytics data to monitor how your WordPress site ranks for specific queries in Google Search. The `gsc_search_analytics` and `gsc_top_queries` tools provide clicks, impressions, CTR, and average position data that can be filtered by date range, query, page, country, and device.
+
+## Core Tools
+
+### Get top queries
+
+```
+Tool: gsc_top_queries
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  row_limit: 50
+Returns: Array of queries with clicks, impressions, ctr, position
+```
+
+This returns the top-performing queries ranked by clicks. Use `row_limit` to control how many queries are returned (default: 25, max: 25000).
+
+### Query search analytics with dimensions
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "page"]
+  row_limit: 100
+Returns: Array of rows with keys (query, page), clicks, impressions, ctr, position
+```
+
+Available dimensions:
+- `query` — the search query text
+- `page` — the URL that appeared in search results
+- `country` — ISO 3166-1 alpha-3 country code
+- `device` — DESKTOP, MOBILE, or TABLET
+- `date` — individual date breakdown
+
+### Filter by specific query
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "date"]
+  dimension_filter_groups:
+    - filters:
+        - dimension: "query"
+          operator: "contains"
+          expression: "wordpress seo"
+  row_limit: 100
+```
+
+Filter operators:
+- `contains` — query contains the expression
+- `equals` — exact match
+- `notContains` — excludes queries containing the expression
+- `notEquals` — excludes exact matches
+
+## Tracking Position Changes Over Time
+
+### Daily position tracking
+
+To track how a keyword's position changes day by day:
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "date"]
+  dimension_filter_groups:
+    - filters:
+        - dimension: "query"
+          operator: "equals"
+          expression: "best wordpress plugins"
+  row_limit: 28
+```
+
+This returns one row per day for the specific query, showing position movement across the date range.
+
+### Compare periods
+
+To compare performance between two periods, make two `gsc_search_analytics` calls with different date ranges and compare the results:
+
+```
+# Period 1: Previous month
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-01-01"
+  end_date: "2026-01-31"
+  dimensions: ["query"]
+  row_limit: 100
+
+# Period 2: Current month
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query"]
+  row_limit: 100
+```
+
+Compare `position`, `clicks`, and `impressions` between periods to identify improving and declining keywords.
+
+## Query-Level Analysis
+
+### High-impression, low-CTR queries
+
+These are queries where your page appears frequently but users rarely click — indicating a title or meta description optimization opportunity:
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "page"]
+  row_limit: 200
+```
+
+Filter results where `impressions > 100` and `ctr < 0.02` (2%). These queries should be prioritized for title tag and meta description improvements.
+
+### Position 4-20 keywords (striking distance)
+
+Keywords ranking on positions 4-20 are in "striking distance" — small improvements can move them to page 1 or top 3:
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "page"]
+  row_limit: 500
+```
+
+Filter results where `position >= 4` and `position <= 20` and `impressions > 50`. These are the highest-ROI optimization targets.
+
+### Device-specific rankings
+
+```
+Tool: gsc_search_analytics
+Params:
+  site_url: "https://example.com/"
+  start_date: "2026-02-01"
+  end_date: "2026-02-28"
+  dimensions: ["query", "device"]
+  row_limit: 100
+```
+
+Compare mobile vs desktop rankings. Significant position differences may indicate mobile usability issues.
+
+## Creating Keyword Dashboards
+
+Build a comprehensive keyword report by combining multiple queries:
+
+1. **Top 50 queries by clicks** — `gsc_top_queries` with `row_limit: 50`
+2. **Position trends for target keywords** — `gsc_search_analytics` with `dimensions: ["query", "date"]` filtered by target queries
+3. **Page-level performance** — `gsc_page_performance` to see which pages drive the most search traffic
+4. **Country breakdown** — `gsc_search_analytics` with `dimensions: ["query", "country"]` for geo-specific insights
+
+## Best Practices
+
+- **Date range selection**: Use at least 28 days of data for reliable averages; short ranges (< 7 days) produce noisy data
+- **Regular monitoring**: Track core keywords weekly to catch position drops early; monthly for trend analysis
+- **Segment by intent**: Group queries by intent (informational, transactional, navigational) to align with content strategy
+- **Position averages**: GSC reports average position weighted by impressions; a page ranking #1 for one query and #50 for another may show position 25
+- **Data freshness**: GSC data has a 2-3 day delay; do not expect same-day data
+- **Row limits**: Default row limit is 1000; for comprehensive audits, increase to 25000
+- **Branded vs non-branded**: Separate branded queries (containing your brand name) from non-branded to get a clearer picture of organic discovery
+- **Click vs impression trends**: Rising impressions with flat clicks indicates a CTR problem; rising clicks with flat impressions indicates improved CTR or rankings

package/skills/wp-search-console/scripts/search_console_inspect.mjs

@@ -0,0 +1,178 @@
+/**
+ * search_console_inspect.mjs — Detect Google Search Console configuration readiness.
+ *
+ * Checks WP_SITES_CONFIG for GSC credentials, sitemaps, robots.txt,
+ * and SEO plugin presence.
+ *
+ * Usage:
+ *   node search_console_inspect.mjs [--cwd=/path/to/project]
+ *
+ * Exit codes:
+ *   0 — GSC or SEO configuration found
+ *   1 — no GSC or SEO configuration found
+ */
+
+import { readFileSync, existsSync, readdirSync } from 'node:fs';
+import { join, resolve } from 'node:path';
+import { argv, stdout, exit } from 'node:process';
+
+// ---------------------------------------------------------------------------
+// Helpers
+// ---------------------------------------------------------------------------
+
+function readFileSafe(filePath) {
+  try { return readFileSync(filePath, 'utf-8'); } catch { return null; }
+}
+
+function existsSafe(filePath) {
+  try { return existsSync(filePath); } catch { return false; }
+}
+
+function globDir(dirPath) {
+  try { return readdirSync(dirPath); } catch { return []; }
+}
+
+// ---------------------------------------------------------------------------
+// Detectors
+// ---------------------------------------------------------------------------
+
+function detectGSCConfig() {
+  const gsc = { configured: false, indicators: [] };
+
+  const raw = process.env.WP_SITES_CONFIG;
+  if (!raw) return gsc;
+
+  let sites;
+  try { sites = JSON.parse(raw); } catch { return gsc; }
+  if (!Array.isArray(sites)) return gsc;
+
+  for (const site of sites) {
+    const label = site.name || site.url || 'unknown';
+
+    if (site.gsc_service_account_key) {
+      gsc.configured = true;
+      gsc.indicators.push(`gsc_service_account_key configured for ${label}`);
+    }
+    if (site.gsc_site_url) {
+      gsc.configured = true;
+      gsc.indicators.push(`gsc_site_url configured for ${label}`);
+    }
+  }
+
+  return gsc;
+}
+
+function detectSitemaps(cwd) {
+  const indicators = [];
+  const sitemapPaths = [
+    'sitemap.xml',
+    'sitemap_index.xml',
+    'wp-sitemap.xml',
+  ];
+
+  for (const sitemapFile of sitemapPaths) {
+    if (existsSafe(join(cwd, sitemapFile))) {
+      indicators.push(`sitemap: ${sitemapFile}`);
+    }
+  }
+
+  return { found: indicators.length > 0, indicators };
+}
+
+function detectRobotsTxt(cwd) {
+  const indicators = [];
+  const robotsPath = join(cwd, 'robots.txt');
+
+  if (!existsSafe(robotsPath)) {
+    return { found: false, indicators };
+  }
+
+  indicators.push('robots.txt exists');
+
+  const content = readFileSafe(robotsPath);
+  if (content) {
+    const lower = content.toLowerCase();
+    if (lower.includes('sitemap:') || lower.includes('sitemap_index')) {
+      indicators.push('robots.txt references sitemap');
+    }
+  }
+
+  return { found: true, indicators };
+}
+
+function detectSEOPlugins(cwd) {
+  const indicators = [];
+  const plugins = globDir(join(cwd, 'wp-content', 'plugins'));
+
+  const seoPlugins = [
+    { dir: 'wordpress-seo', name: 'Yoast SEO' },
+    { dir: 'seo-by-rank-math', name: 'RankMath' },
+    { dir: 'all-in-one-seo-pack', name: 'AIOSEO' },
+  ];
+
+  for (const plugin of plugins) {
+    const pluginLower = plugin.toLowerCase();
+    for (const seo of seoPlugins) {
+      if (pluginLower.includes(seo.dir)) {
+        indicators.push(`seo_plugin: ${seo.name} (${plugin})`);
+      }
+    }
+  }
+
+  return { found: indicators.length > 0, indicators };
+}
+
+// ---------------------------------------------------------------------------
+// Main
+// ---------------------------------------------------------------------------
+
+function main() {
+  const cwdArg = argv.find(a => a.startsWith('--cwd='));
+  const cwd = cwdArg ? resolve(cwdArg.split('=')[1]) : process.cwd();
+
+  const gsc = detectGSCConfig();
+  const sitemaps = detectSitemaps(cwd);
+  const robots_txt = detectRobotsTxt(cwd);
+  const seo_plugins = detectSEOPlugins(cwd);
+
+  const found = gsc.configured || sitemaps.found || robots_txt.found || seo_plugins.found;
+
+  const recommendations = [];
+
+  if (gsc.configured) {
+    recommendations.push('GSC configured — use wp-search-console skill to track keyword rankings and indexing');
+  }
+  if (sitemaps.found) {
+    recommendations.push('Sitemap detected — GSC can be configured to monitor indexing coverage');
+  }
+  if (seo_plugins.found) {
+    recommendations.push('SEO plugin detected — integrate with GSC for keyword-to-content feedback loop');
+  }
+  if (robots_txt.found && robots_txt.indicators.some(i => i.includes('references sitemap'))) {
+    recommendations.push('Sitemap reference found in robots.txt — good for GSC crawling');
+  }
+  if (!found) {
+    recommendations.push('No GSC or SEO configuration detected — use wp-search-console skill to set up Google Search Console');
+  }
+  if (gsc.configured && sitemaps.found && seo_plugins.found) {
+    recommendations.push('Full SEO stack ready — use wp-search-console for keyword tracking and content optimization');
+  }
+
+  const report = {
+    tool: 'search_console_inspect',
+    version: '1.0.0',
+    timestamp: new Date().toISOString(),
+    cwd,
+    found,
+    gsc,
+    sitemaps,
+    robots_txt,
+    seo_plugins,
+    recommendations,
+  };
+
+  stdout.write(JSON.stringify(report, null, 2) + '\n');
+  exit(found ? 0 : 1);
+}
+
+main();

package/skills/wp-social-email/SKILL.md

@@ -0,0 +1,152 @@
+---
+name: wp-social-email
+description: This skill should be used when the user asks to "publish to social media",
+  "schedule social posts", "send email campaign", "Mailchimp integration",
+  "Buffer scheduling", "SendGrid email", "content distribution",
+  "newsletter campaign", "email marketing", "social media management",
+  "distribute content", or mentions publishing WordPress content to social
+  and email channels.
+version: 1.0.0
+---
+
+# WordPress Social & Email Distribution Skill
+
+## Overview
+
+Social and email distribution connects WordPress content to external marketing channels via three services: Mailchimp (email campaigns and audience management), Buffer (social media scheduling and publishing), and SendGrid (transactional email delivery). The WP REST Bridge provides 18 MCP tools across these services, enabling content distribution workflows directly from the WordPress authoring environment.
+
+## When to Use
+
+- User wants to send a newsletter or email campaign from WordPress content
+- User needs to schedule social media posts when a blog post is published
+- User asks about Mailchimp audience management or subscriber lists
+- User wants to connect Buffer for social media scheduling
+- User needs transactional email delivery via SendGrid (welcome emails, confirmations)
+- User asks about content distribution pipelines (blog → social → email)
+- User wants to segment audiences for targeted campaigns
+- User needs analytics on email open rates, click rates, or social engagement
+
+## Decision Tree
+
+1. **What channel or service?**
+   - "Mailchimp" / "audience" / "email campaign" / "newsletter" → Mailchimp integration (Section 1)
+   - "Buffer" / "social post" / "schedule tweet" / "social media" → Buffer social publishing (Section 2)
+   - "SendGrid" / "transactional email" / "email delivery" → SendGrid transactional (Section 3)
+   - "distribute content" / "blog to social" / "content pipeline" → Content-to-distribution workflow (Section 4)
+   - "audience segment" / "targeting" / "list management" → Audience segmentation (Section 5)
+   - "email analytics" / "open rate" / "click rate" / "campaign report" → Distribution analytics (Section 6)
+
+2. **Run detection first:**
+   ```bash
+   node skills/wp-social-email/scripts/distribution_inspect.mjs [--cwd=/path/to/project]
+   ```
+   This identifies configured distribution services and API credentials.
+
+## Service Overview
+
+| Service | Tools | Auth Type | Use Case |
+|---------|-------|-----------|----------|
+| Mailchimp | 7 tools (`mc_*`) | API key | Email campaigns, audience management, subscriber lists |
+| Buffer | 5 tools (`buf_*`) | Access token | Social media scheduling, queue management, analytics |
+| SendGrid | 6 tools (`sg_*`) | API key | Transactional email, templates, contact management |
+
+## Distribution Sections
+
+### Section 1: Mailchimp Integration
+See `references/mailchimp-integration.md`
+- API key setup and WP_SITES_CONFIG configuration
+- Audience management (list, get members, add subscribers)
+- Campaign workflow: create → set content → send → report
+- A/B testing and send time optimization
+
+### Section 2: Buffer Social Publishing
+See `references/buffer-social-publishing.md`
+- Access token setup and WP_SITES_CONFIG configuration
+- Profile management and channel connections
+- Post creation with media attachments and scheduling
+- Queue management and posting analytics
+
+### Section 3: SendGrid Transactional Email
+See `references/sendgrid-transactional.md`
+- API key setup and WP_SITES_CONFIG configuration
+- Transactional email for welcome, password reset, order confirmation
+- Dynamic template management
+- Contact management and email deliverability
+
+### Section 4: Content-to-Distribution Workflow
+See `references/content-to-distribution.md`
+- WordPress-to-channel pipeline (fetch post → format → distribute)
+- Content adaptation per channel (blog → social, blog → newsletter)
+- Scheduling strategies (immediate, drip, evergreen rotation)
+- Multi-channel orchestration
+
+### Section 5: Audience Segmentation
+See `references/audience-segmentation.md`
+- Mailchimp list segmentation strategies
+- SendGrid contact lists and custom fields
+- Buffer profile-based targeting
+- Building audience personas from WordPress user data
+
+### Section 6: Distribution Analytics
+See `references/distribution-analytics.md`
+- Mailchimp campaign reports (open rate, click rate, bounces)
+- Buffer analytics (reach, engagement, clicks)
+- SendGrid stats (deliverability, opens, clicks)
+- Cross-channel performance comparison and KPIs
+
+## Reference Files
+
+| File | Content |
+|------|---------|
+| `references/mailchimp-integration.md` | API setup, audiences, campaigns, A/B testing |
+| `references/buffer-social-publishing.md` | Access token, profiles, posts, queue management |
+| `references/sendgrid-transactional.md` | API setup, transactional email, templates, contacts |
+| `references/content-to-distribution.md` | Content pipeline, adaptation, scheduling, multi-channel |
+| `references/audience-segmentation.md` | List segmentation, custom fields, personas |
+| `references/distribution-analytics.md` | Campaign reports, social stats, KPIs, benchmarks |
+
+## MCP Tools
+
+### Mailchimp Tools (7)
+
+| Tool | Description |
+|------|-------------|
+| `mc_list_audiences` | List all Mailchimp audiences (lists) with member counts |
+| `mc_get_audience_members` | Get subscribers for a specific audience with pagination |
+| `mc_add_subscriber` | Add or update a subscriber in an audience |
+| `mc_create_campaign` | Create a new email campaign (regular, plaintext, A/B test) |
+| `mc_set_campaign_content` | Set the HTML or template content for a campaign |
+| `mc_send_campaign` | Send or schedule a campaign for delivery |
+| `mc_get_campaign_report` | Get campaign performance metrics (opens, clicks, bounces) |
+
+### Buffer Tools (5)
+
+| Tool | Description |
+|------|-------------|
+| `buf_list_profiles` | List connected social media profiles (Twitter, Facebook, LinkedIn, etc.) |
+| `buf_create_update` | Create a social media post with text, media, and optional schedule time |
+| `buf_list_pending` | List posts in the Buffer queue awaiting publication |
+| `buf_list_sent` | List previously published posts with engagement data |
+| `buf_get_analytics` | Get analytics for a profile (reach, engagement, clicks) |
+
+### SendGrid Tools (6)
+
+| Tool | Description |
+|------|-------------|
+| `sg_send_email` | Send a transactional email (plain, HTML, or template-based) |
+| `sg_list_templates` | List available dynamic email templates |
+| `sg_get_template` | Get template details including version and HTML content |
+| `sg_list_contacts` | List contacts with optional search and filtering |
+| `sg_add_contacts` | Add or update contacts with custom fields |
+| `sg_get_stats` | Get email statistics (deliveries, opens, clicks, bounces) |
+
+## Recommended Agent
+
+Use the **`wp-distribution-manager`** agent for complex multi-channel distribution workflows that span multiple services or require coordinated content adaptation.
+
+## Related Skills
+
+- **`wp-content-repurposing`** — transform content formats before distribution
+- **`wp-webhooks`** — trigger distribution on WordPress events (publish, update)
+- **`wp-content`** — create and manage WordPress content for distribution
+- **`wp-content-attribution`** — track content sources and attribution across channels