---

name: sync-docs description: Sync documentation and screenshots to any knowledge base provider (Pylon, Zendesk, Confluence, etc.). Handles two modes: (1) Upload screenshots to KB CDN and return URLs, (2) Sync markdown documentation to KB with proper collection assignment. Provider-agnostic with automatic provider detection from config.

Sync Documentation to Knowledge Base

Sync screenshots and documentation to any knowledge base provider.

Supported Providers: Pylon, Zendesk, Confluence, Notion, and more.

Purpose

This skill handles knowledge base integration in two modes:

1. Upload Mode: Upload screenshots to KB CDN/storage, get URLs
2. Sync Mode: Convert markdown to provider-specific HTML, sync to KB with correct collection

Provider Selection

The skill automatically detects your active KB provider from config.yaml:

Copyknowledge_base:
  provider: "pylon"  # or "zendesk", "confluence", etc.
  providers:
    pylon:
      # Pylon-specific config
    zendesk:
      # Zendesk-specific config

You can also override the provider for a specific operation using --provider.

Prerequisites

1. KB Configuration: Provider credentials and settings in config.yaml
2. Python Environment: KB provider scripts installed
3. Screenshots Captured: For upload mode
4. Documentation Written: For sync mode

Mode 1: Upload Screenshots

When to Use

After screenshots are captured, before creating documentation. You need CloudFront URLs to embed in documentation.

Input

• Feature name
• Screenshots directory (from config.yaml)
• Screenshot filenames

Process

Step 1: Locate Screenshots

Find the captured screenshots:

Copyls -lh output/screenshots/[feature]-*.png

Verify:

• Screenshots exist
• Filenames are correct
• File sizes are reasonable (not 0 bytes)

Step 2: Upload to KB Provider

Use the generic KB upload script for each screenshot:

Copycd /path/to/max-doc-ai

# Uses provider from config.yaml
python3 scripts/kb/upload.py \
  --image output/screenshots/[feature]-overview.png \
  --alt "[Feature Name] overview"

# Or specify provider explicitly
python3 scripts/kb/upload.py \
  --provider zendesk \
  --image output/screenshots/[feature]-overview.png \
  --alt "[Feature Name] overview"

For multiple screenshots, upload each one:

Copy# Screenshot 1
python3 scripts/kb/upload.py \
  --image output/screenshots/[feature]-overview.png \
  --alt "[Feature Name] overview"

# Screenshot 2
python3 scripts/kb/upload.py \
  --image output/screenshots/[feature]-detail.png \
  --alt "[Feature Name] detailed view"

# ... continue for all screenshots

Step 3: Collect CDN URLs

The upload script will output CDN URLs like:

Copy📤 Uploading: feature-overview.png
   ✅ Uploaded: https://cdn-url.example.com/attachments/abc123/feature-overview.png

Save all URLs - you'll need them for the documentation.

Note: URL format varies by provider:

