Skip to content
Back to skills

Daily Composer

ASecurity

Compose a unified daily team report from per-source markdown files in a scratch directory. Use when the prompt asks to merge crawler outputs (slack, discord, email, code) into a single morning brief.

  • 23 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
ai-agentsbash

Works with

  • mcp

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add jshiv/cronicle --skill daily-composer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Daily Composer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Daily Composer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jshiv-daily-composer/badge)](https://www.skillsdirectory.com/skills/jshiv-daily-composer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: daily-composer
description: Compose a unified daily team report from per-source markdown files in a scratch directory. Use when the prompt asks to merge crawler outputs (slack, discord, email, code) into a single morning brief.
allowed-tools:
  - text_editor
  - bash
---

# Daily Composer

You will receive a scratch directory path containing per-source markdown files produced by upstream crawler tasks. Read each one and compose a single unified daily report.

Steps:

1. List the scratch dir to see which sources produced output. Expected files (any subset is fine; the others are crawlers that didn't run or didn't have content):
   - `slack.md` — what happened in Slack
   - `discord.md` — what happened in Discord
   - `email.md` — what came through email
   - `code.md` — code changes / merged PRs

2. For each present file, read it via `text_editor view`.

3. Compose a unified report at `${scratch}/REPORT.md` with this shape:

   ```markdown
   # Daily Report — <YYYY-MM-DD>

   ## TL;DR
   - one-line summary of what mattered today across all channels

   ## Slack
   - bullet
   - bullet

   ## Discord
   - bullet
   - bullet

   ## Email
   - bullet
   - bullet

   ## Code
   - bullet
   - bullet
   ```

   Skip sections whose source file is missing or empty rather than emitting a "no data" placeholder. The TL;DR is required.

4. If a Slack MCP server is configured, post the rendered report to the channel named in the prompt. Otherwise, just leave the file in the scratch dir.

5. Reply with the literal lines:
   ```
   REPORT: ${scratch}/REPORT.md
   COMPOSED.
   ```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…