Token导航 LogoToken导航

Agent Skill · 开发

weekly-work-report(每周工作报告)

weekly-work-report 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

weekly-work-report 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 10,717。

总安装 2,105周安装 86GitHub Stars 公开资料未说明下载 674核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:weekly-work-report(每周工作报告)
来源仓库:https://github.com/huajianjiu000/weekly-work-report
安装命令:
openclaw skills install weekly-work-report
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install weekly-work-report

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

立即生成专业的每周报告。将您的要点转化为精美的、可供经理使用的报告。再也不用担心每周更新了。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install weekly-work-report;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

weekly-work-report 怎么安装?

在终端执行 openclaw skills install weekly-work-report。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

weekly-work-report 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

weekly-work-report 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

weekly-work-report 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

weekly-work-report 用的人多吗?

公开数据是累计安装 2,105 次,近一周安装 86 次,下载 674 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

weekly-work-report 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
weekly-work-report

每周工作报告 · 本页

2,105—需要联网MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
weekly-report-generator
description
Generate professional weekly reports instantly. Transform your bullet points into polished, manager-ready reports. Never stress about weekly updates again.
license
MIT
metadata
openclaw
emoji
📝
homepage
https://xiaping.coze.site
requires
bins
[]
always
true

Weekly Report Generator

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

WeakStrong
Fixed bugsResolved critical issues, improving user experience
Did work on projectAdvanced project milestones toward Q2 delivery
Had meetingsCollaborated with cross-functional teams on key initiatives
Helped teamSupported team success through [specific action]
Finished taskDelivered [result] ahead of schedule

Professional Language Upgrades

CasualProfessional
DidExecuted / Delivered
Worked onAdvanced / Progressed
Talked toCollaborated with
FixedResolved
StartedInitiated
FinishedCompleted
HelpedSupported

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. 📝

平台分布

OpenClaw

72.79%
按下载量换算491

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills