agentera/agently-model-response
legacy/v1/skills/agently-model-response/SKILL.md
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`.
$ install --global
skillsauthnpx skillsauth add agentera/agently-skills agently-model-responseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 27, 2026, 3:12 AM99.5s5 files scanned
SKILL.md
- name:
- agently-model-response
- description:
- 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`.
Agently Model Response
Use this skill when the output contract is already chosen and the remaining issue is how the response instance should be consumed or reused.
The user does not need to say get_response(). Requests to reuse one result as text, parsed data, metadata, or progressive updates should route here.
Native-First Rules
- prefer
get_response()when one request result must be consumed more than once - default to async-first response APIs in services, streaming paths, TriggerFlow steps, and any integration that may overlap work
- treat sync getters and generators as convenience wrappers for scripts, REPL use, or compatibility bridges
- use
delta,instant,specific, orallinstead of custom stream splitting logic
Anti-Patterns
- do not re-issue the same request to obtain text, data, and metadata separately
- do not build ad hoc field-level stream parsers when
instantorstreaming_parsealready fits
Read Next
references/overview.md
Related Skills
agentera/agently
tools
VerifiedTrustedCommunity
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.
16SKILL.mdUpdated Jun 9, 2026
agentera/agently-dynamic-task
data-ai
VerifiedTrustedCommunity
Use when the user needs Agently TaskDAG / Dynamic Task, model-generated or app-submitted DAG planning, TaskDAG validation, DynamicTaskResolver handlers, TaskDAGExecutor execution, or the Agently.create_dynamic_task compatibility facade. TaskDAG is the DAG foundation capability; Dynamic Task is the convenience facade over it and uses TriggerFlow as the execution substrate.
16SKILL.mdUpdated May 21, 2026
agentera/agently-runtime
tools
VerifiedTrustedCommunity
Use when the user wants Agently runtime extension capabilities: Action Runtime, built-in action packages, legacy tool compatibility, MCP access, Execution Environment lifecycle, FastAPIHelper or streaming API exposure, auto-function helpers, KeyWaiter, or optional agently-devtools observation, evaluation, and playground integration.
16SKILL.mdUpdated May 17, 2026
agentera/agently-request
development
VerifiedTrustedCommunity
Use when the user is shaping Agently request-side behavior: model setup, settings files, prompt management, structured output, response reuse, streaming consumption, session memory, embeddings, knowledge-base indexing, retrieval, or retrieval-backed answers within one request family.
16SKILL.mdUpdated May 17, 2026