Duckz289Duckz289/Pipeline-to-proposal-Plugin-STANDARD/skills/weekly-summary/SKILL.md

weekly-summary

Skill2 starsChanged 4 months agoMITView on GitHub

Summarises the week from local deal memory: who was contacted, who replied, who needs a follow-up, which deals are stuck. Triggered by "tổng kết tuần", "tuần này thế nào", "deal nào cần follow", "weekly summary", "review my pipeline", "what needs attention".

6 other projects use a version of this.

Adopted by

Most recently taken up by

quarto-dev/q2their own version, first seen Nov 9, 2026
dmzoneill/skillstheir own version, first seen Oct 24, 2026
iShawnWang/skillstheir own version, first seen Sep 14, 2026
LJW0401/claude-code-skillstheir own version, first seen Apr 30, 2026
willfanguy/work-summary-kittheir own version, first seen Apr 10, 2026
kunwl123456/zeroclaw-skills-collectiontheir own version, first seen Feb 19, 2026

Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
quarto-dev/q2★ 302same name
kunwl123456/zeroclaw-skills-collection★ 27same name
dmzoneill/skills★ 2same name
iShawnWang/skills★ 1same name
LJW0401/claude-code-skills★ 1same name
willfanguy/work-summary-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- crm-noteSkill
- draft-outreach-emailSkill
- draft-proposalSkill
- getting-startedSkill
- research-prospectSkill
- run-pipelineSkill
- setup-product-contextSkill
- suggest-next-stepSkill
- update-deal-feedbackSkill

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read <DATA>/deals/, <DATA>/follow-ups.md, and <DATA>/feedback.md, then return a short table.
line 11
Distinctive:
Keep it tight and readable.
line 14
Very specific:
Read deals/index.md for active deals.
line 18
Very specific:
Read feedback.md filtered to the period asked for (default: last 7 days).
line 19
Very specific:
Read follow-ups.md for overdue and upcoming items.
line 20
Distinctive:
Never fabricate a report to look useful.
line 56
Distinctive:
Write long. It must fit on a phone screen.
line 63
Very specific:
If the user asks for a month or quarter, also read the archive files per ${CLAUDE_PLUGIN_ROOT}/policies/state-management.md.
line 67

“Common” is measured: kept by at least 6 in 10 of the 3 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 summary

Read <DATA>/deals/, <DATA>/follow-ups.md, and <DATA>/feedback.md, then return a short table.

This is the thing a salesperson wants to screenshot — for their manager, their team, themselves. Keep it tight and readable.

How

Read deals/index.md for active deals.
Read feedback.md filtered to the period asked for (default: last 7 days).
Read follow-ups.md for overdue and upcoming items.
Count and group. Never invent numbers — only count what is actually in the files.

Output

### Tuần này (24/07 – 30/07)

- Đã liên hệ: 8 công ty
- Có phản hồi: 3
- Đã hẹn gặp: 1
- Đang chờ trả lời: 4

### Cần làm ngay
- [Quá hạn 2 ngày] ABC Logistics — follow-up proposal
- [Hôm nay] Minh An — gửi báo giá đã sửa

### Đang kẹt
- FPT — im lặng 12 ngày sau demo. Nên gửi break-up hoặc hẹn lại tháng sau.

### Sắp tới
- 02/08 — DEF Corp — gọi lần 2

Drop any section with no data. Nothing overdue → no "needs attention" section. Headings follow the user's language.

When there is no data

<DATA> is empty or has no deals:

Mình chưa có deal nào trong bộ nhớ. Bắt đầu bằng cách viết email cho một khách,
rồi báo mình kết quả — từ tuần sau mình sẽ tổng kết được.

Never fabricate a report to look useful.

Never

Count anything not in the files.
Derive a reply rate when the user has not reported enough outcomes.
Mention opened emails or clicked links — there is no tracking.
Write long. It must fit on a phone screen.

Other periods

If the user asks for a month or quarter, also read the archive files per ${CLAUDE_PLUGIN_ROOT}/policies/state-management.md.

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.

Check your setup, free