Shopify Admin Collection Membership Audit

Safety

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

Workflow Steps

1. OPERATION: products — query Inputs: query: "status:<status_filter>", first: 250, select collections { edges { node { id } } }, pagination cursor Expected output: Products with their collection memberships; paginate until hasNextPage: false

2. For each product: count collections → flag if 0 (orphan) or > max_collections (over-collected)

3. OPERATION: collections — query (for collection names) Inputs: first: 250, select id, title, productsCount Expected output: Collection metadata for enriching the report

GraphQL Operations

# products:query — validated against api_version 2025-01
query ProductCollectionMembership($query: String!, $after: String) {
  products(first: 250, after: $after, query: $query) {
    edges {
      node {
        id
        title
        handle
        status
        collections(first: 30) {
          edges {
            node {
              id
              title
            }
          }
        }
      }
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}

# collections:query — validated against api_version 2025-01
query CollectionOverview($after: String) {
  collections(first: 250, after: $after) {
    edges {
      node {
        id
        title
        handle
        productsCount {
          count
        }
      }
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}

Session Tracking

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

On start, emit:

╔══════════════════════════════════════════════╗
║  SKILL: Collection Membership 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):

══════════════════════════════════════════════
COLLECTION MEMBERSHIP AUDIT
  Products scanned:      <n>
  Orphan products (0 collections):     <n>
  Over-collected (> <max_collections>): <n>

  Orphan products (sample):
    "<title>" — <status>
  Output: collection_audit_<date>.csv
══════════════════════════════════════════════

For format: json, emit:

{
  "skill": "collection-membership-audit",
  "store": "<domain>",
  "products_scanned": 0,
  "orphan_count": 0,
  "over_collected_count": 0,
  "output_file": "collection_audit_<date>.csv"
}

Output Format

CSV file collection_audit_<YYYY-MM-DD>.csv with columns: product_id, title, handle, status, collection_count, collections, issue

Error Handling

Best Practices

• Orphan active products are invisible in store navigation — customers can only find them via direct URL or search. Prioritize fixing these.
• Automated collections (rule-based) may automatically pull products based on tags or conditions — an orphan in manual collections may still appear in automated ones. Check both.
• Use max_collections: 5 for stores with a tightly curated navigation; use higher thresholds for marketplace-style stores where cross-listing is intentional.
• Run after seasonal catalog refreshes to ensure all new products are assigned to the right collections.