做什么
> 翻译:
技能库 智客分类:Agent 工作流 weekly-report
> 翻译:
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
> 翻译:
官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Weekly Report、Overview、How to Use、Report Templates、Individual Weekly Report、Weekly Status Report。
文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。
>
Weekly ReportOverviewHow to UseReport TemplatesIndividual Weekly ReportWeekly Status Report🎯 Summary✅ Accomplishments🚧 In Progress🚫 Blockers📅 Next Week's Priorities📊 Key Metrics (if applicable)
· 许可:MIT
来源分类:skills.sh agent-skill
nameweekly-reportdescription具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「weekly-report」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-0266c7ab6aab0a1b-%E6%AF%8F%E5%91%A8%E6%8A%A5%E5%91%8A.html 请存为 .cursor/skills/weekly-report/SKILL.md 或 .claude/skills/weekly-report/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/claude-office-skills/skills' --list
npx skills add 'https://github.com/claude-office-skills/skills' --skill 'weekly-report'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
name: weekly-report description: ">" version: "1.0.0" author: Claude Office Skills Contributors license: MIT
category: productivity tags:
models: recommended: - claude-sonnet-4 - claude-opus-4 compatible: - claude-3-5-sonnet - gpt-4 - gpt-4o
mcp: server: office-mcp tools: - create_docx - fill_docx_template
capabilities:
languages:
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:
Example prompts:
# 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 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 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]
# 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]
Good: "Reduced API response time by 40%, improving user experience for 50K daily users" Bad: "Worked on performance improvements"
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"
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]
Tell me your preferences:
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:
Name: [Your Name] Week of: [Current Week]
Completed dashboard redesign milestone. User authentication feature in progress, pending security review.
| Task | Status | Expected Completion | |------|--------|---------------------| | User Authentication Feature | 70% | Pending security review |
Agent 工作流
创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.
Agent 工作流
使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.
Agent 工作流
管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.
Agent 工作流
Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…