About agently-model-response
agently-model-response is a skill for choosing how to consume and reuse a response in Agently once the output contract is set. It favors native response APIs and async-first handling over repeated requests or custom stream parsing.
Key features
- 01Reuse results through get_response()
- 02Prefer async response APIs
- 03Use built-in stream modes
- 04Avoid duplicate requests
- 05Avoid custom stream parsing
Use cases
- 01Consuming one result as text and parsed data
- 02Handling responses in streaming services
- 03Reusing response metadata or progressive updates
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ agentera/ agently-skills --skill agently-model-responseAfter installing, type/agently-model-responsein Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
examples/minimal.pyoutputs/.gitkeepexpected.mdreferences/overview.mdscripts/check.pyDetails
From the project READMEAgently 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
Comments
Markdown supported