# Create Clear Weekly Work Reports

Weekly reports are hard when work details are scattered. This skill guides collection, structure, and revision so users can produce clear updates.

## Install

```bash
npx skillstore add yunshu0909/weekly-report
```

## Metadata

- Status: approved
- Slug: yunshu0909-weekly-report
- Skillstore revision: r1
- Version status: missing
- Tree hash: 903453f45a2052e5f809b82abf944087d9a5d4d2a9b122481bcc4dadafd4ba47
- Author: yunshu0909
- GitHub username: yunshu0909
- License: MIT
- Repository: https://github.com/yunshu0909/yunshu\_skillshub/tree/master/weekly-report
- Ref: 64ca8af0f54a325752f08bd54e52151061ea659a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/yunshu0909-weekly-report
- Manifest: https://skillstore.pages.dev/api/skills/yunshu0909-weekly-report/manifest

## Capabilities

- Guides users through collecting weekly work details by module and role.
- Organizes work into sections for engineering, product, operations, design, QA, sales, and general roles.
- Prompts for background, actions, results, status, blockers, owners, and next steps.
- Drafts a structured weekly report with current work and next week priorities.
- Helps revise tone, structure, and emphasis while preserving the user's writing style.

## Use Cases

- Summarize engineering work: Turn completed features, bug fixes, reviews, blockers, and next steps into a clear weekly engineering update.
- Prepare product and operations updates: Organize research, launches, data analysis, user feedback, and follow-up actions into a structured weekly report.
- Create team status reports: Convert scattered team notes into a concise report that shows progress, risks, owners, and next week priorities.

## Prompt Templates

### Draft my weekly report

```
Help me write this week's report. Ask what I worked on, then organize it into a clear draft.
```

### Organize scattered notes

```
Here are my rough notes: [paste notes]. Group them by work area, identify missing details, and ask concise follow-up questions.
```

### Improve a draft

```
Review this weekly report draft. Keep my tone, strengthen the logic, add provided metrics, and clarify blockers.
```

### Prepare a manager-ready update

```
Edit my weekly report for my manager. Use these tasks, risks, and next actions. Keep it concise and do not exaggerate.
```

## Limitations

- It does not verify the factual accuracy of user-provided work details.
- It does not collect data from project trackers or external systems by itself.
- It may need user review to match company-specific report formats.
- It cannot infer important context that the user does not provide.

## Best Practices

- Provide rough notes first, then answer follow-up questions about impact and status.
- Include numbers, customer feedback, or delivery dates when they are available.
- Review the final draft for company terminology, sensitive details, and factual accuracy.

## Anti Patterns

- Do not use the skill to exaggerate outcomes or hide unresolved blockers.
- Do not paste confidential customer or company data unless your environment allows it.
- Do not accept the final report without checking facts, owners, and next steps.

## Security Audit

- Audited at: 2026-07-08T11:21:06.927\+00:00
- Summary: The external command findings are false positives from markdown code fences, inline filenames, and example folder paths. The entropy heuristic is also a false positive because SKILL.md is readable Chinese markdown with no binary, encrypted, or prompt-injection content found.

## Stats

- Views: 124
- Downloads: 60
- Favorites: 2
- Popularity score: 0