What problem does it solve? Teams often scatter scripts, prompts, samples, and outputs across a repository with no consistent structure, making workflows hard to rerun, review, or hand off. This Skill provides a single convention for packaging a repeatable workflow as a self-contained workbook folder. ## Core Features & Use Cases - Canonical Layout: Standardizes workbooks/<workbook-slug>/ with optional scripts/, configs/, samples/, prompts/, schemas/, evals/, traces/, outputs/, and support/ subfolders. - README Template: Enforces a required README shape covering Purpose, Depends on, Contents, How to run/use, and Methodology. - Script & Safety Rules: Requires documented entrypoints, safe sample inputs, and keeps secrets, credentials, and large generated artifacts out of Git. - Use Case: When packaging a prompt-orchestration evaluation workflow, use this Skill to decide the folder structure, write the README, and register large outputs via the artifacts registry instead of committing them. ## Quick Start Ask the agent to create a new workbook under workbooks/ for your workflow following the workbook layout and README conventions.