Token导航 LogoToken导航

Agent Skill · 研究检索

shopify-admin-api(Shopify admin API 搜索)

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则;涉及生成接口文档时,应避免凭空补字段,最好从现有代码、schema 或接口样例中提取事实。

shopify-admin-api 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 55,255。

总安装 489周安装 21GitHub Stars 19下载 171核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:shopify-admin-api(Shopify admin API 搜索)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/shopify-admin-api
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill shopify-admin-api
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill shopify-admin-api

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。适合梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则。涉及生成接口文档时,应避免凭空补字段,最好从现有代码、schema 或接口样例中提取事实。

shopify-admin-api 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/shopify-admin-api

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill sho…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

shopify-admin-api 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill shopify-admin…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

shopify-admin-api 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

shopify-admin-api 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

shopify-admin-api 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

shopify-admin-api 用的人多吗?

公开数据是累计安装 489 次,近一周安装 21 次,下载 171 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

shopify-admin-api 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
shopify-admin-api

Shopify admin API 搜索 · 本页

48919接触敏感数据未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Shopify Admin API

Overview

The Shopify Admin API gives apps full access to a merchant's store data — products, variants, orders, customers, inventory, metafields, and more. It is available in both GraphQL (recommended) and REST flavors, with GraphQL offering precise field selection, bulk operations, and better rate limiting via the calculated cost system. Use the @shopify/shopify-api Node.js library or direct HTTP calls with an Admin API access token.

When to Use This Skill

  • When reading or writing product catalog data (titles, variants, pricing, images, inventory)
  • When fulfilling or updating orders programmatically from an external system
  • When syncing customer records between Shopify and a CRM or ERP
  • When running bulk data exports or imports using Bulk Operations
  • When building an internal tool that needs merchant store access via a Custom App token
  • When automating inventory adjustments from a warehouse management system

Core Instructions

  1. Obtain an Admin API access token For a custom app (single store), create it in Admin → Settings → Apps and Sales Channels → Develop apps. For a public/partner app, the token is obtained after OAuth (see @shopify-app-development). #.env SHOPIFY_ADMIN_API_TOKEN=shpat_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx SHOPIFY_SHOP=mystore.myshopify.com SHOPIFY_API_VERSION=2025-01
  2. Initialize the Admin API client ` // lib/shopify-admin.ts import {shopifyApi, ApiVersion, Session} from "@shopify/shopify-api"; import "@shopify/shopify-api/adapters/node"; const shopify = shopifyApi({apiKey: process.env.SHOPIFY_API_KEY!, apiSecretKey: process.env.SHOPIFY_API_SECRET!, scopes: ["read_products", "write_products", "read_orders", "write_orders"], hostName: process.env.SHOPIFY_APP_URL!, apiVersion: ApiVersion.January25, isEmbeddedApp: false, // true for merchant-facing embedded apps}); // For custom apps with a static token const session = new Session({id: offline_${process.env.SHOPIFY_SHOP}, shop: process.env.SHOPIFY_SHOP!, state: "", isOnline: false, accessToken: process.env.SHOPIFY_ADMIN_API_TOKEN,}); export const adminClient = new shopify.clients.Graphql({session}); export const restClient = new shopify.clients.Rest({session}); `
  3. Query products with GraphQL ` // Fetch products with variants and inventory export async function getProducts(cursor?: string) {const response = await adminClient.request( query GetProducts($cursor: String) {products(first: 50, after: $cursor) {pageInfo {hasNextPage endCursor} edges {node {id title status variants(first: 100) {edges {node {id sku price inventoryQuantity inventoryItem {id}}}}}}}} , {variables: {cursor}}); return response.data.products;} // Update a product's price via mutation export async function updateVariantPrice(variantId: string, price: string) {const response = await adminClient.request( mutation UpdateVariantPrice($id: ID!, $price: Money!) {productVariantUpdate(input: {id: $id, price: $price}) {productVariant {id price} userErrors {field message}}} , {variables: {id: variantId, price}}); const {userErrors} = response.data.productVariantUpdate; if (userErrors.length > 0) throw new Error(userErrors[0].message); return response.data.productVariantUpdate.productVariant;} `
  4. Fetch and update orders ` // Query unfulfilled orders export async function getUnfulfilledOrders() {const response = await adminClient.request( query {orders(first: 50, query: "fulfillment_status:unfulfilled financial_status:paid") {edges {node {id name email createdAt lineItems(first: 50) {edges {node {title quantity variant {id sku}}}} shippingAddress {firstName lastName address1 city province zip country}}}}} ); return response.data.orders.edges.map(({node}: any) => node);} // Mark an order as fulfilled export async function fulfillOrder(orderId: string, trackingNumber: string, trackingCompany: string) {// First get fulfillment order ID const orderResponse = await adminClient.request( query GetFulfillmentOrders($id: ID!) {order(id: $id) {fulfillmentOrders(first: 5) {edges {node {id status lineItems(first: 20) {edges {node {id remainingQuantity}}}}}}}} , {variables: {id: orderId}}); const fulfillmentOrder = orderResponse.data.order.fulfillmentOrders.edges[0]?.node; if (!fulfillmentOrder) throw new Error("No fulfillment order found"); const response = await adminClient.request( mutation FulfillOrder($fulfillment: FulfillmentInput!) {fulfillmentCreate(fulfillment: $fulfillment) {fulfillment {id status} userErrors {field message}}} , {variables: {fulfillment: {lineItemsByFulfillmentOrder: [{fulfillmentOrderId: fulfillmentOrder.id}], trackingInfo: {number: trackingNumber, company: trackingCompany}, notifyCustomer: true,},},}); return response.data.fulfillmentCreate;} `
  5. Run Bulk Operations for large datasets For exporting thousands of products or orders, use Bulk Operations (GraphQL only) — they run asynchronously and return a JSONL file URL: ` // Start a bulk operation export async function startBulkProductExport() {const response = await adminClient.request( mutation {bulkOperationRunQuery(query: """ {products {edges {node {id title status variants {edges {node {id sku price inventoryQuantity}}}}}}} """) {bulkOperation {id status} userErrors {field message}}} ); return response.data.bulkOperationRunQuery.bulkOperation;} // Poll for completion and download URL export async function getBulkOperationStatus() {const response = await adminClient.request( query {currentBulkOperation {id status errorCode objectCount url # JSONL download URL — available when status is COMPLETED}} ); return response.data.currentBulkOperation;} `

