workbook

Defines layout, README, and script conventions for reusable workbook bundles under workbooks/.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill workbook-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workbook
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-tasks/skills/workbook
Command: npx skills add https://github.com/toderian/project_template --skill workbook-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about workbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a reusable workflow folder in a repository?

Create a folder at workbooks/<workbook-slug>/ containing a README.md plus only the subfolders the workflow needs, such as scripts/, configs/, samples/, prompts/, schemas/, evals/, traces/, outputs/, or support/. Do not create empty folders just to match the template.

What sections should a workbook README include?

A workbook README must include Purpose, Depends on, Contents, How to run/use, and Methodology sections. Dependencies are listed as repo-relative paths to other workbooks, and external tools or datasets are named explicitly with setup notes.

When should work go in workbooks/ versus docs/resources/?

Use workbooks/ for reusable working bundles that combine instructions with scripts, data, or outputs for one workflow. Use docs/resources/ for curated knowledge: _inbox/ for raw uploads, _digests/ for summaries, and <area>/attachments/ for long-lived source documents.

Can I commit generated outputs and large artifacts in a workbook?

No. Keep secrets, credentials, customer-specific values, and very large generated outputs out of committed workbooks. Register large or external artifacts via the artifacts-registry skill and commit only the runnable workflow, metadata, safe samples, and output documentation.

What is a prompt orchestration workbook?

It is a workbook bundle for long-running or repeatable agent workflows, packaging prompts, schemas, eval fixtures, trace guidance, and planning scripts. Keep the first version vendor-neutral and add frameworks like LangGraph only when durable state, checkpointing, or branching is required.