agentleFS
claude-office-skillsclaude-office-skills/skills/weekly-report/SKILL.md

weekly-report

Skill433 starsChanged 10 months agoMITView on GitHub

>

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agency-clients, cross-post-video and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • posteverywhereSkill

    agency-clients

    Work safely across several clients or brands in PostEverywhere. Use when the user manages social media for more than one client, brand or business, mentions a client by name, asks to switch clients, or when the connected accounts belong to different companies.

    Also in 3 projects that use this

  • posteverywhereSkill

    cross-post-video

    Post one video to several platforms with PostEverywhere, with the right title and caption for each. Use when the user wants to share a video, Reel, Short or TikTok across TikTok, Instagram Reels, YouTube Shorts, LinkedIn and Facebook Reels, or asks to "post this video everywhere".

    Also in 3 projects that use this

  • CodeWithSulemanSkill

    approval-workflow

    Manage human-in-the-loop approval workflows for sensitive actions like payments, emails to new contacts, social media posts, and other actions requiring human oversight.

    Also in 3 projects that use this

  • flintfromthebasementSkill

    write-blog-post

    Write or edit a long-form blog post in a specific author's voice, then run it through six editorial passes (substance, structure, human voice, de-AI scrub, house style + O'Reilly word list, fresh-context critic) before delivering. Handles drafting from a brief, filling an outline, editing a draft, refreshing an old post, and applying revision notes. Use when the user wants a blog post that sounds like a real person wrote it, not a one-shot generation.

    Also in 3 projects that use this

  • +8 more from posteverywhere

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start with action verbs (Completed, Delivered, Launched, Resolved)

    line 255
  2. Distinctive:

    Should be reviewed for accuracy before sending

    line 306

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Weekly Report

Overview

This skill helps you create consistent, well-structured weekly status reports that communicate progress, blockers, and plans effectively to your team, manager, or stakeholders.

Use Cases:

  • Individual contributor status updates
  • Team lead rollup reports
  • Project status updates
  • Executive summaries
  • Client progress reports

How to Use

  1. Tell me what you accomplished this week
  2. Share any blockers or challenges
  3. Describe your plans for next week
  4. Specify your audience (manager, team, executives, clients)

Example prompts:

  • "Create my weekly status report for my manager"
  • "Generate a team rollup report from these individual updates"
  • "Write an executive summary of our project progress"
  • "Draft a client-facing weekly update"

Report Templates

Individual Weekly Report

# Weekly Status Report

**Name:** [Your Name]
**Week of:** [Date Range]
**Department/Team:** [Team Name]

## 🎯 Summary
[1-2 sentence highlight of the week]

## ✅ Accomplishments
- [Completed task 1]
- [Completed task 2]
- [Completed task 3]

## 🚧 In Progress
| Task | Status | Expected Completion |
|------|--------|---------------------|
| [Task] | [%] | [Date] |

## 🚫 Blockers
- [Blocker 1] - [Impact] - [Help needed]

## 📅 Next Week's Priorities
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]

## 📊 Key Metrics (if applicable)
| Metric | This Week | Last Week | Target |
|--------|-----------|-----------|--------|
| [KPI] | [Value] | [Value] | [Target] |

## 💬 Notes/FYI
- [Any additional information]

Team Rollup Report

# Team Weekly Report

**Team:** [Team Name]
**Week of:** [Date Range]
**Report by:** [Your Name]

## 📊 Team Summary
- **Velocity:** [Points/tasks completed]
- **On Track:** [X] items
- **At Risk:** [X] items
- **Blocked:** [X] items

## 🏆 Key Wins
1. [Major accomplishment 1]
2. [Major accomplishment 2]

## 👥 Individual Updates

### [Team Member 1]
- ✅ [Completed]
- 🔄 [In progress]

### [Team Member 2]
- ✅ [Completed]
- 🔄 [In progress]

## 🚨 Team Blockers
| Blocker | Impact | Owner | Escalation Needed |
|---------|--------|-------|-------------------|
| [Issue] | High/Med/Low | [Name] | Yes/No |

## 📈 Progress Against Goals
| Goal | Target | Current | Status |
|------|--------|---------|--------|
| [Goal] | [Target] | [Current] | 🟢/🟡/🔴 |

## 📅 Next Week Focus
- [Team priority 1]
- [Team priority 2]

## 🆘 Support Needed
- [Request for other teams/management]

Executive Summary Report

# Executive Weekly Update

**Project/Initiative:** [Name]
**Week of:** [Date]
**Status:** 🟢 On Track / 🟡 At Risk / 🔴 Off Track

## TL;DR
[2-3 sentences capturing the most important information]

## Key Highlights
- ✅ [Major win or milestone]
- ⚠️ [Key risk or concern]
- 📊 [Important metric or trend]

## Progress vs Plan
| Milestone | Planned | Actual | Variance |
|-----------|---------|--------|----------|
| [Milestone] | [Date] | [Date] | [+/- days] |

## Financial Summary (if applicable)
| Category | Budget | Actual | Variance |
|----------|--------|--------|----------|
| [Category] | $X | $Y | +/-$Z |

## Risks & Mitigations
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [Risk] | High/Med/Low | High/Med/Low | [Plan] |

## Decisions Needed
- [Decision requiring executive input]

## Next Week Preview
- [Key activities/milestones]

Client Progress Report

# Weekly Progress Update

**Project:** [Project Name]
**Client:** [Client Name]
**Week of:** [Date]
**Prepared by:** [Your Name]

---

Dear [Client Name],

Please find below our weekly progress update for [Project Name].

## Summary
[Brief overview of week's progress]

## Completed This Week
- ✅ [Deliverable 1]
- ✅ [Deliverable 2]

## In Progress
| Item | Progress | Expected Delivery |
|------|----------|-------------------|
| [Work item] | [%] | [Date] |

## Upcoming Milestones
| Milestone | Date | Status |
|-----------|------|--------|
| [Milestone] | [Date] | On Track/At Risk |

## Items Requiring Your Input
- [ ] [Decision or feedback needed]
- [ ] [Approval required]

## Next Week's Focus
- [Planned activities]

---

Please let us know if you have any questions or concerns.

Best regards,
[Your Name]

Writing Guidelines

Accomplishments

  • Start with action verbs (Completed, Delivered, Launched, Resolved)
  • Be specific about outcomes, not just activities
  • Quantify impact when possible
  • Link to business value

Good: "Reduced API response time by 40%, improving user experience for 50K daily users" Bad: "Worked on performance improvements"

Blockers

  • Be specific about the issue
  • Explain the impact (delays, dependencies)
  • State what help you need
  • Include any attempted solutions

Good: "Waiting on API credentials from IT (ticket #1234). This blocks the integration work scheduled for this week. Need escalation to IT manager." Bad: "Can't make progress on integration"

Next Week Plans

  • Be realistic about capacity
  • Prioritize top 3-5 items
  • Include dependencies
  • Note any risks or assumptions

Output Format

I'll generate a report matching your needs:

# [Report Title]

**Period:** [Date range]
**Author:** [Name]
**Audience:** [Manager/Team/Executives/Client]

[Structured content based on template]

Customization Options

Tell me your preferences:

  • Length: Brief (bullet points), standard, detailed
  • Audience: Team, manager, executives, clients
  • Focus: Accomplishments, blockers, metrics
  • Frequency: Can adapt for daily/bi-weekly/monthly
  • Tone: Casual team update or formal stakeholder report

Limitations

  • Cannot access your actual work systems or calendars
  • Relies on information you provide
  • May need adjustment for your organization's specific format
  • Should be reviewed for accuracy before sending

Examples

Example: Quick Status Update

Input: "I finished the dashboard redesign, fixed 3 bugs, still working on the user auth feature which is delayed because I'm waiting on the security review. Next week I'll focus on finishing auth and starting the mobile optimization."

Output:

Weekly Status Report

Name: [Your Name] Week of: [Current Week]

🎯 Summary

Completed dashboard redesign milestone. User authentication feature in progress, pending security review.

✅ Accomplishments

  • Completed dashboard redesign (UI/UX milestone)
  • Resolved 3 bugs in production
  • Advanced user authentication feature development

🚧 In Progress

TaskStatusExpected Completion
User Authentication Feature70%Pending security review

🚫 Blockers

  • Security Review Pending - User auth feature cannot be deployed until security team completes review. Impact: 2-3 day delay. Action needed: Follow up with security team on timeline.

📅 Next Week's Priorities

  1. Complete user authentication feature (post-security review)
  2. Begin mobile optimization work
  3. Address any feedback from dashboard redesign

💬 Notes

  • Dashboard redesign ready for stakeholder demo when needed

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.