技能库智客分类：设计创意 expo-overview

Expo Overview

每一次博览会或EAS任务的出入口和路由器. 在请求、 PRD 或 spec 提及时, 首先装入此技能 —— 在写入代码和选择另一个 expo- * / eas- * 技能之前 EAS 博览会 Go,或Expo-*包件,或项目在"package.json"中具有"expo"依赖性. 在该门内,它也覆盖应用软件的规格和设计来实施(tabs, sacks, 地图, 列表, 导航, 从截图中构建), 以及诸如“执行一个移动应用程序”, “使我的应用看起来像本地的”, “添加导航”, “比较一些数据”, “升级我的SDK”, “添加博览会到我现有的本地应用”, “船到App Store” , 或者“我新到博览会,我从哪里开始”等措辞。一个完全指定的请求(SDK被绑定,库被命名,布局给定)仍然通过这里的路径——共享设置规则仍然适用. 当没有信号时不要加载:没有`expo ' 依赖的光复原生项目不是Expo工作。探测出真正的目标,向右出场* / eas- * 技能的路径,并拥有共享设置规则.

19854 安装量

官方网址：skills.sh

技能介绍

先看中文介绍；官方 description 原文单独保留，不改写 SKILL.md。

做什么

何时用

官方 description 未单独写出 Use when。按规范，代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露：启动时只加载 name 与 description（约 100 token）；任务匹配后才读入整份 SKILL.md 正文；scripts/、references/、assets/ 仅在需要时再读。本文件正文结构：`expo-overview` — router & shared rules for Expo / EAS、Start Here — read before doing anything、Skill Map (by goal)、Translating vague asks、Shared setup rules、When to skip the router hop。

文件分析

文件分析：除 SKILL.md 外，正文引用了 references/native-ios.md、references/launch-without-dev-menu.md，属于带资源的技能包，这些文件按需再读。

官方 description（原文）

Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules.

`expo-overview` — router & shared rules for Expo / EASStart Here — read before doing anythingSkill Map (by goal)Translating vague asksShared setup rulesWhen to skip the router hopSubmitting Feedback

· 许可：MIT

来源分类：skills.sh agent-skill

来源与网址

市场来源：skills.sh

GitHub 完整包

开源榜 Skill 分类

SKILL.md 与 Agent 调用

官方规范 ↗

name: expo-overview
description: Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules.
许可: MIT

发现技能客户端向 Agent 提供名称与描述目录。
匹配与调用用户指定或任务匹配后，载入 SKILL.md 指令。
按需加载按步骤读取参考文档、使用脚本与素材。

指令中引用的文件 · 2

references/native-ios.md
references/launch-without-dev-menu.md

以下路径提取自原文；文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围，保留技能包的附属文件，安装后检查客户端能否发现该技能。

该技能引用了附属文件，请从来源获取完整目录；仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理，确认其中的目标目录与客户端匹配。

把 Agent Skill「expo-overview」安装到我的项目：SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-2ee032421ac4159b-Expo-Overview.html
请存为 .cursor/skills/expo-overview/SKILL.md 或 .claude/skills/expo-overview/SKILL.md，frontmatter 的 name 与 description 保持原样，不要改写。
该技能还带 scripts/、references/、assets/ 等文件，请从 https://github.com/expo/skills 取完整目录，不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表，确认实际名称。

npx skills add 'https://github.com/expo/skills' --list

目标客户端安装范围

npx skills add 'https://github.com/expo/skills' --skill 'expo-overview'

CLI 会交互选择目标 Agent，默认安装到项目；用户级安装使用 -g。先通过查看命令核对仓库内容，再用 npx skills list 检查已安装技能。

SKILL.md 原文可复制，不会改动源文件

# `expo-overview` — router & shared rules for Expo / EAS

## Start Here — read before doing anything

**Do not guess the skill from project files alone.** Many Expo goals look similar from
the filesystem but need different skills.

1. **Confirm this is Expo or EAS work** — the request mentions Expo or EAS, or
   `package.json` has an `expo` dependency. Otherwise this skill does not apply.
   A native app using EAS for delivery qualifies without an Expo runtime.
2. **Read the user's goal** — what outcome do they want, in plain terms?
3. **Classify it** using the Skill Map below, translating casual phrasing to a goal.
4. **Confirm intent** if ambiguous ("Sounds like you want to ship to the stores — that's
   `eas-app-stores`. Right?"), then load that skill's `SKILL.md` and follow it.
5. **Trust the leaf skill** — it has its own detection logic and steps. Don't improvise.

## Skill Map (by goal)

Match the goal to a category, then the skill, then load that leaf's `SKILL.md`.

**Build the app**
- `expo-project-structure` — folder layout for a **new** Expo Router project: where screens, components, and config live (never restructure an existing app to match)
- `expo-native-ui` — screens, styling, semantic colors, native controls, SF Symbols, media, layout
- `expo-router` — navigation: file-based routes, tabs / stacks / modals / sheets, links, headers
- `expo-animation` — motion and gestures: Reanimated worklets, Gesture Handler, screen transitions, sheet and press feedback, haptics, and fixing animation that stutters on device
- `expo-ui` — native UI components via `@expo/ui`: BottomSheet, Picker, Slider, Switch, Menu, Button, FieldGroup (grouped form sections), List / ListItem, and more — real SwiftUI on iOS, Jetpack Compose on Android. The universal layer needs SDK 56+ and runs in Expo Go; the drop-in replacements (`@gorhom/bottom-sheet`, `datetimepicker`, …) and platform-specific layers also exist on SDK 55.
- `expo-design-system` — one visual source of truth: design tokens (color, spacing, typography, radius, shadow, motion), reusable component conventions, and audits for drift (hardcoded colors, spacing, fonts)
- `expo-tailwind-setup` — Tailwind / NativeWind styling
- `expo-data-fetching` — network requests, React Query / SWR, caching, offline, route loaders
- `expo-dom` — run web code or reuse a web library inside native
- `expo-web-to-native` — migrate an existing web / React app to a native iOS / Android app

> **Component selection rule:** whenever you need a UI component (list rows, bottom sheets, pickers, sliders, menus, buttons, segmented controls, toggles), **consult `expo-ui` first** to check whether `@expo/ui` has a native equivalent before reaching for a React Native built-in or a community library. Native `@expo/ui` components give the best platform fit, and on SDK 56+ the universal ones run in Expo Go with no custom build. Load `expo-ui` alongside `expo-native-ui` for any app that renders lists, detail sheets, or form controls. One exception: `@expo/ui` `List` renders native grouped rows (an iOS Settings screen), **not** a virtualized list — use `FlatList` / `FlashList` for large datasets.

**Ship & operate**
- `eas-app-stores` — build and submit iOS/Android apps (Expo and other React Native projects, plus existing native apps), TestFlight, versions, and store metadata
- `eas-hosting` — deploy the web bundle to EAS Hosting; also author Expo Router API routes (`+api.ts` handlers) and their environments / domains
- `eas-workflows` — EAS Workflow YAML and CI/CD pipelines
- `eas-simulator` — run and drive the app on a remote iOS / Android simulator with Expo Simulators (also called EAS Simulator)
- `expo-dev-client` — custom development builds
- `eas-update` — configure, publish, test, and debug compatible over-the-air updates
- `eas-update-insights` — OTA update health: crash rate, adoption, payload size
- `eas-observe` — startup / launch / TTI performance with EAS Observe

**Extend natively**
- `expo-module` — native modules and views (Swift / Kotlin) with the Expo Modules API
- `expo-brownfield` — embed Expo / React Native screens in native SwiftUI/UIKit or Android apps; isolated artifacts and integrated builds
- `expo-app-clip` — iOS App Clip target (AASA, smart app banner)

**Maintain & learn**
- `expo-upgrade` — upgrade the Expo SDK and fix dependency conflicts
- `expo-examples` — canonical, version-matched integration examples (Stripe, Clerk, Supabase, …)

### Translating vague asks

Some everyday phrasings don't obviously map to a skill name — translate before routing:

- "Make it look native" → grouped controls / settings forms = `expo-ui`; screens, styling = `expo-native-ui`; motion = `expo-animation`; navigation = `expo-router`.
- "Make the screens consistent" / "clean up the styling" / "set up a theme or design tokens" → `expo-design-system`.
- "It looks AI-generated" / "too generic, not native" → `expo-design-system` (named native-slop tells + audit), with `expo-native-ui` for the platform idioms.
- "Ship it" / "get an .ipa or .apk" / "release to the stores" / "put my Swift app on TestFlight" → `eas-app-stores` (build + submit, TestFlight, versions, store metadata).
- "I'm new / where do I start" → scaffold first (see Shared setup rules), then route by goal.

## Shared setup rules

Apply the rules that match the project and the requested task.

- **Run Expo commands through the agent CLI.** Run `npx --yes @expo/agent-cli@latest <command>`
  where you would run `npx expo <command>`, including commands shown in other skills. Run
  `npx --yes @expo/agent-cli@latest --help` before your first command. It shows two kinds of
  commands:
  - **Expo CLI commands** (the "Expo CLI" group) go to the project's `expo` unchanged and
    take the same flags.
  - **Agent CLI commands** (all other groups) exist only in the agent CLI. They read the
    project state, get the app onto a device, check the running app, and search the docs
    for the project's SDK. Prefer them to manual steps. Read a command's `--help` before its
    first use, and run `help workflow` for the order to run them in.

EAS commands (`eas build`, `eas update`, `eas submit`) stay on `eas-cli`. The agent CLI is
  experimental: if a command fails because of the CLI itself, run the underlying command
  directly. You can offer to report the failure with `--category agent-cli` (see Submitting Feedback).
- **Native app using EAS for delivery?** Route to `eas-app-stores`; its
  `references/native-ios.md` covers SwiftUI/UIKit on iOS. Keep the existing native
  project. Apply EAS auth/linking below; Expo scaffolding, SDK, and package-install
  rules do not apply to this path.
- **Starting a new Expo app?** Start one the standard way before routing to a feature skill:
  `npx --yes @expo/agent-cli@latest new <directory>` (it accepts `--template` and `--example`),
  laying out folders per `expo-project-structure`. Then classify the user's goal and route.
- **Detect the SDK version** before giving version-specific advice: run
  `npx --yes @expo/agent-cli@latest status`, or read the `expo` version in `package.json` (and
  `app.json` / `app.config.{js,ts}`). Many APIs and defaults differ by SDK.
- **Read the docs for that SDK, not `latest`.** `npx --yes @expo/agent-cli@latest docs:search <query>`
  searches local Markdown docs for the project's SDK. Otherwise use the version-pinned URL,
  e.g. `https://docs.expo.dev/versions/v56.0.0/sdk/ui/` on SDK 56 instead of
  `https://docs.expo.dev/versions/latest/sdk/ui/` — the `latest` pages track the newest
  SDK and can document APIs the project does not have yet.
