serejaris/kimi-skills/work-recap-writer
Claude Code and agent skill by serejaris/kimi-skills
- community
Checking that the SKILL.md file is still in the repository.
Turn scattered work notes and git logs into structured weekly or monthly reports in data-driven, narrative, or OKR-aligned styles. Triggered when the user mentions a weekly report, monthly report, work summary, sprint summary, status update, OKR progress, or needs to organize scattered records into a formal recap.
Install
npx vskill@latest install serejaris/kimi-skills/work-recap-writerSKILL.md
The same SKILL.md was published earlier as serejaris/kimi-skills/work-recap-writer.
work-recap-writer
Generate structured weekly or monthly reports from scattered work notes and git commit history. Supports three styles — data-driven, narrative, and OKR-aligned — to fit different reporting scenarios.
Workflow
When the user asks to generate a weekly or monthly report, follow these steps:
Step 1: Gather Information
Collect two types of information:
1. Work Records (provided by the user)
Ask the user for the following (skip any items they don't have):
- Key tasks completed this period
- In-progress items not yet finished
- Issues or blockers encountered
- Plans for the next period
- Key metrics or data points (if any)
The user can provide information in any form: scattered notes, chat log excerpts, to-do list screenshots, verbal descriptions — all acceptable.
2. Git Commit History (auto-collected)
If the user's working directory is a git repository, automatically run the following commands to retrieve commit history:
If the user specifies a custom date range or author, substitute accordingly. If the current directory is not a git repo or the user explicitly says git history isn't needed, skip this step.
Step 2: Confirm Report Parameters
Confirm the following parameters with the user (skip if already specified in the initial request):
| Parameter | Options | Default | |
|---|---|---|---|
| Report type | Weekly / Monthly | Weekly | |
| Report style | Data-driven / Narrative / OKR-aligned | Data-driven | |
| Time range | Custom dates | Last 7 days (weekly) or 30 days (monthly) | |
| Output language | English / Chinese | English | |
| Audience | Direct manager / Team / Cross-functional | Direct manager |
Step 3: Organize and Categorize
Classify all collected information into the following dimensions:
- Completed — Work delivered during this period
- In Progress — Started but not yet finished, with estimated completion percentage
- Issues & Risks — Blockers, delays, or dependencies encountered
- Next Period Plans — Key priorities for the upcoming period
- Key Metrics — Relevant quantitative indicators (if any)
For git commits, group by feature area or work theme rather than listing individually. Merge related commits into a single work item description.
Step 4: Generate Report by Style
Generate the report using the template that matches the user's chosen style.
Style Templates
Style 1: Data-Driven
Best for scenarios requiring quantitative presentation of work output. Emphasizes numbers, completion rates, and comparisons.
Style 2: Narrative
Best for reporting to non-technical leadership, or when context and business value need to be conveyed.
Style 3: OKR-Aligned
Best for OKR-driven teams, mapping work output to objectives and key results.
Writing Guidelines
Regardless of style, all generated reports should follow these guidelines:
- Defragment: Merge multiple related small items into a single work theme — avoid checklist-style laundry lists
- Quantify first: Use numbers wherever possible (completion counts, progress percentages, metric changes)
- Distinguish fact from plan: Use past tense for completed items, mark in-progress items with progress, and note expected dates for planned items
- Highlight value: Connect each work item to business value or project goals — don't just describe actions
- Surface risks early: Mention blockers or risks prominently — don't bury them in details
- Keep it concise: Limit each item description to 1-2 sentences — avoid redundancy
Output Requirements
- Output format is Markdown
- Report is output directly in the conversation for the user to copy
- If the user requests saving to a file, write to their specified path
- Time range is clearly noted in the report title
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/work-recap-writer/SKILL.md
Popularity
- Repository stars
- 7
- Repository forks
- 3
- 7-day trend score
- 10
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/serejaris/kimi-skills/work-recap-writer)