跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

shopify-admin-agentic-metafields-setup

Define and populate agentic-commerce metafields (material, attributes, key features, specs, sizing) so AI agents can filter and match products to specific shopper requirements.

40RTY-ai · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add 40RTY-ai/shopify-admin-skills --skill shopify-admin-agentic-metafields-setup

技能说明


name: shopify-admin-agentic-metafields-setup role: agentic description: "Define and populate agentic-commerce metafields (material, attributes, key features, specs, sizing) so AI agents can filter and match products to specific shopper requirements." toolkit: shopify-admin, shopify-admin-execution api_version: "2025-01" graphql_operations:

  • metafieldDefinitions:query
  • metafieldDefinitionCreate:mutation
  • products:query
  • metafieldsSet:mutation status: stable compatibility: Claude Code, Cursor, Codex, Gemini CLI audit_signals:
  • listing-metafields
  • variant-metadata
  • sizing-specs-structured

Purpose

AI agents answer constrained queries — "squat-proof leggings under $60", "eucalyptus slip-ons", "machine-washable wool" — by filtering on structured attributes. If those attributes live only in prose (or nowhere), the agent can't filter and your products drop out of the result set. This skill establishes a small, standard set of agentic metafield definitions (material, key features, care, fit, specs) and populates them across the catalog from existing product signals, so agents can match products to requirements. Fixes listing-metafields, variant-metadata, and sizing-specs-structured.

Prerequisites

  • Authenticated Shopify CLI session (shopify auth login --store <domain>)
  • Required API scopes: read_products, write_products, read_metaobject_definitions, write_metaobject_definitions (for definitions)

Parameters

All skills accept these universal parameters:

ParameterTypeRequiredDefaultDescription
storestringyes—Store domain (e.g., mystore.myshopify.com)
formatstringnohumanOutput format: human (default) or json
dry_runboolnofalsePreview mutations without executing

Skill-specific parameters:

ParameterTypeRequiredDefaultDescription
namespacestringnoagenticMetafield namespace to create/populate under
keysstringnomaterial,features,care,fit,specsComma list of metafield keys to ensure exist
collection_idstringno—Limit population to a collection GID
tagstringno—Limit population to a product tag
populate_fromstringnotags,options,descriptionSources to infer values from (no fabrication beyond these)

Safety

⚠️ Step 2 (metafieldDefinitionCreate) and Step 4 (metafieldsSet) write store schema + product data. Definitions are cheap to add but clutter the admin if mis-namespaced; values written from inference can be wrong. Run dry_run: true, review the proposed definitions and the value preview, and only populate values inferred with high confidence — leave the rest blank for human fill.

Workflow Steps

  1. OPERATION: metafieldDefinitions — query Inputs: ownerType: PRODUCT, namespace: <namespace> Expected output: Which target keys already have definitions (skip those).

  2. OPERATION: metafieldDefinitionCreate — mutation Inputs: one per missing key: { namespace, key, name, ownerType: PRODUCT, type: "single_line_text_field" | "list.single_line_text_field" } Expected output: Created definitions; collect userErrors (e.g. already-taken).

  3. OPERATION: products — query Inputs: first: 250, optional filter; fields tags, options, descriptionHtml, existing metafields(namespace); paginate. Expected output: Products + the signals to infer attribute values from.

  4. OPERATION: metafieldsSet — mutation Inputs: batches of { ownerId, namespace, key, value, type } for confidently-inferred, currently-empty values. Expected output: Set metafields; collect userErrors.

GraphQL Operations

# metafieldDefinitions:query — validated against api_version 2025-01
query AgenticMetafieldDefs($namespace: String!) {
  metafieldDefinitions(first: 50, ownerType: PRODUCT, namespace: $namespace) {
    edges { node { id namespace key name type { name } } }
  }
}
# metafieldDefinitionCreate:mutation — validated against api_version 2025-01
mutation AgenticMetafieldDefCreate($definition: MetafieldDefinitionInput!) {
  metafieldDefinitionCreate(definition: $definition) {
    createdDefinition { id namespace key }
    userErrors { field message code }
  }
}
# products:query — validated against api_version 2025-01
query AgenticMetafieldProducts($first: Int!, $after: String, $query: String, $namespace: String!) {
  products(first: $first, after: $after, query: $query) {
    edges {
      node {
        id
        title
        tags
        options { name values }
        descriptionHtml
        metafields(first: 20, namespace: $namespace) {
          edges { node { key value } }
        }
      }
    }
    pageInfo { hasNextPage endCursor }
  }
}
# metafieldsSet:mutation — validated against api_version 2025-01
mutation AgenticMetafieldsSet($metafields: [MetafieldsSetInput!]!) {
  metafieldsSet(metafields: $metafields) {
    metafields { id namespace key }
    userErrors { field message code }
  }
}

Session Tracking

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

On start, emit:

╔══════════════════════════════════════════════╗
║  SKILL: <skill name>                         ║
║  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>

If dry_run: true, prefix every mutation step with [DRY RUN] and do not execute it.

On completion, emit:

For format: human (default):

═════════════════════════════
阅读完整来源 ↗