opsbeginner

Weekly digest reporter

Runs every Monday at 9am, searches the week's activity, writes a concise digest, and posts it to Slack through the pieces integration. No always-on process, no separate scheduler service - the schedule lives next to the agent.

lines 44cost ~$0.02 per runapp id weekly-digest

Install it locally

# save the YAML below as app.yaml in a new folder
digitorn install ./weekly-digest

This is a local install: the folder you create is the source. No Hub package to publish first.

What you get

Posts the Monday digest at 9am, every week, on autopilot
A real, compiler-verified cron schedule (numeric weekday, not a name)
Slack posting through the pieces integration, no bot-token wiring
Cheap on Haiku, no premium model needed

Credentials this template uses

Anthropic Claude

Click each one for the credential setup command, scope guidance, and provider details.

The full YAML, ready to fork

app.yaml

1schema_version: 223app:4  app_id: weekly-digest5  name: "Weekly digest"6  version: "1.0.0"7  category: "devops"89runtime:10  mode: background11  entry_agent: reporter1213tools:14  capabilities:15    default_policy: auto16    grant:17      - { module: pieces, tools: ["*"] }18  modules:19    web: {}20    pieces:21      constraints:22        allowed_pieces: [slack]23    channels:24      config:25        providers:26          monday_digest:27            adapter: cron28            config:29              schedule: "0 9 * * 1"30            activation:31              agent: reporter32              message: "Generate this week's engineering digest."3334agents:35  - id: reporter36    modules: [{web: [search, fetch]}]37    brain:38      provider: anthropic39      model: claude-haiku-4-540      credential: { ref: anthropic_main, scope: per_user, provider: anthropic }41    system_prompt: |42      Generate a concise digest of the last 7 days.43      Post it to the #engineering Slack channel via the pieces Slack action.44      Keep it under 300 words. Be terse.

How it works

cron adapter with a schedule the runtime can actually read

adapter: cron takes a standard 5-field crontab schedule - 0 9 * * 1 for Monday. Day names like MON are rejected at compile time: digitorn-background needs the numeric form, and this template ships one that's been compiled and verified.

pieces for the Slack post, not an invented module

There's no standalone 'slack' module in the schema. Posting to Slack goes through pieces, the same third-party-integration layer real Digitorn apps use, scoped with allowed_pieces: [slack].

minimal tool surface

web for gathering the week's signal, pieces for the Slack post. The agent sees only what it needs to do its one job.

Read the deep dive

10 apps you can ship in 50 lines of YAML

Read article

Newsletter

Get the next post in your inbox.

Engineering notes from the Digitorn team. No marketing, no launch announcements, no "10 prompts that will change your life". Just the things we write that we'd want to read.

Other templates

developerStarter coder/templates/starter-coder developerClaude Code clone/templates/claude-code-clone researchDeep research agent/templates/deep-research messagingDiscord helper/templates/discord-helper developerPull request reviewer/templates/pr-reviewer knowledgeDocumentation generator/templates/doc-writer creativeLive React app builder/templates/react-builder knowledgeKnowledge base agent/templates/knowledge-base-agent opsScheduled data pipeline/templates/data-pipeline