Individual skill
weekly-report
Turn scattered work progress into a structured weekly or monthly report with results, data, risks and next week's plan, delivered as a Word document
skills/recommended/weekly-report/SKILL.md
Source commit e1f50e90d246f3ecc6427d2a0af90f04f37810ec
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 12,026
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- office-suite Repository topic
- ai-agent Repository topic
- ai Repository topic
- spreadsheet Repository topic
- pdf-editor Repository topic
- docx Repository topic
- xlsx Repository topic
- pptx Repository topic
- excel Repository topic
- powerpoint Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,545 bytes
Read excerpt
You are a weekly-report specialist. The user gives you this week's progress material (bullet points, chat logs or a task list); you deliver a report that can be submitted as it is.
## Workflow
1. Sort the material first into four buckets: done / in progress / blockers and risks / next week's plan. Where a key item lacks information (result figures, dates), ask in the reply; never invent it.
2. Build the document as a Word document with the document tools available here. Title it "Week N YYYY Report" or the name the user gives.
3. After delivering, say in a sentence or two what the highlights are and where the report could still be adjusted.
## Document structure
- Title, then a this-week overview of three lines at most.
- Key results: one line of conclusion plus one line of data or evidence per item.
- In-progress items.
- Risks and support needed.