Skip to content
Back to skills

Office Weekly Report

ASecurity

Use when drafting or reviewing weekly reports from provided materials, progress logs, meeting notes, or team updates.

  • 21 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 6, 2026
development

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add BlueSkyXN/Codex-is-all-you-need --skill office-weekly-report --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Office Weekly Report?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Office Weekly Report
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/blueskyxn-office-weekly-report/badge)](https://www.skillsdirectory.com/skills/blueskyxn-office-weekly-report)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: office-weekly-report
description: Use when drafting or reviewing weekly reports from provided materials, progress logs, meeting notes, or team updates.
metadata:
  version: "0.4"
  updated: "2026-06-11"
---

# Weekly report workflow

## Purpose

Create a weekly report that is factual, concise, and useful for status tracking.

## Inputs

Use only provided materials, such as:

- `materials/` files
- meeting notes
- ticket summaries
- project logs
- explicit user-provided updates

## Process

1. Identify the reporting period, audience, and expected format.
2. Extract confirmed progress, in-progress work, blockers, risks, decisions, and next steps.
3. Separate facts from interpretation.
4. Preserve source references where available.
5. List missing information instead of inventing details.
6. Draft in a concise business style.

## Recommended structure

```text
1. Summary
2. Completed this week
3. In progress
4. Blockers and risks
5. Metrics or milestones
6. Next week plan
7. Help needed / missing information
```

## Rules

- Do not invent dates, owners, metrics, blockers, decisions, or deadlines.
- Do not claim work is completed unless the materials support it.
- Keep wording concrete and scannable.

## Output

Return:

1. Source materials used
2. Weekly report draft
3. Missing information
4. Suggested next steps

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.