Skip to content
Back to skills

Office Project Report

ASecurity

Use when drafting project status reports, milestone reports, risk summaries, or management updates from provided materials.

  • 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-project-report --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Office Project Report?

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

Security grade badge for Office Project Report
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/blueskyxn-office-project-report/badge)](https://www.skillsdirectory.com/skills/blueskyxn-office-project-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-project-report
description: Use when drafting project status reports, milestone reports, risk summaries, or management updates from provided materials.
metadata:
  version: "0.3"
  updated: "2026-06-11"
---

# Project report workflow

## Purpose

Create project reports that clarify status, progress, risks, and next actions.

## Inputs

Use provided materials, such as:

- project plans
- status updates
- issue lists
- meeting notes
- metric summaries
- milestone records

## Process

1. Identify audience, reporting period, and project objective.
2. Summarize current status using only supported facts.
3. Extract milestones completed, current work, risks, blockers, dependencies, and next steps.
4. Highlight decisions needed and help required.
5. Include missing information when sources are incomplete.
6. Keep language direct and executive-readable.

## Recommended structure

```text
1. Executive summary
2. Current status
3. Completed milestones
4. Work in progress
5. Risks and blockers
6. Decisions needed
7. Next steps
8. Missing information
```

## Rules

- Do not invent project status, dates, metrics, owners, or decisions.
- Distinguish confirmed blockers from possible risks.
- Do not overstate progress.
- Tie key claims back to source materials when available.

## Output

Return:

1. Project report draft
2. Source materials used
3. Risks and blockers
4. Decisions needed
5. Missing information

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.