Agent skill

Output Meta Project Context

by growthxai in growthxai/output

Comprehensive guide to Output.ai Framework for building durable, LLM-powered workflows orchestrated by Temporal.

Apache-2.0Auto-check passed

Install Output Meta Project Context

skills CLI
$ npx skills add growthxai/output --skill output-meta-project-context -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install growthxai/output output-meta-project-context --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
output-meta-project-context
GitHub stars
442
Token cost
~4.5k tokens
SKILL.md length
1,072 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
Apache-2.0

At a glance

Comprehensive guide to Output.ai Framework for building durable, LLM-powered workflows orchestrated by Temporal.

  • Works in 4 steps: Get the workflow ID from error output → Run npx output workflow debug --json → Look for: failed step name, error… → …
  • SKILL.md covers What is Output.ai?, Core Philosophy, Component Taxonomy and Project Structure, plus 7 more sections
  • Calls npx and docker; needs API_KEY

What it does

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.

Example prompts

  • “/output-meta-project-context”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Read

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Get the workflow ID from error output
  2. Run npx output workflow debug --json
  3. Look for: failed step name, error message, input that caused failure
  4. Check if issue is determinism, schema validation, or external API

What it can do on your machine

Read from SKILL.md and the folder at commit 99ee298. 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

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    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.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

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.

SKILL.md

The full file from growthxai/output at commit 99ee298, republished under its Apache-2.0 licence (© growthxai). 1,072 words, ~4,496 tokens.

Download SKILL.mdSave it as .claude/skills/output-meta-project-context/SKILL.md (or your agent's skills folder).
name
output-meta-project-context
description
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.
allowed-tools
Read

Output.ai Framework - Complete Project Context

What is Output.ai?

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.

Core Philosophy

Separation of orchestration from I/O:

  • Workflows orchestrate execution (must be deterministic - no I/O)
  • Steps/Evaluators handle all I/O operations (HTTP, LLM, database calls)

This separation enables automatic retries, resumption, and debugging.

Component Taxonomy

ComponentPurposeKey Rule
WorkflowOrchestrates step executionMust 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
StepHandles all I/O operationsWhere HTTP, LLM, DB calls happen
EvaluatorQuality assessmentReturns confidence-scored results for validation loops
ScenarioTest input dataJSON files matching workflow's inputSchema
PromptLLM templatesLiquid.js templating with YAML frontmatter config
Eval TestOffline quality testingDataset-driven verification with verify() from @outputai/evals

Project Structure

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.ts

Code Reuse Rules

Shared directory (src/shared/):

  • shared/clients/ - API clients using @outputai/http for external services
  • shared/utils/ - Helper functions and utilities

Allowed imports:

  • Workflows/steps can import from ../../shared/clients/*.js and ../../shared/utils/*.js
  • Workflows/steps can import from local files (./types.js, ./utils.js)
  • Workflows can import another workflow's default export (../other_workflow/workflow.js) and call it as a function (child workflow)

Forbidden:

  • Importing from sibling workflow folders (../other_workflow/steps.js)
  • Steps importing other steps (activity isolation requirement)

Critical Rules

RuleCorrectIncorrect
Zod importimport { z } from '@outputai/core'import { z } from 'zod'
HTTP clientimport { createKyClient } from '@outputai/http'import axios from 'axios'
HTTP bodiesRead with .json()/.text() or cancel unused non-HEAD bodiesRead only response.url/status and leave body open
Cost trackingaddRequestCost in an afterResponse hook for paid APIsCost left untracked, or tracked only at call sites
Credentialsimport { credentials } from '@outputai/core/credentials'process.env.SECRET
LLM callsimport { generateText, aiSdk } from '@outputai/llm'Direct provider SDK
ES importsimport { fn } from './file.js'import { fn } from './file'
Workflow I/OCall steps for any I/ODirect fetch/http in workflow

Determinism violations (never in workflows):

  • Date.now(), new Date()
  • Math.random(), crypto.randomUUID()
  • Direct HTTP/fetch calls
  • File system operations
  • Environment variable reads

Available Tools Inventory

Agents
AgentPurpose
workflow-plannerDesigns workflow architecture, creates implementation blueprints
workflow-debuggerAnalyzes workflow execution traces, identifies issues
workflow-qualityReviews code quality, validates implementations
workflow-prompt-writerCreates and optimizes LLM prompt templates
workflow-context-fetcherGathers documentation and existing patterns
Skills
Workflow Authoring
SkillPurpose
output-plan-workflowPlan workflow architecture - ALWAYS FIRST, creates implementation blueprint
output-build-workflowBuild/implement workflows from a plan, or for modifications
output-debug-workflowDebug workflow issues when workflows fail or behave unexpectedly
output-migrateUpgrade a project between Output framework versions
Workflow Operations
SkillPurpose
output-workflow-runSynchronous workflow execution (waits for result)
output-workflow-startAsynchronous workflow execution (returns ID)
output-workflow-listList available workflows
output-workflow-statusCheck async workflow status
output-workflow-resultGet async workflow result
output-workflow-resetRerun a workflow from after a completed step
Monitoring & Debugging
SkillPurpose
output-workflow-stopStop running workflow
output-workflow-traceTrace workflow execution
output-workflow-trace-fileRender a local trace file as readable markdown
output-workflow-runs-listList workflow run history
output-dev-workflow-costCalculate cost of a workflow run
output-services-checkVerify Output services status
Error Diagnosis
SkillCatches
output-error-zod-importWrong zod import source
output-error-nondeterminismDate.now, Math.random in workflows
output-error-try-catchWorkflow try/catch patterns and typed step-error checks
output-error-missing-schemasIncomplete Zod schema exports
output-error-direct-ioI/O operations in workflow files
output-error-http-clientUsing axios instead of @outputai/http
Meta/Lifecycle
SkillPurpose
output-meta-pre-flightPre-operation validation checks
output-meta-post-flightPost-operation verification
output-meta-project-contextLoad full project context (this skill)
Development
SkillPurpose
output-dev-folder-structureProject and workflow directory layout
output-dev-code-styleCode style conventions for workflow projects
output-dev-workflow-functionWriting deterministic workflow files
output-dev-step-functionWriting step functions for I/O
output-dev-agent-classBuild multi-step tool-loop agents with the Agent class
output-dev-llm-streamingStream LLM progress with Temporal-safe error handling
output-dev-types-fileZod schema definitions
output-dev-evaluator-functionQuality assessment functions
output-dev-eval-testingOffline eval tests with @outputai/evals
output-dev-prompt-fileLLM prompt templates with Liquid.js
output-dev-model-selectionPick a current LLM model via the AI Gateway listing
output-dev-upgrade-prompt-modelsBulk-upgrade model: fields across .prompt files
output-dev-scenario-fileTest input JSON files
output-dev-http-client-createShared HTTP API client patterns
output-dev-cost-hooksSubscribe to cost events (cost:http:request, llm:generation:metering) for observability
output-dev-skill-fileAuthor .md skill files for the framework's lazy-loaded instructions
output-dev-create-skeletonGenerate workflow skeleton
Show full SKILL.md (391 more words)Show less
Evals
SkillPurpose
output-eval-error-analysisReview traces to identify failure modes before building evaluators
output-eval-dataset-designDesign diverse eval datasets via dimension-based variation
output-eval-judge-promptDesign effective LLM judge .prompt files
output-eval-validate-judgeValidate LLM judges against human labels (TPR/TNR)
output-eval-auditAudit an existing eval suite for trustworthiness
Credentials
SkillPurpose
output-dev-credentialsFull credentials system reference (API, scopes, merging, custom providers)
output-credentials-initInitialize encrypted credentials files for the first time
output-credentials-editView and edit credential values with show/get/set/edit commands
output-credentials-env-varsWire credentials to env vars using the credential: convention

CLI Quick Reference

bash
# 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

Naming Conventions

ElementConventionExample
Workflow foldersnake_casefact_checker/
Workflow namesnake_casename: 'fact_checker'
Step functionscamelCasefetchArticle(), analyzeContent()
Schema namesPascalCaseInputSchema, ArticleData
Prompt filessnake_case@version.promptanalyze_claim@v1.prompt
Scenario filessnake_case.jsonhappy_path.json

Common Patterns

Workflow Pattern
typescript
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.

Step Pattern
typescript
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.

HTTP Client Pattern (Shared)

Clients live in src/shared/clients/ and are shared across all workflows.

typescript
// 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.

Evaluator Pattern

Evaluators return confidence-scored results. Three result types available:

typescript
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.

Prompt File Pattern

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:

typescript
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.


Practical Tips

Docker & Services
  • Restart worker after adding workflows: docker restart <project>-worker-1
  • View worker logs: docker logs -f output-worker-1
  • Check services: Use output-services-check skill
Payload Limits
  • Temporal: ~2MB per workflow input/output
  • gRPC: ~4MB maximum
  • For larger data, use file storage and pass references
Debugging Workflow Failures
  1. Get the workflow ID from error output
  2. Run npx output workflow debug <id> --json
  3. Look for: failed step name, error message, input that caused failure
  4. Check if issue is determinism, schema validation, or external API

© 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

Files

Just SKILL.md in coding_assistants/claude/plugins/outputai/skills/output-meta-project-context of growthxai/output.

Open the folder on GitHubat commit 99ee298

Compare with similar skills

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.

Output Meta Project Context compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Output Meta Project Context this skillgrowthxai/output442—~4.5kAutomated safety check: PassApache-2.0
Durable Test Collateralasgeirtj/system_prompts_leaks69k—~687Automated safety check: PassCC0-1.0
Durable Objectscloudflare/skills3k2 repos~1.5kAutomated safety check: PassApache-2.0
Golem Configure Durability Effectgolemcloud/golem1.5k—~1.6kAutomated safety check: PassCustom licence
AWS Lambda Durable Functionsaws/agent-toolkit-for-aws2.8k—~2.3kAutomated safety check: PassApache-2.0
Durable AgentsLeoYeAI/openclaw-master-skills2.2k—~5kAutomated safety check: PassMIT

Similar skills

  • 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.

    69k GitHub stars~687 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Durable Objects

    cloudflare/skills

    Official

    Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.

    3k GitHub starsUsed in 2 repos~1.5k tokens
    Backend & APIsAuto-check passed
  • Choosing durable or ephemeral agent modes and writing custom durable functions in an Effect-based Golem project.

    1.5k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • AWS Lambda Durable Functions

    aws/agent-toolkit-for-aws

    Official

    Builds resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions.

    2.8k GitHub stars~2.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Durable Agents

    LeoYeAI/openclaw-master-skills

    Build autonomous multi-agent pipelines with Mastra (agents only) and Trigger.dev (all workflows and tasks).

    2.2k GitHub stars~5k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed
  • Journey Durable

    butterbase-ai/butterbase-skills

    Use as the durable-objects build stage of the Butterbase journey.

    534 GitHub stars~526 tokensUpdated 5 days ago
    Auto-check passed

More from growthxai/output

All 50 skills in this repo
  • Output Build Workflow

    growthxai/output

    Implement an Output SDK workflow from a plan document. An agent skill from growthxai/output.

    442 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Output Credentials Edit

    growthxai/output

    View, edit, and set encrypted credentials in an Output.ai project.

    442 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes
  • Wire encrypted credentials to environment variables using the credential: convention.

    442 GitHub stars~930 tokensUpdated yesterday
    Auto-check: notes
  • Output Credentials Init

    growthxai/output

    Initialize encrypted credentials for an Output.ai project. An agent skill from growthxai/output.

    442 GitHub stars~803 tokensUpdated yesterday
    Auto-check: notes
  • Output Debug Workflow

    growthxai/output

    Debug Output SDK workflow issues. An agent skill from growthxai/output.

    442 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • Output Dev Agent Class

    growthxai/output

    Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents.

    442 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

Questions about Output Meta Project Context

What does Output Meta Project Context do?

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.

How do I install Output Meta Project Context in Claude Code?

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.

How do I install Output Meta Project Context in Codex?

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.

Can I use Output Meta Project Context 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-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.

What does Output Meta Project Context need to run?

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.

Does Output Meta Project Context access the network?

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.

Is Output Meta Project Context 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 Meta Project Context use?

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.

How many tokens does Output Meta Project Context use?

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.

What are the alternatives to Output Meta Project Context?

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.

Who maintains Output Meta Project Context?

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.