Examples

Customer search and update via REST API

// REST is still valid for simple lookups where GraphQL overhead isn't worth it
export async function searchCustomers(email: string) {
  const response = await restClient.get({
    path: "customers/search",
    query: { query: `email:${email}` },
  });
  return response.body.customers;
}

export async function tagCustomer(customerId: number, tags: string[]) {
  const response = await restClient.put({
    path: `customers/${customerId}`,
    data: { customer: { id: customerId, tags: tags.join(",") } },
  });
  return response.body.customer;
}

Inventory adjustment

export async function adjustInventory(inventoryItemId: string, locationId: string, delta: number) {
  const response = await adminClient.request(`
    mutation AdjustInventory($input: InventoryAdjustQuantitiesInput!) {
      inventoryAdjustQuantities(input: $input) {
        inventoryAdjustmentGroup {
          changes {
            name
            delta
            item { id }
            location { name }
          }
        }
        userErrors { field message }
      }
    }
  `, {
    variables: {
      input: {
        name: "available",
        reason: "correction",
        changes: [
          {
            inventoryItemId,
            locationId,
            delta,
          },
        ],
      },
    },
  });
  return response.data.inventoryAdjustQuantities;
}

Best Practices

  • Prefer GraphQL over REST — GraphQL has a cost-based rate limit (1000 cost units/second) that's more forgiving than REST's 40 requests/second; it also avoids over-fetching
  • Use Bulk Operations for exports above 250 records — never page through thousands of records manually; Bulk Operations handle up to millions of records in a single async job
  • Always handle userErrors on mutations — a 200 HTTP response does not mean success; check userErrors array before treating a mutation as successful
  • Use gid://shopify/Product/123 format for IDs — Admin API GraphQL uses global IDs; never send numeric IDs without the GID prefix
  • Implement exponential backoff — respect Retry-After headers and implement backoff on 429 and 503 responses
  • Cache immutable product data — product titles and handles rarely change; cache them with a reasonable TTL to reduce API calls
  • Scope to minimum required permissions — requesting fewer scopes reduces merchant trust friction at install time

Common Pitfalls

ProblemSolution
Cost exceeds bucket size GraphQL errorReduce the first: argument on connections (use 50 instead of 250) or restructure the query to avoid deeply nested connections
Numeric vs GID ID format mismatchAlways convert REST numeric IDs to GID format: gid://shopify/Product/${numericId}
Bulk operation URL returns 403The JSONL URL is a time-limited signed S3 URL — download it immediately after polling COMPLETED status
Order fulfillment fails with FULFILLMENT_ORDER_NOT_FOUNDOrders must be fulfilled via Fulfillment Orders API (not legacy Fulfillments API) since API version 2022-07
Webhook events trigger duplicate processingUse the admin_graphql_api_id in webhook payloads and implement idempotency keying
Customer update clears existing tagsWhen updating tags, always fetch current tags first and append — the API replaces, not merges

Related Skills

  • @shopify-app-development
  • @shopify-webhooks
  • @shopify-metafields
  • @shopify-storefront-api
  • @bulk-data-operations

平台分布

Codex

33.32%
按下载量换算57

Claude

29.03%
按下载量换算50

Cursor

19.39%
按下载量换算33

Gemini CLI

10.24%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills