weekly-report-generator

Generate professional weekly reports instantly. Transform your bullet points into polished, manager-ready reports. Never stress about weekly updates again.

Security Scan

The skill is an instruction-only weekly-report formatter that asks for no credentials or installs and its instructions match its description, but the manifest sets always:true (force-enabled) without justification which is an unnecessary privilege.

Purpose & Capability

Name/description match the SKILL.md: the skill only documents how to transform bullet points into polished weekly reports. It does not request binaries, credentials, or external services, which is appropriate for its stated purpose.

Instruction Scope

SKILL.md contains only report templates, examples, and transformation guidance — no commands, file reads, environment access, or external endpoints are referenced. Runtime instructions stay within the intended scope.

Install Mechanism

No install spec and no code files are present (instruction-only). This minimizes on-disk risk and is proportionate for a text-transformation skill.

Credentials

The skill declares no required environment variables, credentials, or config paths. That is appropriate for its functionality and reduces exposure to secret exfiltration.

Persistence & Privilege

The skill is marked always:true in its metadata and registry flags, meaning it will be force-included in every agent run. There is no clear justification for this behavior for a simple report formatter; forcing always-on increases the attack surface and is an unnecessary privilege.

What to consider before installing

This skill appears to do exactly what it says and doesn't request secrets or installs, which is good. However, it is configured as always enabled (always:true), which means it will be included in every agent session — an unnecessary and potentially risky privilege for a simple text formatter. Before installing, consider: (1) ask the publisher why the skill must be always-on and request they remove that flag if not needed; (2) verify the publisher/homepage identity (https://xiaping.coze.site) if you plan to trust it long-term; (3) if your platform supports it, install in a restricted/sandboxed environment or disable autonomous invocation for this skill; (4) if you have low tolerance for always-on skills, do not install until the always:true flag is removed. Overall risk is low aside from the always:true privilege, so treat that as the primary concern.

Overview

Turn simple bullet points into professional weekly reports in seconds. Stop staring at blank documents - get polished, manager-ready updates instantly.

When to Use

• User needs to write a weekly status report
• User mentions "weekly report", "status update", "weekly summary"
• User wants to summarize their week's work
• User is preparing for a team meeting
• User needs to document project progress

How It Works

Input

Simple bullet points of what you did this week:

- Finished the API integration
- Fixed 3 bugs in the login flow
- Had a meeting with the design team
- Started working on the new feature

Output

Professional weekly report with proper structure, professional language, and impact framing.

Report Structure

1. Summary

High-level overview of the week's achievements

2. Completed Tasks

What was accomplished with impact statements

3. In Progress

Current work and expected completion

4. Blockers

Issues preventing progress (if any)

5. Next Week

Planned activities and goals

Transformation Examples

Example 1: Developer Report

Input:

- Fixed the bug where users couldn't log in
- Added a new feature for password reset
- Code review for the team
- Started on the API optimization

Output:

## Weekly Summary
Successfully resolved critical authentication issues and delivered the password reset feature, improving user experience and reducing support tickets.

## Completed
✅ Resolved login authentication bug affecting 15% of users, restoring access and reducing support escalations
✅ Implemented password reset functionality with email verification, enhancing account security
✅ Conducted thorough code reviews for 5 pull requests, maintaining code quality standards

## In Progress
🔄 API optimization project - Phase 1 (60% complete, on track for next week delivery)

## Next Week
- Complete API optimization
- Begin database migration planning
- Continue team code review support

Example 2: Marketing Report

Input:

- Posted 3 times on social media
- Wrote a blog article
- Analyzed last month's data
- Meeting with influencers

Output:

## Weekly Summary
Executed multi-channel content strategy with strong engagement metrics and established key influencer partnerships for Q2 campaigns.

## Completed
✅ Published 3 social media posts generating 2,500+ impressions and 150 engagements
✅ Created and published SEO-optimized blog article driving 300+ organic visits
✅ Delivered comprehensive analysis of March performance data with actionable insights

## In Progress
🔄 Influencer partnership negotiations - Awaiting final contract review (expected close next week)

## Next Week
- Finalize influencer agreements
- Launch new campaign creative
- Begin Q2 content calendar planning

Example 3: General Office Report

Input:

- Attended team meetings
- Organized the filing system
- Helped with the presentation
- Answered customer emails

Output:

## Weekly Summary
Supported team operations through active meeting participation, process improvement, and enhanced customer communication.

## Completed
✅ Participated in 4 team meetings, contributing to project planning and decision-making
✅ Reorganized filing system, improving document retrieval efficiency by 40%
✅ Assisted in presentation preparation for client meeting, supporting successful delivery
✅ Responded to 50+ customer inquiries with 98% satisfaction rate

## Next Week
- Continue customer support excellence
- Support upcoming quarterly review preparation
- Implement additional process improvements

Impact Framing

Weak → Strong Transformations

Weak	Strong
Fixed bugs	Resolved critical issues, improving user experience
Did work on project	Advanced project milestones toward Q2 delivery
Had meetings	Collaborated with cross-functional teams on key initiatives
Helped team	Supported team success through [specific action]
Finished task	Delivered [result] ahead of schedule

Professional Language Upgrades

Casual	Professional
Did	Executed / Delivered
Worked on	Advanced / Progressed
Talked to	Collaborated with
Fixed	Resolved
Started	Initiated
Finished	Completed
Helped	Supported

Report Templates

Standard Weekly Report

## Week of [Date] - [Your Name]

### Summary
[One sentence overview of the week]

### Completed
✅ [Task 1 with impact]
✅ [Task 2 with impact]
✅ [Task 3 with impact]

### In Progress
🔄 [Project] - [Status] ([Percent]% complete)

### Blockers
⚠️ [Issue] - [Mitigation plan]

### Next Week
- [Goal 1]
- [Goal 2]

Brief Update

**This Week:**
- [Key achievement 1]
- [Key achievement 2]

**Next Week:**
- [Priority 1]
- [Priority 2]

**Needs:**
- [Any support required]

Usage Guidelines

1. List what you did - Simple bullet points are fine
2. Be honest - We'll frame it professionally
3. Include numbers when possible - Metrics add credibility
4. Mention blockers - Shows proactive communication
5. Preview and adjust - Make it yours before sending

Tips for Better Reports

• Start with impact, not activity
• Use numbers and percentages
• Show progress, not just completion
• Flag blockers early
• Set clear next week goals

---

Never stress about weekly reports again. 📝