- **Moving to a newer SDK is its own task** — load `expo-upgrade` instead of bumping
  versions by hand.
- **Managed vs. bare/prebuild**: the presence of committed `ios/` and `android/`
  directories means native projects exist (prebuild or bare). Config-plugin and
  native-setup steps differ — note which one the project is in.
- **Install packages with `npx --yes @expo/agent-cli@latest install <pkg>`**, not raw
  `npm`/`yarn`/`pnpm add`, so versions stay compatible with the project's SDK. It runs
  `expo install` and links the agent skills that the package ships.
- **Launching the app yourself?** When you open Expo Go or a development build to look
  at, screenshot, or drive it, skip the first-launch onboarding, the dev menu that opens
  at launch, and the floating Tools button. On SDK 58+, Expo CLI does this for launches
  it starts from a non-interactive shell. On SDK 57 and earlier, and for any URL you open
  yourself (`simctl openurl`, `adb`, a controller), follow
  `./references/launch-without-dev-menu.md`.
- **EAS auth & linking** (only needed for build/submit/update/observe/workflows): check
  login with `eas whoami`, log in with `eas login`. A project is linked when
  `extra.eas.projectId` exists in the app config; create it with `eas init` if missing.

## When to skip the router hop

- Only when the user explicitly named a specific `expo-*` / `eas-*` skill → load that
  skill directly.
