Automated summary

Automatically generates a daily developer journal or a progress report from the repository's git history.

Strengths

Covers two output modes: a daily journal and a weekly progress report
Detects whether the project is research or development from commit keywords and file extensions, then adapts the report structure
Uses git log and git diff --stat to build change tables and commit/file statistics
Saves the result to a dated markdown file under reports/YYYY-MM-DD.md

Limitations

Restricted to today's commits or the HEAD~N HEAD range: uncommitted work and anything outside git are ignored
Research vs development detection is keyword-heuristic and can misfire on mixed repositories
No documented way to change the date range, aggregate multiple repos, or merge a team's work

When to use it

Use it at the end of a day or week when you need a quick written record of progress without drafting the report by hand.

When not to use it

Skip it if today's work isn't committed yet, or if you need a narrative report covering decisions and context beyond the code.

Security analysis

Safe

Quality score80/100

The skill only instructs safe, read-only git commands to inspect local history and generate a markdown report. It does not exfiltrate data, modify or delete files beyond writing a report, download scripts, or disable safety controls.

No concerns found

How this analysis is made

Examples

Daily journal

/work-report

Weekly progress report

/work-report progress

Report after a research sprint

Look at my commits from today, recognise that this is a research repo with training runs, and write the journal entry with experiment parameters, results and next steps.

Work Report Skill

Name: Work Report
Author: Skills Guide Bot

Auto-generate developer journal and progress report.

Commands

/work-report — daily journal
/work-report progress — progress report

Instructions

1. Get git info

git log --since="today 00:00" --format="%h %s" --no-merges
git diff --stat HEAD~N HEAD

2. Detect project type

Research: commits contain experiment/train/test/lr/batch; files are .py/.ipynb/.csv/.pth
Development: commits contain fix/feat/refactor; files are .js/.ts/.html/.java

3. Generate report

Research journal:

Experiment parameters and results
Conclusions
Code changes
Next steps

Developer journal:

Today's work summary
Code changes table
Stats (commits, files)

Progress report:

This week's achievements
Current issues
Next week's plan
Support needed

4. Save

Output to reports/YYYY-MM-DD.md

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/work-report-mryiqh9p/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/work-report-mryiqh9p' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/work-report-mryiqh9p/download' --output '.skill-downloads/work-report-mryiqh9p/SKILL.md.part' && mv '.skill-downloads/work-report-mryiqh9p/SKILL.md.part' '.skill-downloads/work-report-mryiqh9p/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/work-report-mryiqh9p/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot