Durable Test Collateral
asgeirtj/system_prompts_leaks
Load the body before the first implementation edit for a bug fix or behavior change, or when the user or governing specification makes reusable tests a deliverable.
Comprehensive guide to Output.ai Framework for building durable, LLM-powered workflows orchestrated by Temporal.
$ npx skills add growthxai/output --skill output-meta-project-context -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install growthxai/output output-meta-project-context --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context .claude/skills/output-meta-project-context && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "output-meta-project-context" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context into .claude/skills/output-meta-project-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-meta-project-context", 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.
$skill-installer install https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-meta-project-contextType 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.
$ npx skills add growthxai/output --skill output-meta-project-context -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install growthxai/output output-meta-project-context --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .agents/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context .agents/skills/output-meta-project-context && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "output-meta-project-context" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context into .agents/skills/output-meta-project-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-meta-project-context", 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.
$ npx skills add growthxai/output --skill output-meta-project-context -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install growthxai/output output-meta-project-context --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context .cursor/skills/output-meta-project-context && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "output-meta-project-context" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context into .cursor/skills/output-meta-project-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-meta-project-context", 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.
$ gemini skills install https://github.com/growthxai/output.git --path coding_assistants/claude/plugins/outputai/skills/output-meta-project-context--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add growthxai/output --skill output-meta-project-context -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install growthxai/output output-meta-project-context --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context .gemini/skills/output-meta-project-context && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "output-meta-project-context" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context into .gemini/skills/output-meta-project-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-meta-project-context", 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.
$ gh skill install growthxai/output output-meta-project-contextInstalls 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).
$ npx skills add growthxai/output --skill output-meta-project-context -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .github/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context .github/skills/output-meta-project-context && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "output-meta-project-context" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context into .github/skills/output-meta-project-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-meta-project-context", 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.
$ npx skills add growthxai/output --skill output-meta-project-context -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install growthxai/output output-meta-project-context --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context .opencode/skills/output-meta-project-context && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "output-meta-project-context" agent skill from https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-meta-project-context into .opencode/skills/output-meta-project-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "output-meta-project-context", 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.
output-meta-project-contextComprehensive guide to Output.ai Framework for building durable, LLM-powered workflows orchestrated by Temporal.
Output Meta Project Context is an agent skill from growthxai/output. Comprehensive guide to Output.ai Framework for building durable, LLM-powered workflows orchestrated by Temporal. Covers project structure, workflow patterns, steps, LLM integration, HTTP clients, CLI commands, and the full inventory of available agents and skills.
Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 99ee298. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npxdockerFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx and docker, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Output Meta Project Context loads about 4.5k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 1,072 words of instructions outside code blocks.
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.
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.
The full file from growthxai/output at commit 99ee298, republished under its Apache-2.0 licence (© growthxai). 1,072 words, ~4,496 tokens.
.claude/skills/output-meta-project-context/SKILL.md (or your agent's skills folder).Output.ai provides infrastructure for building production-grade AI workflows: fact checkers, content generators, data extractors, research assistants, and multi-step agents. Built on Temporal, it guarantees durable execution - if execution fails mid-run, it resumes from the last successful step.
Separation of orchestration from I/O:
This separation enables automatic retries, resumption, and debugging.
| Component | Purpose | Key Rule |
|---|---|---|
| Workflow | Orchestrates step execution | Must be deterministic (no I/O, no Date.now(), no Math.random()). Call other workflows as functions (await otherWorkflow( input )) to run them as child workflows; never use executeChild or startChild from @temporalio/workflow |
| Step | Handles all I/O operations | Where HTTP, LLM, DB calls happen |
| Evaluator | Quality assessment | Returns confidence-scored results for validation loops |
| Scenario | Test input data | JSON files matching workflow's inputSchema |
| Prompt | LLM templates | Liquid.js templating with YAML frontmatter config |
| Eval Test | Offline quality testing | Dataset-driven verification with verify() from @outputai/evals |
config/
├── credentials.yml.enc # Global encrypted credentials
├── credentials.key # Global decryption key (DO NOT COMMIT)
└── credentials/ # Environment-specific credentials
├── production.yml.enc
└── production.key
src/
├── shared/ # Shared code across workflows
│ ├── clients/ # API clients (e.g., jina.ts, stripe.ts)
│ └── utils/ # Utility functions (e.g., string.ts)
└── workflows/ # Workflow definitions
└── {workflow_name}/
├── workflow.ts # Orchestration logic (deterministic)
├── steps.ts # I/O operations
├── types.ts # Zod schemas (input, output, internal)
├── evaluators.ts # Quality checks (optional)
├── utils.ts # Local utilities (optional)
├── credentials.yml.enc # Workflow-specific credentials (optional)
├── prompts/ # LLM templates (optional)
│ └── generate@v1.prompt
├── scenarios/ # Test inputs (optional)
│ └── happy_path.json
└── tests/ # Offline eval tests (optional)
├── datasets/ # YAML test datasets
│ └── happy_path.yml
└── evals/ # Eval evaluators and workflow
├── evaluators.ts
└── workflow.tsShared directory (src/shared/):
shared/clients/ - API clients using @outputai/http for external servicesshared/utils/ - Helper functions and utilitiesAllowed imports:
../../shared/clients/*.js and ../../shared/utils/*.js./types.js, ./utils.js)../other_workflow/workflow.js) and call it as a function (child workflow)Forbidden:
../other_workflow/steps.js)| Rule | Correct | Incorrect |
|---|---|---|
| Zod import | import { z } from '@outputai/core' | import { z } from 'zod' |
| HTTP client | import { createKyClient } from '@outputai/http' | import axios from 'axios' |
| HTTP bodies | Read with .json()/.text() or cancel unused non-HEAD bodies | Read only response.url/status and leave body open |
| Cost tracking | addRequestCost in an afterResponse hook for paid APIs | Cost left untracked, or tracked only at call sites |
| Credentials | import { credentials } from '@outputai/core/credentials' | process.env.SECRET |
| LLM calls | import { generateText, aiSdk } from '@outputai/llm' | Direct provider SDK |
| ES imports | import { fn } from './file.js' | import { fn } from './file' |
| Workflow I/O | Call steps for any I/O | Direct fetch/http in workflow |
Determinism violations (never in workflows):
Date.now(), new Date()Math.random(), crypto.randomUUID()| Agent | Purpose |
|---|---|
workflow-planner | Designs workflow architecture, creates implementation blueprints |
workflow-debugger | Analyzes workflow execution traces, identifies issues |
workflow-quality | Reviews code quality, validates implementations |
workflow-prompt-writer | Creates and optimizes LLM prompt templates |
workflow-context-fetcher | Gathers documentation and existing patterns |
| Skill | Purpose |
|---|---|
output-plan-workflow | Plan workflow architecture - ALWAYS FIRST, creates implementation blueprint |
output-build-workflow | Build/implement workflows from a plan, or for modifications |
output-debug-workflow | Debug workflow issues when workflows fail or behave unexpectedly |
output-migrate | Upgrade a project between Output framework versions |
| Skill | Purpose |
|---|---|
output-workflow-run | Synchronous workflow execution (waits for result) |
output-workflow-start | Asynchronous workflow execution (returns ID) |
output-workflow-list | List available workflows |
output-workflow-status | Check async workflow status |
output-workflow-result | Get async workflow result |
output-workflow-reset | Rerun a workflow from after a completed step |
| Skill | Purpose |
|---|---|
output-workflow-stop | Stop running workflow |
output-workflow-trace | Trace workflow execution |
output-workflow-trace-file | Render a local trace file as readable markdown |
output-workflow-runs-list | List workflow run history |
output-dev-workflow-cost | Calculate cost of a workflow run |
output-services-check | Verify Output services status |
| Skill | Catches |
|---|---|
output-error-zod-import | Wrong zod import source |
output-error-nondeterminism | Date.now, Math.random in workflows |
output-error-try-catch | Workflow try/catch patterns and typed step-error checks |
output-error-missing-schemas | Incomplete Zod schema exports |
output-error-direct-io | I/O operations in workflow files |
output-error-http-client | Using axios instead of @outputai/http |
| Skill | Purpose |
|---|---|
output-meta-pre-flight | Pre-operation validation checks |
output-meta-post-flight | Post-operation verification |
output-meta-project-context | Load full project context (this skill) |
| Skill | Purpose |
|---|---|
output-dev-folder-structure | Project and workflow directory layout |
output-dev-code-style | Code style conventions for workflow projects |
output-dev-workflow-function | Writing deterministic workflow files |
output-dev-step-function | Writing step functions for I/O |
output-dev-agent-class | Build multi-step tool-loop agents with the Agent class |
output-dev-llm-streaming | Stream LLM progress with Temporal-safe error handling |
output-dev-types-file | Zod schema definitions |
output-dev-evaluator-function | Quality assessment functions |
output-dev-eval-testing | Offline eval tests with @outputai/evals |
output-dev-prompt-file | LLM prompt templates with Liquid.js |
output-dev-model-selection | Pick a current LLM model via the AI Gateway listing |
output-dev-upgrade-prompt-models | Bulk-upgrade model: fields across .prompt files |
output-dev-scenario-file | Test input JSON files |
output-dev-http-client-create | Shared HTTP API client patterns |
output-dev-cost-hooks | Subscribe to cost events (cost:http:request, llm:generation:metering) for observability |
output-dev-skill-file | Author .md skill files for the framework's lazy-loaded instructions |
output-dev-create-skeleton | Generate workflow skeleton |
| Skill | Purpose |
|---|---|
output-eval-error-analysis | Review traces to identify failure modes before building evaluators |
output-eval-dataset-design | Design diverse eval datasets via dimension-based variation |
output-eval-judge-prompt | Design effective LLM judge .prompt files |
output-eval-validate-judge | Validate LLM judges against human labels (TPR/TNR) |
output-eval-audit | Audit an existing eval suite for trustworthiness |
| Skill | Purpose |
|---|---|
output-dev-credentials | Full credentials system reference (API, scopes, merging, custom providers) |
output-credentials-init | Initialize encrypted credentials files for the first time |
output-credentials-edit | View and edit credential values with show/get/set/edit commands |
output-credentials-env-vars | Wire credentials to env vars using the credential: convention |
# Development
npx output dev # Start dev environment
# List & inspect
npx output workflow list # List available workflows
# Execute
npx output workflow run <name> --input '{}' # Run synchronously (waits)
npx output workflow start <name> --input '{}' # Run async (returns ID)
npx output workflow status <id> # Check async status
npx output workflow result <id> # Get async result
# Debug
npx output workflow debug <id> # Debug failed workflow
npx output workflow debug <id> --json # Machine-readable output
# Rerun from a step (replays up to <stepName>, re-executes everything after)
npx output workflow reset <id> --step <stepName>
npx output workflow reset <id> --step <stepName> --reason "why"
# Eval Testing
npx output workflow test <name> # Run eval tests against datasets
npx output workflow test <name> --cached # Use cached output (fast)
npx output workflow test <name> --save # Run fresh and save results
npx output workflow dataset list <name> # List datasets for a workflow
npx output workflow dataset generate <name> --input '{}' # Generate dataset
# Credentials
npx output credentials init # Initialize encrypted credentials
npx output credentials edit # Edit credentials (decrypts, opens $EDITOR)
npx output credentials set <path> <value> # Set single credential value
npx output credentials show # Show decrypted credentials
npx output credentials get <path> # Get single credential value| Element | Convention | Example |
|---|---|---|
| Workflow folder | snake_case | fact_checker/ |
| Workflow name | snake_case | name: 'fact_checker' |
| Step functions | camelCase | fetchArticle(), analyzeContent() |
| Schema names | PascalCase | InputSchema, ArticleData |
| Prompt files | snake_case@version.prompt | analyze_claim@v1.prompt |
| Scenario files | snake_case.json | happy_path.json |
import { workflow, z } from '@outputai/core';
import { fetchData, processData } from './steps.js';
export const inputSchema = z.object( { url: z.string().url() } );
export const outputSchema = z.object( { result: z.string() } );
export default workflow( {
name: 'my_workflow',
description: 'Processes data from URL',
inputSchema,
outputSchema,
fn: async input => {
const data = await fetchData( input.url );
const result = await processData( data );
return { result };
}
} );See output-dev-workflow-function for comprehensive patterns.
import { step, z } from '@outputai/core';
import { createKyClient } from '@outputai/http';
export const fetchData = step(
{ name: 'fetchData', inputSchema: z.string(), outputSchema: z.any() },
async url => {
const client = createKyClient( { prefix: url } );
const response = await client.get( '' );
return response.json();
}
);See output-dev-step-function for comprehensive patterns.
Clients live in src/shared/clients/ and are shared across all workflows.
// src/shared/clients/example.ts
import { FatalError, ValidationError } from '@outputai/core';
import { createKyClient } from '@outputai/http';
import { credentials } from '@outputai/core/credentials';
const API_KEY = credentials.require( 'example.api_key' );
const client = createKyClient( {
prefix: 'https://api.example.com',
headers: { Authorization: `Bearer ${API_KEY}` },
timeout: 30000,
retry: { limit: 3, statusCodes: [ 408, 429, 500, 502, 503, 504 ] }
// If this is a paid API, add an `afterResponse` cost hook — see
// output-dev-http-client-create. Free/internal services need nothing more.
} );
export async function fetchFromExample( query: string ): Promise<ExampleResponse> {
try {
const response = await client.get( 'endpoint', { searchParams: { q: query } } );
return response.json();
} catch ( error: unknown ) {
const err = error as { status?: number; message?: string };
if ( err.status === 401 || err.status === 403 ) {
throw new FatalError( `Auth failed: ${err.message}` );
}
throw new ValidationError( `Request failed: ${err.message}` );
}
}Error type guidelines:
FatalError: 401, 403, 404 (won't succeed on retry)ValidationError: 429, 5xx (may succeed on retry)See output-dev-http-client-create for comprehensive patterns, and output-dev-cost-hooks for forwarding cost events to your own observability system.
Evaluators return confidence-scored results. Three result types available:
import { evaluator, z, EvaluationBooleanResult, EvaluationNumberResult, EvaluationStringResult } from '@outputai/core';
// Boolean evaluator - pass/fail checks
export const evaluateCompleteness = evaluator( {
name: 'evaluate_completeness',
description: 'Check if content meets minimum length',
inputSchema: z.object( { content: z.string(), minLength: z.number() } ),
fn: async ( { content, minLength } ) => {
return new EvaluationBooleanResult( {
value: content.length >= minLength,
confidence: 1.0,
reasoning: `Content has ${content.length} chars (min: ${minLength})`
} );
}
} );See output-dev-evaluator-function for comprehensive patterns.
Prompts use YAML frontmatter + Liquid.js templating. Location: src/workflows/{name}/prompts/
---
provider: anthropic
# current as of 2026-05-04 — run output-dev-model-selection for the latest
model: claude-sonnet-4-6
temperature: 0.7
maxOutputTokens: 4096
---
<system>
You are an expert content analyzer.
{% if context %}
Additional context: {{ context }}
{% endif %}
</system>
<user>
Analyze the following content:
<content>
{{ content }}
</content>
Provide {{ numberOfPoints | default: 3 }} key insights.
</user>Using in steps:
import { generateText, aiSdk } from '@outputai/llm';
import { z } from '@outputai/core';
// Structured output
const { output } = await generateText( {
prompt: 'analyze@v1',
variables: { content: 'Article text...', numberOfPoints: 5 },
output: aiSdk.Output.object( {
schema: z.object( { insights: z.array( z.string() ) } )
} )
} );
// Text output
const { result } = await generateText( {
prompt: 'summarize@v1',
variables: { content: 'Article text...' }
} );Call arguments: prompt, promptDir, variables, tools, output, toolChoice, stopWhen, abortSignal, plus streaming callbacks.
For progress callbacks inside a step, prefer generateTextWithStreaming() or Agent.generateWithStreaming(). They return complete results and reject on stream failures. If direct streamText() access is required, capture onError and throw the captured error after consuming the stream. See output-dev-llm-streaming.
Provider & model selection: the SDK supports anthropic, openai, google-vertex, amazon-bedrock, azure, and perplexity. Don't pin specific model IDs in docs — they drift. To pick a current model, run output-dev-model-selection, which queries the AI Gateway model index live.
See output-dev-prompt-file for comprehensive patterns.
docker restart <project>-worker-1docker logs -f output-worker-1output-services-check skillnpx output workflow debug <id> --json© growthxai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in coding_assistants/claude/plugins/outputai/skills/output-meta-project-context of growthxai/output.
Open the folder on GitHubat commit 99ee298
Output Meta Project Context 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Output Meta Project Context this skillgrowthxai/output | 442 | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Durable Test Collateralasgeirtj/system_prompts_leaks | 69k | — | ~687 | Automated safety check: Pass | CC0-1.0 | |
| Durable Objectscloudflare/skills | 3k | 2 repos | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Golem Configure Durability Effectgolemcloud/golem | 1.5k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| AWS Lambda Durable Functionsaws/agent-toolkit-for-aws | 2.8k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Durable AgentsLeoYeAI/openclaw-master-skills | 2.2k | — | ~5k | Automated safety check: Pass | MIT |
asgeirtj/system_prompts_leaks
Load the body before the first implementation edit for a bug fix or behavior change, or when the user or governing specification makes reusable tests a deliverable.
cloudflare/skills
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
golemcloud/golem
Choosing durable or ephemeral agent modes and writing custom durable functions in an Effect-based Golem project.
aws/agent-toolkit-for-aws
Builds resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions.
LeoYeAI/openclaw-master-skills
Build autonomous multi-agent pipelines with Mastra (agents only) and Trigger.dev (all workflows and tasks).
butterbase-ai/butterbase-skills
Use as the durable-objects build stage of the Butterbase journey.
growthxai/output
Implement an Output SDK workflow from a plan document. An agent skill from growthxai/output.
growthxai/output
View, edit, and set encrypted credentials in an Output.ai project.
growthxai/output
Wire encrypted credentials to environment variables using the credential: convention.
growthxai/output
Initialize encrypted credentials for an Output.ai project. An agent skill from growthxai/output.
growthxai/output
Debug Output SDK workflow issues. An agent skill from growthxai/output.
growthxai/output
Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents.
Comprehensive guide to Output.ai Framework for building durable, LLM-powered workflows orchestrated by Temporal. Output Meta Project Context is an agent skill from growthxai/output.ai Framework for building durable, LLM-powered workflows orchestrated by Temporal.
Run `npx skills add growthxai/output --skill output-meta-project-context -a claude-code`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-meta-project-context in growthxai/output) into .claude/skills/output-meta-project-context in your project. Claude Code loads it when a task matches its description.
Run `npx skills add growthxai/output --skill output-meta-project-context -a codex`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-meta-project-context in growthxai/output) into .agents/skills/output-meta-project-context in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthxai/output --skill output-meta-project-context -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-meta-project-context, .gemini/skills/output-meta-project-context, .github/skills/output-meta-project-context and .opencode/skills/output-meta-project-context in your project.
Going by SKILL.md and its folder, Output Meta Project Context needs the command-line tools its instructions call (npx and docker) and credentials named API_KEY. Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read.
SKILL.md contains no URLs. Its commands use npx and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Output Meta Project Context 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.
About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Output Meta Project Context: Durable Test Collateral (asgeirtj/system_prompts_leaks, 69k stars), Durable Objects (cloudflare/skills, 3k stars), Golem Configure Durability Effect (golemcloud/golem, 1.5k stars) and AWS Lambda Durable Functions (aws/agent-toolkit-for-aws, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
growthxai (a GitHub organization) maintains it in growthxai/output, which has 442 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 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.