• Pylon: CloudFront URLs (https://d...cloudfront.net/...)
• Zendesk: Zendesk CDN URLs
• Confluence: Atlassian media URLs

Step 4: Create URL Mapping

Document the mapping:

Copy## CloudFront URLs for [Feature Name]

1. **[feature]-overview.png**
   - CloudFront URL: https://d1234abcd.cloudfront.net/attachments/abc123/feature-overview.png
   - Alt text: [Feature Name] overview

2. **[feature]-detail.png**
   - CloudFront URL: https://d1234abcd.cloudfront.net/attachments/abc123/feature-detail.png
   - Alt text: [Feature Name] detailed view

[... continue for all screenshots ...]

Step 5: Provide URLs to Next Step

Return the CloudFront URLs so they can be used in documentation:

Copy✅ Screenshot Upload Complete

Uploaded [X] screenshots to Pylon CDN.

CloudFront URLs:
- feature-overview: https://cloudfront.url/1.png
- feature-detail: https://cloudfront.url/2.png
[... list all ...]

These URLs should be used in the documentation markdown.

---

Mode 2: Sync Documentation

When to Use

After documentation is written with embedded CloudFront URLs. This publishes the documentation to Pylon knowledge base.

Input

• Feature name
• Category (must match config.yaml collections)
• Documentation file path
• Title and slug for the article

Process

Step 1: Verify Documentation File

Check that documentation file exists and is valid:

Copycat output/features/YYYY-MM-DD_[feature-slug]/[feature-slug].md

Verify:

• File exists
• Valid markdown
• No H1 heading (starts with H2)
• Screenshots use CloudFront URLs
• Content is complete

Step 2: Determine Article Key

Create a unique key for state tracking:

Pattern: [category]-[feature-slug]

Examples:

• features-dashboards
• integrations-slack
• getting-started-quickstart

This key is used to track whether the article already exists in Pylon.

Step 3: Sync to KB Provider

Use the generic KB sync script:

Copycd /path/to/max-doc-ai

# Uses provider from config.yaml
python3 scripts/kb/sync.py \
  --file output/features/YYYY-MM-DD_[feature-slug]/[feature-slug].md \
  --key [category]-[feature-slug] \
  --title "[Feature Name]" \
  --slug "[feature-slug]" \
  --collection [category]

# Or specify provider explicitly
python3 scripts/kb/sync.py \
  --provider zendesk \
  --file output/features/YYYY-MM-DD_[feature-slug]/[feature-slug].md \
  --key [category]-[feature-slug] \
  --title "[Feature Name]" \
  --slug "[feature-slug]" \
  --collection [category]

Example:

Copypython3 scripts/kb/sync.py \
  --file output/features/2025-12-22_dashboards/dashboards.md \
  --key features-dashboards \
  --title "Dashboards" \
  --slug "dashboards" \
  --collection features

Step 4: Monitor Sync Process

The script will:

1. Read markdown file
2. Convert to HTML
3. Wrap images in React components (required by Pylon)
4. Check if article exists (via state file)
5. Create new or update existing article
6. Set collection_id (CRITICAL: must be set during creation)
7. Return article URLs

Watch for:

Copy📄 Syncing: dashboards.md
🔄 Converting markdown to HTML...
   ✅ 3 images with React wrappers
✨ Creating new article...
   Collection: features (abc-123-collection-id)
   ✅ Created article ID: xyz-789-article-id
💾 State updated: features-dashboards

Step 5: Extract Article URLs

The sync will output:

Copy✅ Article synced successfully!
   Public URL: https://yourproduct-kb.help.usepylon.com/articles/dashboards
   Internal URL: https://app.usepylon.com/docs/[kb-id]/articles/[article-id]

Save both URLs:

• Public URL: For customer-facing announcements
• Internal URL: For editing and management

Step 6: Verify in Pylon

Optional but recommended - verify the article in Pylon:

1. Open the public URL in browser
2. Check that:
   • Article title is correct
   • Content is properly formatted
   • Screenshots are visible and sized correctly
   • Images have React wrappers (inspect HTML if needed)
   • Article is in the correct collection

Step 7: Document Results

Provide a summary:

Copy## Documentation Synced: [Feature Name]

**Article Title:** [Feature Name]
**Slug:** [feature-slug]
**Category/Collection:** [category]
**State Key:** [category]-[feature-slug]

### URLs:

**Public (for announcements):**
https://yourproduct-kb.help.usepylon.com/articles/[slug]

**Internal (for editing):**
https://app.usepylon.com/docs/[kb-id]/articles/[article-id]

### Technical Details:

- Markdown file: output/features/YYYY-MM-DD_[feature-slug]/[feature-slug].md
- Images: [X] screenshots with React wrappers
- Collection ID: [collection-id]
- Article ID: [article-id]
- Created/Updated: [timestamp]

### Next Steps:

Use the public URL in customer announcements.

---

Provider-Specific Details

Content Conversion

Each provider may have specific HTML requirements:

Pylon: Requires images to be wrapped in React component structures. The PylonProvider handles this automatically.

Structure:

Copy<div class="react-renderer node-imageBlock" contenteditable="false" draggable="true">
  <div data-node-view-wrapper="" style="white-space: normal;">
    <button aria-label="Preview image: Preview" class="inline-block w-full cursor-zoom-in">
      <div class="ml-auto mr-auto mx-auto" style="width: 100%;">
        <div contenteditable="false">
          <img class="block" alt="..." src="https://cloudfront.url/image.png">
        </div>
      </div>
    </button>
  </div>
</div>

Why this matters:

• Without this structure, images won't render in Pylon
• The structure is NOT optional
• Must be exact format

Collection ID Requirement

CRITICAL: The collection_id MUST be set when creating an article. It cannot be reliably added later via PATCH requests.

This is why the sync script:

1. Checks state to see if article exists
2. If new, creates with collection_id set
3. If existing, updates via PATCH (collection already set)

State Tracking

Pylon's API doesn't provide a "list all articles" endpoint, so we maintain our own state file:

Location: demo/docs/sync-state.json

Structure:

Copy{
  "knowledge_base_id": "...",
  "articles": {
    "features-dashboards": {
      "article_id": "...",
      "collection_id": "...",
      "public_url": "...",
      "internal_url": "...",
      "synced_at": "2025-01-15T10:30:00Z"
    }
  }
}

URL Encoding

CloudFront URLs often contain & characters in query parameters. Pylon requires unencoded ampersands (& not &). The converter handles this automatically.

Configuration

Knowledge base settings in config.yaml:

Copyknowledge_base:
  # Active provider
  provider: "pylon"  # or "zendesk", "confluence", etc.

  # Provider-specific configurations
  providers:
    pylon:
      api_key: "${PYLON_API_KEY}"
      kb_id: "${PYLON_KB_ID}"
      author_user_id: "${PYLON_AUTHOR_ID}"
      api_base: "https://api.usepylon.com"
      collections:
        getting-started: "${COLLECTION_GETTING_STARTED_ID}"
        features: "${COLLECTION_FEATURES_ID}"
        integrations: "${COLLECTION_INTEGRATIONS_ID}"

    zendesk:
      subdomain: "${ZENDESK_SUBDOMAIN}"
      email: "${ZENDESK_EMAIL}"
      api_token: "${ZENDESK_API_TOKEN}"
      locale: "en-us"
      categories:
        getting-started: "${ZENDESK_SECTION_ID_1}"
        features: "${ZENDESK_SECTION_ID_2}"
        integrations: "${ZENDESK_SECTION_ID_3}"

Setup Steps:

1. Choose your KB provider
2. Create collections/sections in the provider's UI
3. Copy collection/section IDs
4. Add to config.yaml under the appropriate provider
5. Set knowledge_base.provider to your active provider

Troubleshooting

Upload Failures

Issue: Screenshot upload fails with 401 Unauthorized

Solution:

• Check PYLON_API_KEY is set correctly in .env
• Verify API key has necessary permissions
• Try regenerating API key in Pylon settings

Issue: Upload succeeds but no URL returned

Solution:

• Check Pylon API response format hasn't changed
• Verify network connectivity
• Check image file is valid PNG/JPG

Sync Failures

Issue: Article creation fails with "Collection not found"

Solution:

• Verify collection ID in config.yaml is correct
• Check collection exists in Pylon
• Ensure collection ID matches the category name

Issue: Images don't appear in Pylon article

Solution:

• Verify CloudFront URLs are accessible
• Check React wrappers are applied (run with --validate flag)
• Ensure URLs use unencoded & characters
• Inspect HTML in Pylon to see actual structure

Issue: Article created but in wrong collection

Solution:

• Delete article from Pylon UI
• Remove from state file: python3 scripts/utils/state.py --delete [key]
• Fix collection ID in config.yaml
• Sync again

State Issues

Issue: Sync thinks article exists but it doesn't

Solution:

Copy# Check state
python3 scripts/utils/state.py --summary

# Remove incorrect entry
python3 scripts/utils/state.py --delete [article-key]

# Sync again

Issue: State file corrupted

Solution:

• Backup existing: cp demo/docs/sync-state.json demo/docs/sync-state.json.backup
• Delete state file
• Re-sync all articles (they'll be created fresh)

Integration with Release Workflow

This skill is used twice in the release workflow:

1. Capture screenshots (capture-screenshots skill)
2. ✅ Upload screenshots to CDN ← Mode 1: You are here first
3. Create documentation (update-product-doc skill) ← Uses CloudFront URLs
4. ✅ Sync documentation to Pylon ← Mode 2: You are here second
5. Create announcements (create-changelog skill) ← Uses public article URL

The public article URL from Mode 2 should be provided to the create-changelog skill.