- A fully-specified task (SDK version pinned, file layout given, libraries named) is
  **not** a reason to skip: the shared rules above still apply — check them, then route
  to the matching leaf skill.

## Submitting Feedback
You can voluntarily report errors, misleading or outdated information in this skill, so Expo can improve it:
```bash
npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-overview" --message "<actionable feedback>"
```
Use `--category agent-cli` for a problem with the agent CLI, and `--category evals` when an agent repeatedly fails at an Expo task. Run `feedback --help` for subjects and the data that the command sends.
Each report goes to Expo with project and environment details. Show the user the message, and send it only if the user agrees. If you cannot ask the user, do not send it. Do not include secrets or personal data.

觉得这个技能有帮助？

🚀 晒出用它做的作品

阅读排版

--- name: expo-overview description: "Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules." license: MIT --- # `expo-overview` — router & shared rules for Expo / EAS ## Start Here — read before doing anything **Do not guess the skill from project files alone.** Many Expo goals look similar from the filesystem but need different skills. 1. **Confirm this is Expo or EAS work** — the request mentions Expo or EAS, or `package.json` has an `expo` dependency. Otherwise this skill does not apply. A native app using EAS for delivery qualifies without an Expo runtime. 2. **Read the user's goal** — what outcome do they want, in plain terms? 3. **Classify it** using the Skill Map below, translating casual phrasing to a goal. 4. **Confirm intent** if ambiguous ("Sounds like you want to ship to the stores — that's `eas-app-stores`. Right?"), then load that skill's `SKILL.md` and follow it. 5. **Trust the leaf skill** — it has its own detection logic and steps. Don't improvise. ## Skill Map (by goal) Match the goal to a category, then the skill, then load that leaf's `SKILL.md`. **Build the app** - `expo-project-structure` — folder layout for a **new** Expo Router project: where screens, components, and config live (never restructure an existing app to match) - `expo-native-ui` — screens, styling, semantic colors, native controls, SF Symbols, media, layout - `expo-router` — navigation: file-based routes, tabs / stacks / modals / sheets, links, headers - `expo-animation` — motion and gestures: Reanimated worklets, Gesture Handler, screen transitions, sheet and press feedback, haptics, and fixing animation that stutters on device - `expo-ui` — native UI components via `@expo/ui`: BottomSheet, Picker, Slider, Switch, Menu, Button, FieldGroup (grouped form sections), List / ListItem, and more — real SwiftUI on iOS, Jetpack Compose on Android. The universal layer needs SDK 56+ and runs in Expo Go; the drop-in replacements (`@gorhom/bottom-sheet`, `datetimepicker`, …) and platform-specific layers also exist on SDK 55. - `expo-design-system` — one visual source of truth: design tokens (color, spacing, typography, radius, shadow, motion), reusable component conventions, and audits for drift (hardcoded colors, spacing, fonts) - `expo-tailwind-setup` — Tailwind / NativeWind styling - `expo-data-fetching` — network requests, React Query / SWR, caching, offline, route loaders - `expo-dom` — run web code or reuse a web library inside native - `expo-web-to-native` — migrate an existing web / React app to a native iOS / Android app > **Component selection rule:** whenever you need a UI component (list rows, bottom sheets, pickers, sliders, menus, buttons, segmented controls, toggles), **consult `expo-ui` first** to check whether `@expo/ui` has a native equivalent before reaching for a React Native built-in or a community library. Native `@expo/ui` components give the best platform fit, and on SDK 56+ the universal ones run in Expo Go with no custom build. Load `expo-ui` alongside `expo-native-ui` for any app that renders lists, detail sheets, or form controls. One exception: `@expo/ui` `List` renders native grouped rows (an iOS Settings screen), **not** a virtualized list — use `FlatList` / `FlashList` for large datasets. **Ship & operate** - `eas-app-stores` — build and submit iOS/Android apps (Expo and other React Native projects, plus existing native apps), TestFlight, versions, and store metadata - `eas-hosting` — deploy the web bundle to EAS Hosting; also author Expo Router API routes (`+api.ts` handlers) and their environments / domains - `eas-workflows` — EAS Workflow YAML and CI/CD pipelines - `eas-simulator` — run and drive the app on a remote iOS / Android simulator with Expo Simulators (also called EAS Simulator) - `expo-dev-client` — custom development builds - `eas-update` — configure, publish, test, and debug compatible over-the-air updates - `eas-update-insights` — OTA update health: crash rate, adoption, payload size - `eas-observe` — startup / launch / TTI performance with EAS Observe **Extend natively** - `expo-module` — native modules and views (Swift / Kotlin) with the Expo Modules API - `expo-brownfield` — embed Expo / React Native screens in native SwiftUI/UIKit or Android apps; isolated artifacts and integrated builds - `expo-app-clip` — iOS App Clip target (AASA, smart app banner) **Maintain & learn** - `expo-upgrade` — upgrade the Expo SDK and fix dependency conflicts - `expo-examples` — canonical, version-matched integration examples (Stripe, Clerk, Supabase, …) ### Translating vague asks Some everyday phrasings don't obviously map to a skill name — translate before routing: - "Make it look native" → grouped controls / settings forms = `expo-ui`; screens, styling = `expo-native-ui`; motion = `expo-animation`; navigation = `expo-router`. - "Make the screens consistent" / "clean up the styling" / "set up a theme or design tokens" → `expo-design-system`. - "It looks AI-generated" / "too generic, not native" → `expo-design-system` (named native-slop tells + audit), with `expo-native-ui` for the platform idioms. - "Ship it" / "get an .ipa or .apk" / "release to the stores" / "put my Swift app on TestFlight" → `eas-app-stores` (build + submit, TestFlight, versions, store metadata). - "I'm new / where do I start" → scaffold first (see Shared setup rules), then route by goal. ## Shared setup rules Apply the rules that match the project and the requested task. - **Run Expo commands through the agent CLI.** Run `npx --yes @expo/agent-cli@latest ` where you would run `npx expo `, including commands shown in other skills. Run `npx --yes @expo/agent-cli@latest --help` before your first command. It shows two kinds of commands: - **Expo CLI commands** (the "Expo CLI" group) go to the project's `expo` unchanged and take the same flags. - **Agent CLI commands** (all other groups) exist only in the agent CLI. They read the project state, get the app onto a device, check the running app, and search the docs for the project's SDK. Prefer them to manual steps. Read a command's `--help` before its first use, and run `help workflow` for the order to run them in. EAS commands (`eas build`, `eas update`, `eas submit`) stay on `eas-cli`. The agent CLI is experimental: if a command fails because of the CLI itself, run the underlying command directly. You can offer to report the failure with `--category agent-cli` (see Submitting Feedback). - **Native app using EAS for delivery?** Route to `eas-app-stores`; its `references/native-ios.md` covers SwiftUI/UIKit on iOS. Keep the existing native project. Apply EAS auth/linking below; Expo scaffolding, SDK, and package-install rules do not apply to this path. - **Starting a new Expo app?** Start one the standard way before routing to a feature skill: `npx --yes @expo/agent-cli@latest new ` (it accepts `--template` and `--example`), laying out folders per `expo-project-structure`. Then classify the user's goal and route. - **Detect the SDK version** before giving version-specific advice: run `npx --yes @expo/agent-cli@latest status`, or read the `expo` version in `package.json` (and `app.json` / `app.config.{js,ts}`). Many APIs and defaults differ by SDK. - **Read the docs for that SDK, not `latest`.** `npx --yes @expo/agent-cli@latest docs:search ` searches local Markdown docs for the project's SDK. Otherwise use the version-pinned URL, e.g. `https://docs.expo.dev/versions/v56.0.0/sdk/ui/` on SDK 56 instead of `https://docs.expo.dev/versions/latest/sdk/ui/` — the `latest` pages track the newest SDK and can document APIs the project does not have yet. - **Moving to a newer SDK is its own task** — load `expo-upgrade` instead of bumping versions by hand. - **Managed vs. bare/prebuild**: the presence of committed `ios/` and `android/` directories means native projects exist (prebuild or bare). Config-plugin and native-setup steps differ — note which one the project is in. - **Install packages with `npx --yes @expo/agent-cli@latest install `**, not raw `npm`/`yarn`/`pnpm add`, so versions stay compatible with the project's SDK. It runs `expo install` and links the agent skills that the package ships. - **Launching the app yourself?** When you open Expo Go or a development build to look at, screenshot, or drive it, skip the first-launch onboarding, the dev menu that opens at launch, and the floating Tools button. On SDK 58+, Expo CLI does this for launches it starts from a non-interactive shell. On SDK 57 and earlier, and for any URL you open yourself (`simctl openurl`, `adb`, a controller), follow `./references/launch-without-dev-menu.md`. - **EAS auth & linking** (only needed for build/submit/update/observe/workflows): check login with `eas whoami`, log in with `eas login`. A project is linked when `extra.eas.projectId` exists in the app config; create it with `eas init` if missing. ## When to skip the router hop - Only when the user explicitly named a specific `expo-*` / `eas-*` skill → load that skill directly. - A fully-specified task (SDK version pinned, file layout given, libraries named) is **not** a reason to skip: the shared rules above still apply — check them, then route to the matching leaf skill. ## Submitting Feedback You can voluntarily report errors, misleading or outdated information in this skill, so Expo can improve it: ```bash npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-overview" --message "" ``` Use `--category agent-cli` for a problem with the agent CLI, and `--category evals` when an agent repeatedly fails at an Expo task. Run `feedback --help` for subjects and the data that the command sends. Each report goes to Expo with project and environment details. Show the user the message, and send it only if the user agrees. If you cannot ask the user, do not send it. Do not include secrets or personal data.

Expo Overview

技能介绍

做什么

何时用

代理如何加载

文件分析

SKILL.md 与 Agent 调用

安装这个技能

相关技能

Automation Workflows

Ui Ux Pro Max

Frontend Design

N8n Workflow Automation