Loading...
Loading...
Found 4 Skills
Use when the user needs conversation continuity, memo, or restore-after-restart behavior for a request family, including session ids, chat history, request-side memory boundaries, and session-backed continuity.
Use when the user wants to reuse one model result, read text/data/meta without re-requesting, or stream partial updates, including `get_response()`, async getters, `delta`, `instant`, and `specific`.
Use when the user wants tool use, MCP access, HTTP or streaming API exposure, auto-function helpers, or wait-for-key behavior through Agently-native extension surfaces rather than custom wrappers first.
Use when the user wants to build, initialize, validate, optimize, or refactor a model-powered assistant, internal tool, automation, evaluator, or workflow from a business scenario or common problem statement, including project-structure refactors or starter skeletons that may separate model setup, prompt config, and orchestration, even if the request also mentions a UI, app shell, or local model service such as Ollama, and it is still unclear whether the solution should stay a single request, add supporting capabilities, or become orchestration. The user does not need to mention Agently explicitly.