Publication Channel Audit

Purpose

Queries all active products and the publications (sales channels) they are visible on. Flags products that are active but missing from key channels (e.g., Online Store, Google Shopping, Meta). Prevents silent revenue loss from products that exist in the catalog but are invisible on sales channels. Read-only — no mutations.

Prerequisites

Parameters

Safety

> ℹ️ Read-only skill — no mutations are executed. Safe to run at any time.

Workflow Steps

Inputs: first: 50

Expected output: All available publications (sales channels) with id, name

Inputs: query: "status:active", first: 250, select publishedOnCurrentPublication, resourcePublications { publication { name } }, pagination cursor

Expected output: Active products with their channel publication status

GraphQL Operations

# publications:query — validated against api_version 2025-01
query SalesChannels {
  publications(first: 50) {
    edges {
      node {
        id
        name
        supportsFuturePublishing
        app {
          title
        }
      }
    }
  }
}

# products:query — validated against api_version 2025-01
query ProductPublications($after: String) {
  products(first: 250, after: $after, query: "status:active") {
    edges {
      node {
        id
        title
        handle
        status
        resourcePublications(first: 20) {
          edges {
            node {
              publication {
                id
                name
              }
              publishDate
              isPublished
            }
          }
        }
      }
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}

Session Tracking

Claude MUST emit the following output at each stage. This is mandatory.

On start, emit:

╔══════════════════════════════════════════════╗
║  SKILL: Publication Channel Audit            ║
║  Store: <store domain>                       ║
║  Started: <YYYY-MM-DD HH:MM UTC>             ║
╚══════════════════════════════════════════════╝

After each step, emit:

[N/TOTAL] <QUERY|MUTATION>  <OperationName>
          → Params: <brief summary of key inputs>
          → Result: <count or outcome>

On completion, emit:

For format: human (default):

══════════════════════════════════════════════
PUBLICATION CHANNEL AUDIT
  Active products:          <n>
  Sales channels found:     <n>
  Products missing channels: <n>

  Missing from "Online Store":
    "<product title>"  (<handle>)
  Output: publication_audit_<date>.csv
══════════════════════════════════════════════

For format: json, emit:

{
  "skill": "publication-channel-audit",
  "store": "<domain>",
  "active_products": 0,
  "channels_found": 0,
  "missing_channel_count": 0,
  "output_file": "publication_audit_<date>.csv"
}

Output Format

CSV file publication_audit_.csv with columns:

product_id, title, handle, channel_name, is_published, publish_date, issue

Error Handling

Best Practices