Install the "output-dev-agent-class" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-agent-class into .claude/skills/output-dev-agent-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-agent-class", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add growthxai/output --skill output-dev-agent-class -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "output-dev-agent-class" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-agent-class into .agents/skills/output-dev-agent-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-agent-class", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add growthxai/output --skill output-dev-agent-class -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "output-dev-agent-class" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-agent-class into .cursor/skills/output-dev-agent-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-agent-class", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add growthxai/output --skill output-dev-agent-class -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "output-dev-agent-class" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-agent-class into .gemini/skills/output-dev-agent-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-agent-class", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add growthxai/output --skill output-dev-agent-class -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "output-dev-agent-class" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-agent-class into .github/skills/output-dev-agent-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-agent-class", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add growthxai/output --skill output-dev-agent-class -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "output-dev-agent-class" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-agent-class into .opencode/skills/output-dev-agent-class/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-dev-agent-class", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
output-dev-agent-class
GitHub stars
442
Token cost
~2.6k tokens
SKILL.md length
761 words
Files
1
Skills in repo
52
Repo updated
First seen
Licence
Apache-2.0
At a glance
Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents.
Building agents with skills
SKILL.md covers Overview, When to Use This Skill, Import Pattern and Construction, plus 10 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Structured output
What it does
Output Dev Agent Class is an agent skill from growthxai/output. Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents. Use when building agents with skills, structured output, stateful conversations, or streaming callbacks.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering Structured output and tool calling and Building AI agents. The repository describes itself as: The open-source TypeScript framework for building AI workflows and agents. Designed for Claude Code describe what you want, Claude builds it, with all the best practices already… The licence is Apache-2.0.
Read from SKILL.md and the folder at commit ff9e1ab. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Read
Write
Edit
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Output Dev Agent Class loads about 2.6k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 761 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~60
When it runs· the whole SKILL.md, loaded when a task matches
~2.6k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/output-dev-agent-class/SKILL.md (or your agent's skills folder).
name
output-dev-agent-class
description
Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents. Use when building agents with skills, structured output, stateful conversations, or streaming callbacks.
allowed-tools
Read, Write, Edit
Using the Agent Class
Overview
The Agent class uses an internal AI SDK ToolLoopAgent through composition with Output prompt files and the skills system. It does not inherit from ToolLoopAgent. Use it when you need multi-step tool execution, conversation history, or a reusable agent instance. For single-shot LLM calls without tools, generateText is simpler.
When to Use This Skill
Building multi-step agents that call tools in a loop
Using skills (lazy-loaded instructions) with an agent
Creating agents with structured output via aiSdk.Output.object()
Implementing stateful conversations with messageStore
Streaming Agent progress with onChunk
Deciding between Agent and generateText
Import Pattern
typescript
import { Agent, aiSdk } from '@outputai/llm';
import type { MessageStore } from '@outputai/llm';
import { z } from '@outputai/core';
Agent comes from @outputai/llm. Use aiSdk.Output for structured output. Import z from @outputai/core (never from zod directly). MessageStore is the type for a pluggable getMessages / addMessages store; implement it yourself.
Construction
The prompt file is loaded and rendered at construction time. Variables and tools are fixed at construction. Skills and maxSteps come from the prompt file. The agent is ready to call generate(), generateWithStreaming(), or stream() immediately.
The method behaves like generate() while using streaming internally. It returns the complete response, rejects on stream errors, and automatically appends messages to the configured message store. It accepts the same messages, abortSignal, and toolChoice as generate(), plus onChunk. Prefer it over stream() in Temporal activity steps unless direct access to the stream result is required.
stream()
Use stream() when direct control over textStream or stream is required. It accepts the same messages, abortSignal, and toolChoice as generate(), plus onChunk, onEnd, and onError:
typescript
const stream = await agent.stream();
for await ( const chunk of stream.textStream ) {
process.stdout.write( chunk );
}
Like streamText, the stream result provides textStream and stream iterables, plus promise-based properties (text, usage, finishReason) that resolve on completion.
stream() appends messages to the message store in its wrapped onEnd when finishReason is not 'error'. See output-dev-llm-streaming for streaming and error-handling guidance.
Use .describe() on schema fields instead of .min()/.max() for number constraints. Anthropic does not support minimum/maximum JSON Schema constraints in tool definitions.
Show full SKILL.md (304 more words)Show less
Message Store
By default, Agent is stateless. Each generate() call starts fresh with only the initial prompt messages. Pass a messageStore to maintain history across calls:
typescript
import { Agent } from '@outputai/llm';
import type { MessageStore } from '@outputai/llm';
const messages: Parameters<MessageStore['addMessages']>[0] = [];
const messageStore: MessageStore = {
getMessages: () => messages,
addMessages: incoming => {
messages.push( ...incoming );
}
};
const chatbot = new Agent( {
prompt: 'chatbot@v1',
messageStore
} );
const r1 = await chatbot.generate( {
messages: [ { role: 'user', content: 'Hello, tell me about Output.' } ]
} );
// r1.text: "Output is an AI framework for..."
const r2 = await chatbot.generate( {
messages: [ { role: 'user', content: 'How does it handle retries?' } ]
} );
// r2 sees the full history from r1
ModelMessage is an AI SDK type available through the aiSdk namespace or as an import from ai. There is no built-in store. Implement the interface in memory for a single process, or with your database for durable history.
Using Agent in Workflow Steps
In workflow steps, construct a new Agent per invocation. Variables come from the step input:
Output Dev Agent Class next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Output Dev Agent Class compared with similar skills
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management", or needs ADK (Agent…
AI agent and LLM system engineering reference covering single-agent dev (ReAct, tool calling, plan-execute), multi-agent coordination (swarm, role decomposition, file locking), LLM security (prompt…
Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents. Output Dev Agent Class is an agent skill from growthxai/output. Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents.
When should I use Output Dev Agent Class?
Output Dev Agent Class fits situations like: building agents with skills; structured output; stateful conversations; streaming callbacks.
How do I install Output Dev Agent Class in Claude Code?
Run `npx skills add growthxai/output --skill output-dev-agent-class -a claude-code`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-dev-agent-class in growthxai/output) into .claude/skills/output-dev-agent-class in your project. Claude Code loads it when a task matches its description.
How do I install Output Dev Agent Class in Codex?
Run `npx skills add growthxai/output --skill output-dev-agent-class -a codex`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-dev-agent-class in growthxai/output) into .agents/skills/output-dev-agent-class in your project. Codex loads it when a task matches its description.
Can I use Output Dev Agent Class in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthxai/output --skill output-dev-agent-class -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/output-dev-agent-class, .gemini/skills/output-dev-agent-class, .github/skills/output-dev-agent-class and .opencode/skills/output-dev-agent-class in your project.
What does Output Dev Agent Class need to run?
SKILL.md names no scripts, command-line tools or credentials: Output Dev Agent Class is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit.
Does Output Dev Agent Class access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Output Dev Agent Class safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Output Dev Agent Class use?
Output Dev Agent Class is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Output Dev Agent Class use?
About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Output Dev Agent Class?
Skills that share tags, products or a category with Output Dev Agent Class: Google Agents CLI Adk Code (pifferologo/cloud-agents-cli, 129 stars), E2b Code Interpreter (agent-sandbox/agent-sandbox, 218 stars), Agents And Middleware (VectorSpaceLab/AREX-Skill, 330 stars) and Build Agents (vercel/vercel-plugin, 301 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Output Dev Agent Class?
growthxai (a GitHub organization) maintains it in growthxai/output, which has 442 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 8, 2026.
Source: growthxai/output on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.