Automated summary
Validates and repairs the folder and file structure of Output SDK workflows, checking naming conventions and required files after migration from the older Flow SDK.
Strengths
- Explicit side-by-side comparison of the old Flow SDK layout versus the new Output SDK layout
- Precise naming rules for folders, core files (workflow.ts, steps.ts, types.ts), .prompt files and scenario JSON files
- Ready-to-run bash validation snippets to detect missing required files and leftover artifacts
- Clear table of files to rename or delete after migration
Limitations
- Scoped to a single SDK's conventions, not a general-purpose project structure linter
- Only checks layout and naming, not whether the workflow code itself is correct
- Assumes the user supplies the correct workflow folder path
Use right after migrating a workflow to the Output SDK, or when creating a new workflow folder, to confirm the structure and names match conventions.
Don't use it on projects that aren't built on the Output SDK, or when you need to verify workflow logic rather than file layout.
Security analysis
CautionThe skill contains legitimate file validation and cleanup commands. The rm commands are narrowly targeted at known migration leftovers and do not perform destructive broad actions, exfiltration, or obfuscation, but the use of file-modifying Bash warrants caution.
- •Uses Bash commands including rm and mv to delete or rename files, though scoped to specific migration cleanup files.
- •Includes shell loops and file checks that could affect files if the workflow path variable is misconfigured.
Examples
Check the folder structure of src/workflows/analyze_document against the Output SDK conventions and tell me which required files are missing or misnamed.My workflow folder still has activities.ts and prompts.ts — remove or rename these files and make the structure match the Output SDK conventions.Create the correct Output SDK folder structure for a new workflow called generate_report, including workflow.ts, steps.ts, types.ts and a scenarios folder.name: flow-conventions-folder-structure description: Validate and fix folder structure for Output SDK workflows. Use to ensure migrated workflows follow the correct structure conventions. allowed-tools: [Bash, Read, Grep, Glob]
Output SDK Folder Structure Conventions
Overview
This skill documents the required folder structure for Output SDK workflows and helps validate/fix structure issues after migration.
When to Use This Skill
After Migration:
- Validating folder structure is correct
- Fixing structure issues
- Renaming files to match conventions
During Setup:
- Creating new workflow directories
- Understanding project organization
Folder Structure Comparison
Flow SDK (Old Structure)
src/
└── workflows/
└── example_workflow/
├── activities.ts # Activity functions
├── helpers.ts # Optional helpers
├── prompts.ts # JS prompt arrays
├── prompts.xml # XML prompts
├── readme.xml # Documentation
├── types.ts # Type definitions
└── workflow.ts # Workflow class
Output SDK (New Structure)
src/
└── workflows/
└── example_workflow/
├── workflow.ts # Workflow function (export default)
├── steps.ts # Step definitions
├── types.ts # Types + Zod schemas
├── analyzeDocument@v1.prompt # Prompt files
├── generateSummary@v1.prompt
└── scenarios/ # Test input files
├── basic_input.json
└── full_options.json
File Naming Conventions
Workflow Folder
- Use
snake_casefor folder names - Match the workflow name
# Correct
user_onboarding/
generate_report/
analyze_document/
# Wrong
userOnboarding/
GenerateReport/
analyze-document/
Core Files
| File | Naming | Purpose |
|------|--------|---------|
| workflow.ts | Exact name | Workflow definition |
| steps.ts | Exact name | All step definitions |
| types.ts | Exact name | Types and Zod schemas |
Prompt Files
Format: {descriptiveName}@{version}.prompt
# Correct
analyzeDocument@v1.prompt
generateSummary@v1.prompt
extractEntities@v2.prompt
# Wrong
analyze.prompt # Missing version
analyzeDocument.txt # Wrong extension
analyze-document@v1.md # Wrong extension
Scenario Files
Format: {descriptive_name}.json
# Correct
basic_input.json
full_options.json
edge_case_empty.json
question_ada_lovelace.json
# Wrong
test1.json # Not descriptive
BasicInput.json # Not snake_case
Required vs Optional Files
Required Files
| File | Must Exist | Purpose |
|------|------------|---------|
| workflow.ts | Yes | Workflow entry point |
| steps.ts | Yes (if steps exist) | Step definitions |
| types.ts | Yes | Schemas and types |
Optional Files/Folders
| File/Folder | Optional | Purpose |
|-------------|----------|---------|
| *.prompt | If LLM calls | Prompt templates |
| scenarios/ | Recommended | Test inputs |
| helpers.ts | If needed | Utility functions |
Files to Remove After Migration
| File | Action |
|------|--------|
| activities.ts | Rename to steps.ts or delete after conversion |
| prompts.ts | Delete after converting to .prompt files |
| prompts.xml | Delete after converting to .prompt files |
| readme.xml | Can keep for reference or delete |
Validation Commands
Check Folder Structure
WORKFLOW="src/workflows/my_workflow"
# List all files
ls -la $WORKFLOW/
# Check for required files
[ -f "$WORKFLOW/workflow.ts" ] && echo "✓ workflow.ts" || echo "✗ workflow.ts missing"
[ -f "$WORKFLOW/steps.ts" ] && echo "✓ steps.ts" || echo "✗ steps.ts missing"
[ -f "$WORKFLOW/types.ts" ] && echo "✓ types.ts" || echo "✗ types.ts missing"
# Check for leftover files
[ -f "$WORKFLOW/activities.ts" ] && echo "⚠ activities.ts should be removed" || echo "✓ No activities.ts"
[ -f "$WORKFLOW/prompts.ts" ] && echo "⚠ prompts.ts should be removed" || echo "✓ No prompts.ts"
[ -f "$WORKFLOW/prompts.xml" ] && echo "⚠ prompts.xml should be removed" || echo "✓ No prompts.xml"
Check Folder Naming
# List workflow folders
ls -d src/workflows/*/
# Check for non-snake_case folders
ls -d src/workflows/*/ | while read dir; do
name=$(basename "$dir")
if [[ "$name" =~ [A-Z] ]] || [[ "$name" =~ "-" ]]; then
echo "⚠ Non-snake_case folder: $name"
fi
done
Check Prompt File Naming
# List prompt files
ls src/workflows/my_workflow/*.prompt 2>/dev/null
# Check for version in prompt names
for f in src/workflows/my_workflow/*.prompt; do
if [[ ! "$f" =~ @v[0-9]+\.prompt$ ]]; then
echo "⚠ Missing version: $f"
fi
done
Fixing Structure Issues
Rename activities.ts to steps.ts
mv src/workflows/my_workflow/activities.ts src/workflows/my_workflow/steps.ts
Create scenarios directory
mkdir -p src/workflows/my_workflow/scenarios
Fix folder naming
# Rename from camelCase to snake_case
mv src/workflows/userOnboarding src/workflows/user_onboarding
Remove old files
rm src/workflows/my_workflow/prompts.ts
rm src/workflows/my_workflow/prompts.xml
Complete Example
Before Migration
src/workflows/userReport/
├── activities.ts
├── helpers.ts
├── prompts.ts
├── prompts.xml
├── readme.xml
├── types.ts
└── workflow.ts
After Migration
src/workflows/user_report/ # Renamed to snake_case
├── workflow.ts # Converted to workflow()
├── steps.ts # Converted from activities.ts
├── types.ts # Added Zod schemas
├── generateReport@v1.prompt # Converted from prompts.ts
├── formatOutput@v1.prompt
└── scenarios/ # NEW
├── daily_report.json
├── weekly_report.json
└── full_options.json
Project-Wide Structure
src/
├── workflows/
│ ├── user_onboarding/
│ │ ├── workflow.ts
│ │ ├── steps.ts
│ │ ├── types.ts
│ │ ├── welcome@v1.prompt
│ │ └── scenarios/
│ ├── generate_report/
│ │ ├── workflow.ts
│ │ ├── steps.ts
│ │ ├── types.ts
│ │ ├── analyze@v1.prompt
│ │ └── scenarios/
│ └── shared_steps/ # Optional: shared steps
│ └── shared_steps.ts
├── shared/ # Optional: shared utilities
│ ├── types.ts
│ └── helpers.ts
└── index.ts # Exports
Validation Checklist
- [ ] Workflow folder uses
snake_case - [ ]
workflow.tsexists - [ ]
steps.tsexists (if workflow has steps) - [ ]
types.tsexists - [ ] Prompt files use
name@version.promptformat - [ ] No leftover
activities.ts - [ ] No leftover
prompts.tsorprompts.xml - [ ]
scenarios/directory exists (recommended) - [ ] Scenario files use
snake_case.jsonformat
Related Skills
flow-validation-checklist- Complete migration validationflow-create-scenario-files- Creating test scenariosflow-analyze-workflow-structure- Pre-migration analysis
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/output-sdk-folder-structure-conventions-ms47vp2h/download' --output '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md.part' && mv '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md.part' '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md' && test -s '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/flow-conventions-folder-structure' && cp -R '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h' '.claude/skills/flow-conventions-folder-structure'Cursor
test -f '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md' && test -s '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/flow-conventions-folder-structure' && cp -R '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h' '.cursor/skills/flow-conventions-folder-structure'Codex
test -f '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md' && test -s '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/flow-conventions-folder-structure' && cp -R '.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h' '.agents/skills/flow-conventions-folder-structure'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h'openskills read 'output-sdk-folder-structure-conventions-ms47vp2h'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/output-sdk-folder-structure-conventions-ms47vp2h/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.