Cf Publish

Publish Content — ContentForge CMS Publishing

Push publication-ready content from the ContentForge pipeline directly to your CMS (Webflow or WordPress) via MCP connectors. Preview before publishing, verify post-publish, and fall back to HTML export when no connector is available.

Context efficiency

Pipeline phase. Grep before Read for references/, humanization-patterns.json, brand voice profiles. Pass earlier-phase outputs by path + line range, not by reloading. On /contentforge:resume, load only the failed phase's state.

When to Use

Use /cf-publish when:

• You have a finished, reviewed content piece (Phase 8 complete, score >=7.0)
• You want to publish directly to Webflow or WordPress without copy-pasting
• You need to schedule content for a future publish date
• You want post-publish verification (URL live, meta tags correct, images loaded)
• You want an HTML export for manual upload when no CMS connector is configured

Do NOT use for:

• Content still in pipeline (must be Phase 8 complete)
• Content flagged for human review (score = 7.0 (refuse to publish unreviewed content)

Validation checks:

Content Validation
---------------------------------------------------
Title: "AI in Healthcare: 2026 Trends"        OK
Quality Score: 9.2/10                          OK
Status: Approved (Phase 8 Complete)            OK
Word Count: 1,947                              OK
Meta Title: 58 chars                           OK
Meta Description: 152 chars                    OK
SEO Slug: ai-in-healthcare-2026-trends         OK
Featured Image: hero-ai-healthcare.jpg         OK
---------------------------------------------------
All checks passed. Ready to format for Webflow.

Rejection cases:

• Quality score : "AI in Healthcare: 2026 Trends..." PASS

: Present, 152 chars PASS : Present PASS : Present PASS : Present PASS

Content Integrity: H1 present: "AI in Healthcare: 2026 Trends" PASS Word count matches: 1,947 (expected 1,947) PASS Images loaded: 3/3 PASS Internal links valid: 5/5 PASS

SEO Elements: URL slug correct: ai-in-healthcare-2026-trends PASS Schema markup: Article (JSON-LD) PASS Robots meta: index, follow PASS

=================================================== All 12 checks passed. Content is live and verified.

**If verification fails:**

VERIFICATION WARNING =================================================== URL Accessible: 200 OK PASS Meta Description: MISSING FAIL Expected: "Explore how AI is transforming..." Found: (empty)

Action: Meta description did not save correctly. Attempting fix via API PATCH... Fixed: Meta description updated. Re-verification: PASS ===================================================

### Step 7: Update Tracking Sheet

After successful publish:

Tracking Sheet Updated: Row: 5 Status: "Published" Published URL: https://acme-corp.webflow.io/blog/ai-in-healthcare-2026-trends Published At: 2026-02-25 14:30:00 Platform: Webflow Verification: All 12 checks passed

## Fallback: HTML Export Mode

When no CMS connector is available, generate a standalone HTML file.

### What Gets Generated

Output: .tmp/publish-exports/ai-in-healthcare-2026-trends.html

HTML Export includes:

• Full article content in clean, semantic HTML5
• Inline CSS for typography (portable, no external dependencies)
• Meta tags in (title, description, OG tags, Twitter cards)
• Schema.org Article markup (JSON-LD)
• Featured image with alt text
• Responsive formatting (mobile-friendly)
• Copy-paste ready for any CMS

### HTML Export File Structure

```html

  
  AI in Healthcare: 2026 Trends and Predictions
  
  
  
  
  
    { "@context": "https://schema.org", "@type": "Article", ... }
  

  
    AI in Healthcare: 2026 Trends and Predictions
    
  

Manual Upload Instructions

HTML Export Complete
===================================================
File: .tmp/publish-exports/ai-in-healthcare-2026-trends.html
Size: 48 KB

Manual Upload Instructions:
1. Open your CMS dashboard
2. Create a new blog post / article
3. Switch to HTML/code view
4. Copy the contents of the  tag
5. Paste into the content editor
6. Copy meta title and description from the  section
7. Upload featured image separately
8. Set URL slug to: ai-in-healthcare-2026-trends
9. Preview and publish

Alternatively, connect your CMS for direct publishing:
  /digital-marketing-pro:connect webflow
  /digital-marketing-pro:connect wordpress
===================================================

Output Example

Successful Publish:

CONTENTFORGE PUBLISH COMPLETE
===================================================

Content: AI in Healthcare: 2026 Trends
Platform: Webflow
Status: Published (LIVE)
URL: https://acme-corp.webflow.io/blog/ai-in-healthcare-2026-trends

Quality Score: 9.2/10
Word Count: 1,947
Meta Tags: All present and verified
Images: 3 loaded
Verification: 12/12 checks passed

Tracking Sheet: Updated (Row 5)
Published At: 2026-02-25 14:30:00

===================================================
Content is live and verified. No further action required.

Error Handling

CMS API Rate Limit

Error: 429 Too Many Requests
Action: Wait 60 seconds, retry (max 3 attempts)
If persistent: Save as draft, notify user to publish manually

Authentication Expired

Error: 401 Unauthorized
Action: Prompt user to re-authenticate
  Webflow: Re-authorize at https://webflow.com/oauth/authorize
  WordPress: Refresh application password

Content Too Large

Error: 413 Payload Too Large (WordPress limit: 2MB per post)
Action: Split content into parts or compress images
Fallback: Generate HTML export, notify user

Duplicate Slug

Error: Slug "ai-in-healthcare-2026-trends" already exists
Action: Check if this is an update (v1.1 refresh) or duplicate
  If update: PATCH existing post (preserve URL, update content)
  If duplicate: Append "-2" to slug, warn user

Image Upload Failure

Error: Featured image upload failed (timeout)
Action: Retry image upload (3 attempts)
Fallback: Publish without featured image, flag for manual fix
  "Published successfully but featured image failed to upload.
   Please upload hero-ai-healthcare.jpg manually in your CMS."

Platform-Specific Notes

Webflow

• Uses Collection Items API for blog posts
• Rich text field supports HTML content directly
• Images must be uploaded to Webflow Assets first, then referenced
• Publish requires site publish after item creation (API call to publish site)
• CMS items are draft by default; explicit publish step needed
• Rate limit: 60 requests per minute

WordPress

• Uses REST API v2 (/wp-json/wp/v2/posts)
• Gutenberg blocks preferred over classic editor HTML
• Featured image uploaded via /wp-json/wp/v2/media, then linked by ID
• Categories and tags are taxonomy term IDs (lookup by name first)
• Supports date field for scheduling
• Application Passwords or OAuth for authentication
• Rate limit: Varies by host (typically 100-500 requests/minute)

Requirements

MCP Integrations (Optional but Recommended)

• Webflow MCP (https://mcp.webflow.com/sse) -- For direct Webflow publishing
• WordPress -- Via REST API (no MCP endpoint; uses HTTP connector or direct API)

Environment

• Claude Code or Cowork (latest version)
• Content must have completed Phase 8 (Output Manager)
• Quality score >= 7.0

Integration with Other Skills

Before Publishing:

• /contentforge -- Generate the content piece
• /batch-process -- Generate multiple pieces for bulk publishing
• /content-refresh -- Update old content before republishing

After Publishing:

• /cf-social-adapt -- Generate social media posts to promote the published article
• /content-refresh -- Schedule future refresh for evergreen content

Related Skills

• [/contentforge](../contentforge/SKILL.md) -- Full content production pipeline
• [/batch-process](../batch-process/SKILL.md) -- Parallel content production
• [/content-refresh](../content-refresh/SKILL.md) -- Update existing content
• [/cf-social-adapt](../cf-social-adapt/SKILL.md) -- Social media adaptation

---

Version: 3.4.0 Agent: Output Manager (Phase 8) + CMS Publisher utility Utilities: cms-publisher.md Platforms: Webflow, WordPress Fallback: HTML export for manual upload

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: indranilbanerjee
• Source: indranilbanerjee/contentforge
• License: MIT
• Homepage: https://indranil.in

Install and usage instructions live in the source repository linked above.