Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

guest-checkout客人结账

Agent Skill

guest-checkout 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

539

周安装

22

GitHub Stars

19

下载量

174
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill guest-checkout

简介

guest-checkout 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围和维护状态,注意是否会触发联网或文件读写操作。
  • 建议结合原始 README 核验具体用法和功能边界。

SKILL.md

Guest Checkout

Overview

Requiring account creation before purchase is one of the top causes of checkout abandonment — it adds friction for first-time buyers who do not yet trust your store enough to commit to a relationship. Enabling guest checkout and deferring account creation to after the purchase typically increases checkout completion by 20–35%. All major platforms support this with a single settings change.

When to Use This Skill

  • When checkout funnel analysis shows a significant drop-off at the account creation or login step
  • When setting up a new store and deciding on account requirements
  • When adding a "Buy as Guest" option to an existing checkout that currently requires login
  • When optimizing first-time buyer conversion rates

Core Instructions

Step 1: Enable guest checkout on your platform


Shopify

Guest checkout is enabled by default on Shopify. To verify or configure it:

  1. Go to Settings → Checkout → Customer accounts
  2. Choose one of:

- Accounts are optional (recommended): customers can check out as a guest or log in; Shopify shows a "Continue as guest" option - Accounts are disabled: checkout requires no account at all - Accounts are required: blocks guest checkout — avoid this unless you specifically need a members-only store

  1. Click Save

For the post-purchase account creation prompt (so guests can save their details after buying):

  1. Under Settings → Checkout → Customer accounts, enable Self-serve returns and Order status page — this lets guests view their order status without an account
  2. Shopify automatically sends a "Create an account" link in the order confirmation email when accounts are optional

WooCommerce

  1. Go to WooCommerce → Settings → Accounts & Privacy
  2. Under Guest checkout:

- Check Allow customers to place orders without an account (enables guest checkout) - Uncheck Allow customers to log into an existing account during checkout if you want to simplify the checkout form (or leave checked to offer both)

  1. Under Account creation:

- Check Allow customers to create an account during checkout — this shows an optional "Create an account" checkbox on the checkout page - Check Allow customers to create an account on the "My account" page — this lets guests create an account after ordering via the confirmation email link

  1. Click Save changes

For post-purchase account creation, WooCommerce automatically includes an account creation prompt in the order confirmation email when the above settings are enabled.

BigCommerce

  1. Go to Settings → Store Setup → Account Signup
  2. Under Customer accounts, select Optional — customers can check out as guests or create an account
  3. Enable Send account creation email — this sends a post-purchase email prompting the customer to activate an account with a single click

Alternatively, BigCommerce supports Apple ID login and Google login which let returning customers authenticate without a traditional password — lower friction than full account creation.


Custom / Headless

For headless storefronts, implement the guest checkout pattern with post-purchase account creation:

Guest order flow:

  1. Email is the only required identifier — collect it at the start of checkout
  2. Check if an account exists for that email; if yes, offer to log in or continue as guest
  3. Place the order without linking it to a user account
  4. Generate a time-limited account creation token (72 hours) and include it in the confirmation email
// POST /api/auth/check-email — check if account exists before showing login prompt
async function checkEmail(req, res) {
  const { email } = req.body;
  const exists = await db.users.findUnique({ where: { email: email.toLowerCase() } });
  res.json({ exists: !!exists });
}

// POST /api/auth/create-account-from-order — called when guest clicks "Create account" link
async function createAccountFromOrder(req, res) {
  const { token, password } = req.body;
  const record = await db.accountCreationTokens.findUnique({ where: { token } });

  if (!record || record.expiresAt < new Date()) {
    return res.status(400).json({ error: 'Link expired — request a new one from your account page' });
  }

  const user = await db.users.create({
    data: { email: record.email, passwordHash: await hashPassword(password) },
  });

  // Associate all guest orders with this email to the new account
  await db.orders.updateMany({
    where: { guestEmail: record.email, userId: null },
    data: { userId: user.id },
  });

  await db.accountCreationTokens.delete({ where: { token } });
  res.json({ success: true });
}

Order tracking without an account: Let guest customers track orders via order number + email, without requiring login:

// GET /api/orders/track?orderNumber=ORDER-12345&email=customer@example.com
async function trackGuestOrder(req, res) {
  const { orderNumber, email } = req.query;
  const order = await db.orders.findFirst({
    where: {
      orderNumber,
      OR: [{ guestEmail: email.toLowerCase() }, { user: { email: email.toLowerCase() } }],
    },
    include: { fulfillments: true },
  });
  if (!order) return res.status(404).json({ error: 'Order not found' });
  res.json({ order });
}

Step 2: Optimize the post-purchase account creation prompt

The order confirmation page is the ideal time to offer account creation — the customer is in a positive, just-purchased state and has a concrete reason to create an account (tracking their order).

Best practices for the prompt:

  • Lead with the benefit, not the action: "Track this order and check out faster next time" vs. "Create an account"
  • Make it one click: show a password field only; all other details are already known from the order
  • Include in the confirmation email: many customers miss the on-page prompt; the email gives them a 72-hour window to create the account

Email template for post-purchase account creation:

Subject: Your order #{{orderNumber}} is confirmed!

Hi {{email}},

Your order is on its way!

---
SAVE YOUR DETAILS FOR NEXT TIME
Create a free account to track your order and check out faster:
{{accountCreationUrl}}
(This link expires in 72 hours)
---

Step 3: Measure guest checkout adoption

Track these metrics in Google Analytics 4 or your analytics platform:

  • Guest checkout rate: what % of orders are placed as guest? (target: 40–60% for new customers)
  • Post-purchase account creation rate: what % of guests create accounts within 72 hours? (target: 15–25%)
  • Checkout completion rate by type: compare guest vs. account checkout completion rates

If guest checkout completion is significantly higher than account checkout completion, consider making accounts optional store-wide rather than having the login prompt appear prominently.

Best Practices

  • Require only email at checkout entry — do not ask for a password or account creation before taking payment; defer it entirely to post-purchase
  • Offer to log in, not force it — when the email has an existing account, show both "Log in" and "Continue as guest"; never block checkout
  • Send the account creation link in the confirmation email — many shoppers miss the on-page prompt
  • Link historical guest orders on account creation — when a guest creates an account, transfer all prior orders with that email to their new account
  • Expire account creation tokens — 72 hours is appropriate; long enough to read the email, short enough for security

Common Pitfalls

ProblemSolution
Shopify requiring account login at checkoutGo to Settings → Checkout → Customer accounts and set to "Accounts are optional"
WooCommerce not allowing guest checkoutEnable "Allow customers to place orders without an account" in WooCommerce → Settings → Accounts & Privacy
Guest orders inaccessible after account creationWhen creating the account, associate all orders matching the guest email to the new user ID
Account creation link in email expiredSet token expiry to 72 hours minimum; include a link to request a new one in the confirmation email
Guest checkout bypasses fraud preventionApply the same fraud scoring to guest orders as authenticated orders — Shopify Fraud Analysis and Stripe Radar both work regardless of account status

Related Skills

  • @checkout-flow-optimization
  • @cart-logic
  • @order-processing-pipeline
  • @accessibility-commerce

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.65%
按下载量换算66

Claude

31.43%
按下载量换算55

Cursor

18.75%
按下载量换算33

Gemini CLI

8.24%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills