workflows-install

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Zapier Workflows Early Access Install

Zapier Workflows 早期访问安装指引

Imperative recipe. Each step gates the next. Do not skip a step that failed.

This is the public-first EA path. It uses the Zapier SDK CLI and does not install the legacy

@zapier/zapier-sdk-code-substrate

package.

强制步骤说明：每一步都是下一步的前提，请勿跳过失败的步骤。

这是面向公众的早期访问路径，使用Zapier SDK CLI，不会安装旧版

@zapier/zapier-sdk-code-substrate

包。

Flow

流程

mermaid

flowchart TD
  probe["1. Probe environment"] --> envOk{"Node 18+, npm, git OK?"}
  envOk -->|no| stopEnv["STOP: tell user what to install"]
  envOk -->|yes| installCli["2. Install or update SDK CLI"]
  installCli --> verifyExperimental["3. Verify experimental commands"]
  verifyExperimental --> commandsOk{"Code Workflows commands visible?"}
  commandsOk -->|no| stopCli["STOP: diagnose SDK CLI install"]
  commandsOk -->|yes| checkAuth["4. Check Zapier auth"]
  checkAuth --> authOk{"JSON has data and no errors?"}
  authOk -->|no| login["4b. Ask user to run interactive login"]
  login --> checkAuth
  authOk -->|yes| checkAccess["5. Check Zapier Workflows EA access"]
  checkAccess --> accessOk{"Read-only workflow list succeeds?"}
  accessOk -->|no| stopAccess["STOP: closed beta access required"]
  accessOk -->|yes| installSkills["6. Bootstrap companion skills"]
  installSkills --> report["7. Report success and next steps"]

mermaid

flowchart TD
  probe["1. 探测环境"] --> envOk{"Node 18+, npm, git 正常？"}
  envOk -->|否| stopEnv["终止：告知用户需要安装的工具"]
  envOk -->|是| installCli["2. 安装或更新SDK CLI"]
  installCli --> verifyExperimental["3. 验证实验性命令"]
  verifyExperimental --> commandsOk{"Code Workflows命令可见？"}
  commandsOk -->|否| stopCli["终止：排查SDK CLI安装问题"]
  commandsOk -->|是| checkAuth["4. 检查Zapier身份验证"]
  checkAuth --> authOk{"JSON包含数据且无错误？"}
  authOk -->|否| login["4b. 要求用户运行交互式登录"]
  login --> checkAuth
  authOk -->|是| checkAccess["5. 检查Zapier Workflows早期访问权限"]
  checkAccess --> accessOk{"只读工作流列表请求成功？"}
  accessOk -->|否| stopAccess["终止：需要封闭测试访问权限"]
  accessOk -->|是| installSkills["6. 引导安装配套技能"]
  installSkills --> report["7. 报告成功结果及后续步骤"]

What This Installs

本次安装内容

@zapier/zapier-sdk-cli@latest

— public npm package that provides

zapier-sdk

zapier-sdk-cli

, and

zapier-sdk-experimental

. Installed globally.

Five companion skills installed through the

skills

CLI:

workflows/doctor

workflows/create

workflows/list

workflows/history

, and

workflows/modify

What this does not install:

```
@zapier/zapier-sdk-code-substrate
```
— old private CLI path. Do not install it for EA.
```
@zapier/zapier-durable
```
globally. The create skill installs or pins it inside workflow projects when needed.

@zapier/zapier-sdk-cli@latest

— 提供

zapier-sdk

、

zapier-sdk-cli

和

zapier-sdk-experimental

的公开npm包，将全局安装。

通过

skills

CLI安装的五个配套技能：

workflows/doctor

、

workflows/create

、

workflows/list

、

workflows/history

和

workflows/modify

。

本次不会安装的内容：

```
@zapier/zapier-sdk-code-substrate
```
— 旧版私有CLI路径，早期访问版本无需安装。
全局安装
```
@zapier/zapier-durable
```
。create技能会在需要时在工作流项目内部安装或固定该包。

Step 1: Probe Environment

步骤1：探测环境

Run each check. If any fails, stop and tell the user how to fix it.

bash

node --version
npm --version
git --version

Expected output:

bash

v18.0.0   # or higher
10.x.x    # npm version; any current version is fine
git version 2.x.x

Requirements:

Tool	Minimum version	Install if missing
Node	18	`brew install node` or use nvm
npm	any current version	bundled with Node
git	any	usually preinstalled on macOS; otherwise `brew install git`

If Node or npm is missing, explain that Node includes npm and the user needs a normal Node install before continuing. For macOS users, suggest either the Node LTS installer from

nodejs.org

, Homebrew (

brew install node

), or nvm if they already use it. Do not continue until

node --version

and

npm --version

work.

If git is missing, explain that git is needed only to download the companion skills from GitHub. For macOS users, suggest installing Apple Command Line Tools or Homebrew git. Do not continue until

git --version

works.

运行以下各项检查，若任何一项失败，需终止操作并告知用户修复方法。

bash

node --version
npm --version
git --version

预期输出：

bash

v18.0.0   # 或更高版本
10.x.x    # npm版本；任何当前版本均可
git version 2.x.x

要求：

工具	最低版本	缺失时的安装方式
Node	18	`brew install node` 或使用nvm
npm	任何当前版本	随Node捆绑安装
git	任意版本	macOS通常预装；否则使用 `brew install git`

若缺失Node或npm，需说明Node包含npm，用户需先完成标准Node安装再继续。对于macOS用户，建议从

nodejs.org

下载Node LTS安装包、使用Homebrew（

brew install node

），或如果已使用nvm则通过nvm安装。需等到

node --version

和

npm --version

命令可正常运行后再继续。

若缺失git，需说明git仅用于从GitHub下载配套技能。对于macOS用户，建议安装Apple命令行工具或Homebrew git。需等到

git --version

命令可正常运行后再继续。

Step 2: Install Or Update The Zapier SDK CLI

步骤2：安装或更新Zapier SDK CLI

Check for an existing binary and the latest published CLI version:

bash

which zapier-sdk
zapier-sdk --version
npm view @zapier/zapier-sdk-cli version

zapier-sdk

is missing, install the CLI globally:

bash

npm install -g @zapier/zapier-sdk-cli@latest

zapier-sdk

already exists, compare the installed version from

zapier-sdk --version

with the latest version from

npm view @zapier/zapier-sdk-cli version

. If they differ, update the CLI:

bash

npm install -g @zapier/zapier-sdk-cli@latest

After updating, rerun:

bash

zapier-sdk --version
npm view @zapier/zapier-sdk-cli version

Continue only when the installed CLI version matches the latest published

@zapier/zapier-sdk-cli

version.

Verify the binary is on PATH:

bash

which zapier-sdk
zapier-sdk --version

If global npm installs fail because of permissions, tell the user to fix their Node/npm setup before retrying. Prefer a user-owned Node install through nvm or Homebrew over

sudo npm install -g

检查现有二进制文件及最新发布的CLI版本：

bash

which zapier-sdk
zapier-sdk --version
npm view @zapier/zapier-sdk-cli version

若

zapier-sdk

不存在，全局安装CLI：

bash

npm install -g @zapier/zapier-sdk-cli@latest

若

zapier-sdk

已存在，对比

zapier-sdk --version

的已安装版本与

npm view @zapier/zapier-sdk-cli version

的最新版本。若版本不同，更新CLI：

bash

npm install -g @zapier/zapier-sdk-cli@latest

更新后，重新运行：

bash

zapier-sdk --version
npm view @zapier/zapier-sdk-cli version

仅当已安装的CLI版本与最新发布的

@zapier/zapier-sdk-cli

版本一致时，方可继续。

验证二进制文件是否在PATH中：

bash

which zapier-sdk
zapier-sdk --version

若全局npm安装因权限失败，需告知用户先修复Node/npm配置后重试。优先推荐通过nvm或Homebrew进行用户级Node安装，而非使用

sudo npm install -g

。

Step 3: Verify Code Workflows Experimental Commands

步骤3：验证Code Workflows实验性命令

bash

zapier-sdk --experimental --help
zapier-sdk --experimental create-workflow --help
zapier-sdk --experimental publish-workflow-version --help
zapier-sdk --experimental run-durable --help
zapier-sdk --experimental list-triggers --help
zapier-sdk --experimental get-workflow-run --help
zapier-sdk --experimental trigger-workflow --help
zapier-sdk --experimental list-workflow-drafts --help
zapier-sdk --experimental publish-workflow-draft --help

Expected output includes the Code Workflows command group, including commands such as:

text

create-workflow
list-workflows
run-durable
publish-workflow-version
list-workflow-runs
get-workflow-run
list-workflow-drafts
create-workflow-draft
get-workflow-draft
update-workflow-draft
publish-workflow-draft
discard-workflow-draft

The command-specific help must expose the flags the companion skills depend on:

```
create-workflow --help
```
includes
```
--private
```
.

publish-workflow-version --help

includes

--connections

--app-versions

, and

--trigger

update-workflow-draft --help

includes

--draft-revision

publish-workflow-draft --help

includes

--draft-revision

and

--enabled

run-durable --help

includes

--connections

and

--private

```
list-triggers --help
```
succeeds.
```
get-workflow-run --help
```
succeeds.
```
trigger-workflow --help
```
includes
```
--input
```
.

The equivalent binary may also work:

bash

zapier-sdk-experimental --help

If neither form exposes Code Workflows commands, stop and diagnose the SDK CLI install. Do not fall back to

@zapier/zapier-sdk-code-substrate

zapier-sdk

exists but the Code Workflows command group or required command-specific flags are missing, the user likely has an older SDK CLI. Run:

bash

npm install -g @zapier/zapier-sdk-cli@latest
zapier-sdk --experimental --help
zapier-sdk --experimental publish-workflow-version --help

Retry the command-specific help checks once after updating. Proceed only after the Code Workflows command group and required flags are visible. If the required flags are still missing after updating, stop and report the installed CLI version and latest npm version; do not install companion skills into a workspace that cannot run their documented command shapes.

bash

zapier-sdk --experimental --help
zapier-sdk --experimental create-workflow --help
zapier-sdk --experimental publish-workflow-version --help
zapier-sdk --experimental run-durable --help
zapier-sdk --experimental list-triggers --help
zapier-sdk --experimental get-workflow-run --help
zapier-sdk --experimental trigger-workflow --help
zapier-sdk --experimental list-workflow-drafts --help
zapier-sdk --experimental publish-workflow-draft --help

预期输出应包含Code Workflows命令组，例如：

text

create-workflow
list-workflows
run-durable
publish-workflow-version
list-workflow-runs
get-workflow-run
list-workflow-drafts
create-workflow-draft
get-workflow-draft
update-workflow-draft
publish-workflow-draft
discard-workflow-draft

命令的详细帮助需展示配套技能依赖的参数：

```
create-workflow --help
```
包含
```
--private
```
。

publish-workflow-version --help

包含

--connections

、

--app-versions

和

--trigger

。

update-workflow-draft --help

包含

--draft-revision

。

publish-workflow-draft --help

包含

--draft-revision

和

--enabled

。

run-durable --help

包含

--connections

和

--private

。

```
list-triggers --help
```
可成功运行。
```
get-workflow-run --help
```
可成功运行。
```
trigger-workflow --help
```
包含
```
--input
```
。

等效二进制文件也可正常运行：

bash

zapier-sdk-experimental --help

若两种方式均未展示Code Workflows命令，需终止操作并排查SDK CLI安装问题。请勿回退到

@zapier/zapier-sdk-code-substrate

。

若

zapier-sdk

存在但Code Workflows命令组或所需命令参数缺失，说明用户可能使用旧版SDK CLI。运行：

bash

npm install -g @zapier/zapier-sdk-cli@latest
zapier-sdk --experimental --help
zapier-sdk --experimental publish-workflow-version --help

更新后重新进行命令帮助检查。仅当Code Workflows命令组及所需参数可见时，方可继续。若更新后所需参数仍缺失，需终止操作并报告已安装的CLI版本和最新npm版本；请勿在无法运行文档指定命令的工作区安装配套技能。

Step 4: Authenticate To Zapier

步骤4：Zapier身份验证

Check auth state first:

bash

zapier-sdk get-profile --json

Treat auth as successful only if the JSON has a non-null

data

object with an email and the

errors

array is empty. Do not rely on exit code alone; some SDK CLI auth failures return exit code 0 with errors in the JSON body.

Expected successful output includes the user's email:

json

{
  "data": {
    "email": "user@example.com"
  },
  "errors": []
}

data

is null,

errors

is non-empty, or the error message says authentication is required, stop and ask the user to run the interactive login command in a real terminal:

bash

zapier-sdk login

This opens a browser. The CLI error text may suggest

npx zapier-sdk login

, but after the global install above the preferred command is

zapier-sdk login

. Do not run browser login inside a non-interactive shell or background process unless the user explicitly asks you to manage the interactive login. After the user finishes login, rerun

zapier-sdk get-profile --json

and inspect the JSON again.

For Zapier employees, the normal path is to log in with their Zapier work account. For external-user testing, use the account that has been allowlisted for Zapier Workflows EA.

Do not ask the user for a Zapier password, API key, npm token, or copied auth token. Authentication should happen through the browser-based

zapier-sdk login

flow unless the user explicitly says they are using client credentials for automation.

If the user wants non-interactive auth for automation, note that the CLI error message may mention

ZAPIER_CREDENTIALS

or client credential environment variables. For this EA install path, prefer browser login unless the user already has client credentials.

先检查身份验证状态：

bash

zapier-sdk get-profile --json

仅当JSON包含非空

data

对象（含邮箱）且

errors

数组为空时，方可视为身份验证成功。请勿仅依赖退出码；部分SDK CLI身份验证失败会返回退出码0，但JSON主体包含错误信息。

预期成功输出包含用户邮箱：

json

{
  "data": {
    "email": "user@example.com"
  },
  "errors": []
}

若

data

为空、

errors

非空，或错误信息提示需要身份验证，需终止操作并要求用户在真实终端中运行交互式登录命令：

bash

zapier-sdk login

该命令会打开浏览器。CLI错误信息可能建议使用

npx zapier-sdk login

，但在完成全局安装后，优先推荐使用

zapier-sdk login

。除非用户明确要求管理交互式登录，否则请勿在非交互式shell或后台进程中运行浏览器登录。用户完成登录后，重新运行

zapier-sdk get-profile --json

并再次检查JSON内容。

对于Zapier员工，通常需使用Zapier工作账户登录。对于外部测试用户，需使用已加入Zapier Workflows早期访问白名单的账户。

请勿向用户索要Zapier密码、API密钥、npm令牌或复制的身份验证令牌。除非用户明确表示使用客户端凭据进行自动化操作，否则身份验证应通过基于浏览器的

zapier-sdk login

流程完成。

若用户需要用于自动化的非交互式身份验证，需注意CLI错误信息可能提及

ZAPIER_CREDENTIALS

或客户端凭据环境变量。对于此早期访问安装路径，优先推荐浏览器登录，除非用户已拥有客户端凭据。

Step 5: Check Zapier Workflows EA Access

步骤5：检查Zapier Workflows早期访问权限

After SDK profile auth succeeds, confirm the authenticated account has Zapier Workflows EA access with a read-only Code Workflows call:

bash

zapier-sdk --experimental list-workflows --json

Expected output is JSON containing workflow data or an empty list, with no errors. This command should not create or modify cloud state.

Treat the access check as successful only if the JSON has workflow data or an empty workflow list and

errors

is empty. Do not rely on exit code alone; this command may return exit code 0 while the JSON body contains errors.

If the response says authentication is required, return to Step 4 and diagnose SDK auth.

If the response includes any of the following, treat it as a Zapier Workflows EA access failure and stop before installing companion skills:

None of the security schemes (userJwt) successfully authenticated this request

```
allowlist
```
,
```
not allowlisted
```
, or
```
not whitelisted
```

forbidden

permission

unauthorized

, or

access denied

When EA access fails, tell the user:

text

You're logged in to Zapier as <email>, and the Zapier SDK CLI is installed, but this account does not currently have Zapier Workflows EA access.

Zapier Workflows is currently only available to members of our closed beta.

To request access, fill out the beta sign-up form:

https://next-gen-zaps.zapier.app/

Submitting the form does not grant access immediately. The Zapier team will review your request and let you know once access has been granted.

After your account is allowlisted, rerun the workflows-install skill in this workspace. Reinstalling Node, npm, git, or the SDK CLI will not fix this access check.

Use the email from

zapier-sdk get-profile --json

in place of

<email>

SDK账户身份验证成功后，通过只读Code Workflows调用确认已验证账户拥有Zapier Workflows早期访问权限：

bash

zapier-sdk --experimental list-workflows --json

预期输出为包含工作流数据或空列表的JSON，且无错误信息。该命令不应创建或修改云端状态。

仅当JSON包含工作流数据或空工作流列表且

errors

为空时，方可视为权限检查成功。请勿仅依赖退出码；该命令可能返回退出码0，但JSON主体包含错误信息。

若响应提示需要身份验证，返回步骤4排查SDK身份验证问题。

若响应包含以下任意内容，视为Zapier Workflows早期访问权限失败，需在安装配套技能前终止操作：

None of the security schemes (userJwt) successfully authenticated this request

```
allowlist
```
、
```
not allowlisted
```
或
```
not whitelisted
```

forbidden

、

permission

、

unauthorized

或

access denied

当早期访问权限失败时，告知用户：

text

您已以<email>身份登录Zapier，且Zapier SDK CLI已安装，但该账户目前暂无Zapier Workflows早期访问权限。

Zapier Workflows目前仅对封闭测试成员开放。

如需申请访问权限，请填写测试版注册表单：

https://next-gen-zaps.zapier.app/

提交表单并不意味着立即获得访问权限。Zapier团队会审核您的申请，获得权限后会通知您。

账户加入白名单后，请在当前工作区重新运行workflows-install技能。重新安装Node、npm、git或SDK CLI无法解决此权限检查问题。

将

zapier-sdk get-profile --json

中的邮箱替换

<email>

。

Step 6: Bootstrap The Workflows Companion Skills

步骤6：引导安装工作流配套技能

Install the companion skills into the current workspace only after SDK auth and Zapier Workflows EA access are confirmed.

Use the public

skills.sh

install path. The

npx

command runs the

skills

CLI; the skill content comes from the public

zapier/agent-skills

GitHub repo after that repo is published.

bash

npx skills add zapier/agent-skills --skill workflows-doctor --yes
npx skills add zapier/agent-skills --skill workflows-create --yes
npx skills add zapier/agent-skills --skill workflows-list --yes
npx skills add zapier/agent-skills --skill workflows-history --yes
npx skills add zapier/agent-skills --skill workflows-modify --yes

Verify:

bash

npx skills list --json

Expected output should include the installed workflows companion skills:

workflows-doctor

workflows-create

workflows-list

workflows-history

, and

workflows-modify

If any companion skill is missing, rerun the specific

npx skills add ...

command and diagnose before proceeding.

Updates later use the standard

skills

CLI update path. If a companion skill detects SDK/skill drift, rerun

workflows-install

or run

workflows-doctor

; those are the canonical repair paths.

bash

npx skills update --project

仅在SDK身份验证和Zapier Workflows早期访问权限确认后，方可在当前工作区安装配套技能。

使用公开的

skills.sh

安装路径。

npx

命令运行

skills

CLI；技能内容来自公开的

zapier/agent-skills

GitHub仓库（需该仓库已发布）。

bash

npx skills add zapier/agent-skills --skill workflows-doctor --yes
npx skills add zapier/agent-skills --skill workflows-create --yes
npx skills add zapier/agent-skills --skill workflows-list --yes
npx skills add zapier/agent-skills --skill workflows-history --yes
npx skills add zapier/agent-skills --skill workflows-modify --yes

验证安装：

bash

npx skills list --json

预期输出应包含已安装的工作流配套技能：

workflows-doctor

、

workflows-create

、

workflows-list

、

workflows-history

和

workflows-modify

。

若任何配套技能缺失，重新运行对应的

npx skills add ...

命令并排查问题后再继续。

后续更新使用标准

skills

CLI更新路径。若配套技能检测到SDK/技能版本不一致，重新运行

workflows-install

或

workflows-doctor

；这些是标准修复路径。

bash

npx skills update --project

Step 7: Report Success

步骤7：报告成功结果

Tell the user:

Zapier SDK CLI is installed and on PATH, confirmed via
```
which zapier-sdk
```
.
Code Workflows experimental commands are available.
The authenticated Zapier account email from
```
zapier-sdk get-profile --json
```
.
Zapier Workflows EA access was confirmed with a read-only workflow listing.

Five companion workflow skills are installed:

workflows/doctor

workflows/create

workflows/list

workflows/history

, and

workflows/modify

This confirms SDK CLI install, login, Zapier Workflows EA access, and skill bootstrap. It does not yet prove that building, publishing, triggering, or running a full workflow works.

Next steps for the user:

Configure app connections at https://zapier.com/app/assets/connections before attempting to build workflows.
Reload your agent workspace so the new skills are picked up. This is required before the agent can reliably auto-discover the installed workflow skills.
Ask your agent to create a workflow, for example: "Create a Zapier workflow that takes a manual input and sends a Slack message."

告知用户：

