agentera/agently-output-control
skills/agently-output-control/SKILL.md
Use when the user wants stable structured fields, required keys, reliable machine-readable sections, or downstream-consumable output from one model request, including prompt-config-owned output contracts, `.output(...)`, field ordering, `ensure_keys`, and structured streaming.
$ install --global
skillsauthnpx skillsauth add agentera/agently-skills agently-output-controlInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
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
VirusTotalMulti-engine malware detection
70%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 27, 2026, 3:18 AM182.1s6 files scanned
SKILL.md
- name:
- agently-output-control
- description:
- Use when the user wants stable structured fields, required keys, reliable machine-readable sections, or downstream-consumable output from one model request, including prompt-config-owned output contracts, `.output(...)`, field ordering, `ensure_keys`, and structured streaming.
Agently Output Control
Use this skill when the question is what shape the model should return and how that shape should stay reliable.
The user does not need to say .output(...) or ensure_keys. Requests for stable JSON-like fields, structured reports, or machine-readable sections should route here.
Native-First Rules
- default to async-first response consumption when structured output will be streamed, reused, or served over an async boundary
- prefer prompt-config-owned output contracts such as
.request.outputwhen the schema is stable and shared across a request family - prefer
.output(...)for machine-readable results when the schema is dynamic, exploratory, or easier to keep close to code - prefer
ensure_keyswhen required fields must be enforced - keep output schema explicit when downstream systems, workflow branches, or later model steps consume the result
Anti-Patterns
- do not handwrite JSON post-processors when
.output(...)already owns the contract - do not rebuild a stable shared schema in Python if prompt config can own it once
- do not build custom retry loops for missing keys before checking
ensure_keys - do not default to sync-only result handling when the caller is already async-capable
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