agentleFS
Sign inStart free
aiflaredevaiflaredev/aiflare/skills/daily-digest/SKILL.md

daily-digest

Skill0 starsChanged 6 months agoMITView on GitHub

Generate a daily digest report (DEV or PM audience), then save it to the server.

17 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the first token is dev or pm (case-insensitive), interpret it as audience and consume it.

    line 12
  2. Very specific:

    If the next remaining token (or the first token, when audience was not specified) matches YYYY-MM-DD, interpret it as date.

    line 13
  3. Distinctive:

    Before generating the report, run git log --oneline -3 to detect the language used in recent commit messages.

    line 25
  4. Very specific:

    Call get_daily_digest MCP tool with date (if specified) and audience.

    line 30
  5. Very specific:

    Call save_daily_digest_report MCP tool with date, title, content, and audience.

    line 33
  6. Distinctive:

    All report content MUST be written in formal report style.

    line 44
  7. Very specific:

    Commit hashes (e.g., abc1234)

    line 71
  8. Very specific:

    All statements MUST be derived from the data returned by get_daily_digest.

    line 83

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Generate a daily digest report. Two audiences are supported via argument: DEV (developer-facing) or PM (business-facing).

Argument Parsing

Tokenize $ARGUMENTS by whitespace. Apply the rules in order:

  1. If the first token is dev or pm (case-insensitive), interpret it as audience and consume it. Otherwise, audience defaults to DEV.
  2. If the next remaining token (or the first token, when audience was not specified) matches YYYY-MM-DD, interpret it as date. Otherwise, omit date (the MCP tool will use today's date).
  3. Ignore any further tokens.

Examples:

  • /daily-digest → audience=DEV, date=today
  • /daily-digest 2026-04-09 → audience=DEV, date=2026-04-09
  • /daily-digest pm → audience=PM, date=today
  • /daily-digest pm 2026-04-09 → audience=PM, date=2026-04-09
  • /daily-digest dev 2026-04-09 → audience=DEV, date=2026-04-09

Writing Language

Before generating the report, run git log --oneline -3 to detect the language used in recent commit messages. Write the entire report in that language.

Steps

  1. Parse arguments to determine audience and (optionally) date.
  2. Call get_daily_digest MCP tool with date (if specified) and audience. The header in the returned data will indicate whether you are in DEV or PM mode.
  3. Generate the report following the DEV mode or PM mode section below — only one applies based on the resolved audience. Do not mix the two.
  4. Display the generated report to the user.
  5. Call save_daily_digest_report MCP tool with date, title, content, and audience.
  6. Display the save confirmation message.

DEV mode

Apply this section ONLY when audience=DEV.

Writing Style

All report content MUST be written in formal report style. Do not use conversational or casual tone.

  • O: "Payment retry logic was implemented.", "A total of 3 commits were made."
  • X: "We added some retry stuff.", "So basically 3 commits happened."

Required Sections

  • Title: A one-sentence summary of the day's key work (include the date)
  • Overview: 2-3 sentences describing the overall work of the day (total commits, sessions, key areas)
  • Session Summary: For each session, summarize what was done, key decisions made, and files changed
  • Tag Distribution: Breakdown of work by type (FEATURE, BUGFIX, REFACTOR, etc.)
  • Most Changed Files: List the most frequently changed files with context on why they were modified
  • Key Decisions: Highlight important architectural or design decisions from the day

Technical vocabulary (commit hashes, file paths, class/function names, terms like "refactoring", "schema") is allowed.

PM mode

Apply this section ONLY when audience=PM.

Writing Style

All report content MUST be written in formal report style. Do not use conversational or casual tone.

Forbidden vocabulary (NEVER include)

  • Commit hashes (e.g., abc1234)
  • File paths (e.g., src/payment/PaymentService.kt)
  • Class/function names (e.g., PaymentService, createPayment())
  • Technical jargon: "refactoring", "migration", "endpoint", "query", "schema", "DI", "JPA", etc.

Preferred vocabulary

  • Product/feature unit naming: "checkout screen", "user signup flow", "admin page"
  • Business impact framing: "internal stability improvement", "performance improvement", "user experience improvement"

Hallucination guard

All statements MUST be derived from the data returned by get_daily_digest. Do NOT add facts not present in the data (external meetings, customer feedback, schedules, etc.).

Required Sections (5 — all mandatory)

Even if a section's data is sparse, do NOT omit it — instead state "Limited activity today" or equivalent. Section consistency must be preserved.

  1. Title: A one-sentence summary including the date (e.g., 2026-05-09: Official launch of the payment module and monitoring beta in progress)
  2. Today's Key Achievements: 2–3 bullets describing user/business-facing progress. Extract user-facing items from keyDecisions and tagBreakdown.
  3. Key Decisions and Their Impact: Re-narrate keyDecisions in non-technical vocabulary. For each decision, state its business/product impact in one sentence.
  4. Work Distribution: From sessions and mostChangedFiles, describe per-session/per-area work focus. If work is concentrated in one area, state so explicitly.
  5. Reference Statistics: Total commits, total sessions, tag breakdown — kept brief, in appendix tone.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free