weekly-report · genspark-ai — Claude Code skill: notes to a Word report
weekly-report turns rough progress notes into a structured weekly or monthly report and returns a Word document you can hand in.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill weekly-report -a claude-codeWhat weekly-report does
Feed it the week's raw material: a bullet list, a chat log, a task list. The skill sorts all of it into four groups, then asks back for any figure or date a key item is missing instead of filling the gap itself.
The result is a Word file. A title (Week N YYYY Report unless you name it yourself), an overview capped at three lines, key results where each entry pairs a conclusion with its evidence, open work, risks plus the support you need, and the plan. Every entry stays within two lines and leads with the conclusion.
Producing the .docx relies on the document tools present in your session; without them you get text in the reply and no file. Once the document is delivered, the reply carries a sentence or two on the highlights and what could still be tuned.
What it helps with
- turn scattered weekly notes into a submittable report
- sort progress into done, in-progress and risk buckets
- surface missing numbers before the report goes out
- produce a Word status report for a manager
- carry last week's report into this week's version
Example prompts for the agent
- Sort this week's notes into done, in progress and risks, then build the Word report.
- Build a monthly report from this task list, title it
Week N YYYY Report. - Carry last week's report forward and add this week's results.
How to install weekly-report
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill weekly-report -a claude-code2Manually: put the files in place
~/.claude/skills/weekly-report/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/weekly-report/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill weekly-report -a codex2Manually: put the files in place
.agents/skills/weekly-report/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill weekly-report -a cursor2Manually: put the files in place
.cursor/skills/weekly-report/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/weekly-report2Manually: put the files in place
.github/skills/weekly-report/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill weekly-report -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/weekly-reportManually: put the files in place
.devin/skills/weekly-report/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about weekly-report
How do I install weekly-report in Claude Code?
Run npx skills add genspark-ai/genoffice --skill weekly-report -a claude-code. The skill lands at ~/.claude/skills/weekly-report/SKILL.md.
What does weekly-report do?
It turns raw progress material into a weekly or monthly report with results, data, risks and next week's plan, saved as a Word document.
Does it make up numbers that are missing?
No. When a key item has no figure or date, the skill asks for it in the reply instead of guessing.
Source text
SKILL.md · Apache-2.0
--- name: weekly-report description: 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 category: office scenarios: Weekly and monthly reports | Work summaries | Status reports quickPrompts: Write this week's report from these notes | Carry last week's report forward into this week's version metadata: version: 1.0.0 --- 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. - Next week's plan. ## Style - Conclusion first, numbers wherever possible, no item longer than two lines, no filler or boilerplate. ## Output One Word document. The reply holds only the one- or two-sentence note on highlights and possible adjustments.
© genspark-ai · Apache-2.0 · genspark-ai/genoffice
Similar skills
All skills for Office documents →weekly-report by other authors comes first.