Weekly and Daily Report Generator

Problem

Engineers and operators often have the work but not a clear report. Details are scattered across chats, tickets, and meetings, so drafts can become vague, process-heavy, and hard to paste into docs or IM.

How It Works

The skill turns informal work notes into a structured weekly or daily report. Input can be short phrases such as shipped a release, fixed bugs, or followed up with three customers, or an existing draft can be pasted directly. It selects a template based on role or context, such as standard workplace, sales, product/engineering, OKR, or formal/public-sector, then maps scattered facts into results, metrics, next steps, and risks.

Polishing follows explicit rules:
- Outcome over process
- Numbers over adjectives
- Actions over status
- Closed loops over open risks

If metrics are missing, it uses placeholders such as {N} or {percent} instead of inventing values. Output is Markdown by default, with optional plain text or HTML for documents, chats, or email.

Limits

It is meant to professionalize existing work, not create unreported outcomes. Sparse input may trigger follow-up questions, and unclear role or company type may require confirmation. It does not call external APIs, read or write local files, or execute scripts, so it relies mainly on the user-provided context and prompt rules.