Zapier SDK CLI已安装且在PATH中，通过
```
which zapier-sdk
```
确认。
Code Workflows实验性命令可用。
已验证的Zapier账户邮箱来自
```
zapier-sdk get-profile --json
```
。
通过只读工作流列表确认拥有Zapier Workflows早期访问权限。

已安装五个工作流配套技能：

workflows/doctor

、

workflows/create

、

workflows/list

、

workflows/history

和

workflows/modify

。

以上确认了SDK CLI安装、登录、Zapier Workflows早期访问权限及技能引导完成，但尚未验证构建、发布、触发或运行完整工作流的功能。

用户后续步骤：

在尝试构建工作流前，前往https://zapier.com/app/assets/connections配置应用连接。
重新加载代理工作区，以便识别新安装的技能。这是代理能够可靠自动发现已安装工作流技能的必要步骤。
要求代理创建工作流，例如："创建一个接收手动输入并发送Slack消息的Zapier工作流。"

Troubleshooting

故障排查

Symptom	Likely cause	Fix
`node --version` prints less than `v18`	Old Node	`brew upgrade node` or use nvm to install a current LTS
`npm install -g` fails with permissions errors	Global npm prefix is not user-writable	Use nvm or Homebrew Node; avoid `sudo npm install -g` unless the user explicitly accepts that system-level change
`zapier-sdk --experimental --help` lacks Code Workflows commands	Old CLI or wrong package installed	Install `@zapier/zapier-sdk-cli@latest` , then rerun `zapier-sdk --version` and the help command
`zapier-sdk get-profile` says not logged in	User has not authenticated the CLI	Run `zapier-sdk login` in an interactive terminal, then retry
`get-profile` succeeds but `list-workflows` returns an access, permission, allowlist, or JWT/security-scheme error	The Zapier account is authenticated but does not have Zapier Workflows EA access	Stop before installing companion skills. Tell the user Zapier Workflows is currently only available to members of our closed beta, include the authenticated email, and ask them to rerun `workflows-install` after allowlisting.
`zapier-sdk login` does not open a browser	No default browser configured, or remote/SSH session	Try `zapier-sdk login --no-browser` if supported by the installed CLI, or run from a local terminal
`zapier-sdk login` hangs in a non-interactive shell	`login` is browser-interactive; cannot run unattended	Ask the user to run it manually in an actual terminal
`npx skills add zapier/agent-skills --skill workflows-...` fails	Public skill source is unavailable, the skill has not been published yet, or network access failed	Confirm the `zapier/agent-skills` public repo and workflow skill path are available, then rerun the specific install command
Skills do not auto-invoke after install	Agent workspace has not reloaded the skills directory	Reload workspace or restart your agent

症状	可能原因	修复方法
`node --version` 输出低于 `v18`	Node版本过旧	`brew upgrade node` 或使用nvm安装当前LTS版本
`npm install -g` 因权限错误失败	全局npm前缀不可被用户写入	使用nvm或Homebrew安装Node；除非用户明确接受系统级变更，否则避免使用 `sudo npm install -g`
`zapier-sdk --experimental --help` 缺少Code Workflows命令	CLI版本过旧或安装了错误包	安装 `@zapier/zapier-sdk-cli@latest` ，然后重新运行 `zapier-sdk --version` 和帮助命令
`zapier-sdk get-profile` 提示未登录	用户未验证CLI	在交互式终端中运行 `zapier-sdk login` ，然后重试
`get-profile` 成功但 `list-workflows` 返回访问权限、白名单或JWT/安全方案错误	Zapier账户已验证但无Zapier Workflows早期访问权限	在安装配套技能前终止操作。告知用户Zapier Workflows目前仅对封闭测试成员开放，包含已验证邮箱，并要求用户加入白名单后重新运行 `workflows-install` 。
`zapier-sdk login` 无法打开浏览器	未配置默认浏览器，或处于远程/SSH会话	若已安装的CLI支持，尝试 `zapier-sdk login --no-browser` ，或在本地终端运行
`zapier-sdk login` 在非交互式shell中挂起	`login` 为浏览器交互式操作，无法无人值守运行	要求用户在真实终端中手动运行
`npx skills add zapier/agent-skills --skill workflows-...` 失败	公开技能源不可用、技能尚未发布或网络访问失败	确认 `zapier/agent-skills` 公开仓库及工作流技能路径可用，然后重新运行对应的安装命令
安装后技能无法自动调用	代理工作区未重新加载技能目录	重新加载工作区或重启代理