安装命令
npx skills add https://github.com/agentera/agently-skills --skill agently-playbook🇨🇳中文介绍
Agently Playbook
此技能是 Agently 工作的顶层场景路由入口点。当问题始于业务目标、产品行为或系统设计，而非某个具体 API 时使用它。它有助于选择正确的 Agently 能力路径、正确的技能组合以及正确的升级顺序。它本身不替代实现技能。
前提条件：Agently >= 4.0.8.5。
适用范围
在以下情况使用此技能：
- 决定问题应保持为单个请求还是应变为一个工作流
- 决定设计应使用模型请求、多智能体模式还是 TriggerFlow
- 决定核心问题是请求质量、输出控制、专家协调、复杂规划还是工作流编排
- 决定何时添加工具、MCP、检索、记忆、提示配置或 FastAPI 暴露
- 决定何时应使用 TriggerFlow 进行并发管理、长时间运行的控制流，或混合同步和异步任务编排（即使没有模型调用）
- 决定哪些部分属于 Agently，哪些部分属于业务逻辑
- 为真实的业务场景选择实现顺序
不要在以下情况使用此技能：
- 直接的 API 级别实现细节
- 以特定供应商的配置作为主要问题
- 以直接的 TriggerFlow 或响应解析机制作为主要问题
工作流程
- 从 references/scenario-router.md 开始，对业务需求进行分类。
- 阅读 references/escalation-ladder.md 以选择最窄的可行解决方案和正确的升级路径。
- 当请求始于现实的产品或运营场景而非技术形态时，阅读 references/real-world-scenarios.md。
- 当需求类似于标准生产场景时，阅读 references/common-solution-recipes.md。
- 阅读 以选择确切的实现技能或技能组合。
🇺🇸English
Agently Playbook
This skill is the top-level scenario-routing entry point for Agently work. Use it when the problem starts from business goals, product behavior, or system design rather than one specific API. It helps choose the right Agently capability path, the right skill combination, and the right escalation order. It does not replace the implementation skills themselves.
Prerequisite: Agently >= 4.0.8.5.
Scope
Use this skill for:
- deciding whether the problem should stay one request or become a workflow
- deciding whether the design should use model requests, multi-agent patterns, or TriggerFlow
- deciding whether the core problem is request quality, output control, specialist coordination, complex planning, or workflow orchestration
- deciding when to add tools, MCP, retrieval, memory, prompt config, or FastAPI exposure
- deciding when TriggerFlow should be used for concurrency management, long-running control flow, or mixed sync-and-async task orchestration even without model calls
- deciding which parts belong to Agently and which parts belong to business logic
- choosing an implementation order for real business scenarios
Do not use this skill for:
- direct API-level implementation details
- provider-specific configuration as the main problem
- direct TriggerFlow or response-parsing mechanics as the main problem
Workflow
- Start with references/scenario-router.md to classify the business requirement.
- Read references/escalation-ladder.md to choose the narrowest viable solution and the correct upgrade path.
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者，精准高效
