Skip to content
Diagnosis · Automation

output-dev-folder-structure

Workflow folder structure conventions for Output SDK.

Connecting the steps of a workflow

Works with
ClaudeChatGPTGeminiClaude CodeCodexCursorCopilotGemini CLI
Setup
Upload one file
About a minute in Claude. One command in coding tools.
Contains
Instructions only
Text files — no scripts or programs.
Maintained
Last change 2 Oct 2026
On the repository’s main branch.

What it does

This skill documents the standard folder structure for Output SDK workflows. Following these conventions ensures consistency across the codebase and enables proper tooling support.

When your AI uses it

Use when creating new workflows, organizing workflow files, or understanding the standard project layout

You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.

What it can touch

  • No script files in its folder

    Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.

    How we know

    Listed the one file in the skill’s folder on GitHub; none is a script or program.

  • Says which tools it uses

    It declares the tools it expects to be allowed: [Read, Glob]

    How we know

    The allowed-tools field in the SKILL.md front matter.

  • No known risk pattern found

    Launch7’s automated check read all 1 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

    How we know

    Read 2026-10-05, commit 46e7530 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

  • Recently maintained

    Its repository has had changes recently.

    How we know

    Last push to growthxai/output: 2026-10-02 (3 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI

Supported. Upload it once in Claude’s settings. Works on every plan, including Free.

  1. Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.

  2. In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.

  3. Make sure code execution is switched on (Settings → Capabilities). Skills need it.

  4. Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.

How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end

More from growthxai

All from this publisher →
  • output-build-workflow

    Implement an Output SDK workflow from a plan document.

    growthxaiInstructions only
  • output-debug-workflow

    Debug Output SDK workflow issues.

    growthxaiRuns terminal commands
  • output-dev-agent-class

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

    growthxaiInstructions only
  • output-dev-code-style

    Code style conventions for Output SDK workflow projects.

    growthxaiInstructions only
  • output-dev-create-skeleton

    Generate workflow skeleton files using the Output SDK CLI.

    growthxaiRuns terminal commands