AgentMarketMCP / SKILL 资产档案馆

目录 / weekly-report-pack

SKILL 未评级 已上架

weekly-report-pack

--- name: weekly-report-pack description: Auto-generate structured weekly/daily/monthly reports from scattered work traces — chats, todos, calendar, git commits, notes. Quantified wins, risks with actions taken, deliverable-oriented next steps. Multi-audience versions (manager / cross-team / exec). version: 1.0.0 author: RAY license: CC-BY-4.0 tags: [reporting, status-update, productivity, standup, writing] pricing: free: Free — 3 reports/week, single audience, no charts pro: $9/month — unlimited + monthly template + multi-audience versions + chart suggestions annual: $90/year pay_per_use: $5 one-time (single custom report) enterprise: $99/month (team template + bulk generation) tiers: - id: free name: Free price: Free quota: Free — 3 reports/week, single audience, no charts - id: pro name: Pro Monthly price: $9/month — unlimited + monthly template + multi-audience versions + chart suggestions quota: unlimited - id: annual name: Pro Annual price: $90/year quota: unlimited - id: enterprise name: Enterprise price: $99/month (team template + bulk generation) quota: team unlimited monetization: model: freemium_subscription currency: USD paywall_trigger: free quota exhausted trial_days: 7 free_trial: true upgrade_path: Pro Monthly -> Pro Annual -> Enterprise --- # Weekly Report Pack ## What problem it solves Writing status reports isn't about typing — it's about **organization**: which of the 20 things you did this week actually matter, how to quantify wins without sounding like a brag sheet, and how to surface problems without looking helpless. This pack turns "scattered traces → structured report" into a repeatable pipeline. ## Workflow 1. **Feed**: dump this week's work traces — chat logs, checked todos, calendar, git commits, notes. Any format. 2. **Pick template**: `daily` (3-part) / `weekly` (5-part) / `monthly` (business view). First run: confirm the audience (direct manager / cross-team / exec) — audience controls depth and tone. 3. **Generate**, conclusion-first: - **Core progress** (max 3 items, each = result + number + impact) - **Key metrics** (WoW delta; if no data, suggest how to collect it) - **Issues & risks** (format: issue + mitigation already taken + support needed — never a naked complaint) - **Next week** (deliverable-oriented, dependencies flagged) 4. **Format**: Markdown / email body / Slack or Teams message. ## Quality rules - Every progress item must answer "so what" — what it means for the team/project. - Numbers first: never write "significantly improved" when a number exists. - Every issue must carry an action, otherwise it goes to "observations". - Compare against last week's report to avoid re-reporting the same progress (user pastes last week's version). ## Boundaries Never fabricate data; unprovided metrics marked as [TBD]. Neutral wording on other people's performance.

模型生成摘要(rules/v1 · 2026-11-17 10:45):---
这是模型对公开材料的总结,不是官方声明,请以原链内容为准。

存档时间线

版本存档时间内容哈希内容
v12026-11-17 10:445fea7d94 可取

版本索引永久保留;内容副本只保留最新 1 份,更早版本仅留索引与哈希(存档时间线的证据链不会因此断裂)。

下载存档内容副本

纠错与举报(发现条目失效、署名有误或涉及侵权?)
提交举报 / 纠错

侵权举报经核验成立后,我们会即时下线该条目并删除已存的内容副本。