Skip to content

Recipes

Ready-made workflow templates and worked examples you can import, study, or adapt.

Recipes are full workflow definitions packaged as JSON files. Import one to get a working starting point, then edit it for your team. They are different from Examples, which are written walkthroughs — recipes are the workflows themselves.

How to use a recipe

  1. Download the .playbook.json file from the list below.
  2. In Pencel, go to WorkflowsImport.
  3. Pick the file. Pencel reads the workflow, lists any connections it needs, and walks you through filling in credentials.
  4. Open the imported workflow in the authoring view to edit it before promoting.

TIP

Treat recipes as starting points, not finished products. The instructions, schedules, and tool wiring are reasonable defaults — your team's process will need adjustments.

Available recipes

RecipeWhat it does
adversarial-tools.playbook.jsonRed-team a workflow by intentionally probing tool edge cases
compliance-audit.playbook.jsonWalk through a compliance checklist and produce an audit report
customer-feedback-triage.playbook.jsonCluster, prioritize, and route incoming customer feedback
legal-contract-review.playbook.jsonSummarize key clauses, flag risks, and draft a redline memo
long-pipeline.playbook.jsonMulti-stage pipeline example with branching and approvals
mcp-notion-query.playbook.jsonQuery Notion via MCP and roll results into a structured report
multi-source-news-brief.playbook.jsonAggregate news from multiple sources into a daily brief
vague-morning-cleanup.playbook.jsonTriage overnight messages and tasks into a morning action list
weekly-team-summary.playbook.jsonSummarize the past week's work into a team-facing update

The full list lives in docs/recipes/ in the source repo.

  • RFP Scout (Federal) — a recipe with its own walkthrough covering source filtering, the mcp-rfp pattern, and how the seen-stream deduplication works. Good reference for building any "watch a source, surface new items" workflow.

What's Next