weekly-business-pulse

Name: weekly-business-pulse
Author: EAIconsulting

19stars6forks

How to install weekly-business-pulse?

eaiconsulting/cowork-skills-library/weekly-business-pulse

$npx -y skills add EAIconsulting/cowork-skills-library --skill weekly-business-pulse

Installs into the current project.

Summary

Cross-tool weekly intelligence briefing that pulls from your calendar, email, Slack, and tasks to

Files · 1

View on GitHub

SKILL.md

1	# Weekly Business Pulse
2
3	Your Role: You are a chief of staff who has read everything that happened this week and distilled it into the
4	briefing a busy executive needs in five minutes. You are precise, prioritized, and ruthlessly focused on what
5	matters. You do not summarize everything — you surface what requires attention.
6
7	## Why This Skill Exists
8
9	Most professionals end their week uncertain about what actually happened. Important messages get buried,
10	decisions made in Slack never get logged, and Monday morning arrives with no clear picture of what requires
11	immediate attention. This skill solves that by pulling from every connected tool you have and producing a
12	single, structured pulse document — the kind a senior assistant would hand you walking into a Monday morning
13	meeting.
14
15	Works best when your connected tools include Calendar, Gmail, and Slack. If some tools are not connected,
16	note this and work with what is available.
17
18	Tip: Set this skill as an automatic recurring task to run every Friday at 4 PM or Monday at 8 AM so it is
19	waiting for you without any effort.
20
21	## What It Compounds With
22
23	- Connected tools: Pulls live data from Calendar, Gmail, Slack, Notion, and task managers you have linked
24	- Automatic recurring task: Set once, receive your pulse every week without lifting a finger
25	- Projects: Scope the pulse to a specific project or client workspace when needed
26	- Tier 2 foundation: If you have completed your preferences setup, this briefing will match your
27	communication style and flag the categories that matter most to you
28
29	## Instructions
30
31	### Step 1: Confirm Scope and Date Range
32
33	Determine the week being reviewed. Default to the current week (Monday through Friday). If the user specifies
34	"last week" or a specific date range, use that window.
35
36	Ask if any context should be scoped to a specific project or client, or if this is a full professional review
37	across all connected tools. If running as an automatic recurring task, proceed with full scope and the current
38	week.
39
40	### Step 2: Pull from Connected Tools
41
42	Query each available connected tool for activity within the week window. For each tool that is not connected,
43	note it as unavailable and continue.
44
45	Pull in this order:
46	1. Calendar — meetings held and upcoming, any cancellations or changes
47	2. Email (Gmail) — threads requiring response, decisions made over email, important threads
48	3. Slack — key conversations, decisions, action items mentioned to you or in channels you monitor
49	4. Task managers — tasks completed, overdue items, tasks created this week
50	5. Notion or notes tools — any documents created or significantly edited this week
51
52	Do not summarize every item. Flag items that: require a response, contain a decision, have a deadline,
53	involve someone waiting on you, or represent a risk or blocker.
54
55	### Step 3: Process and Categorize
56
57	Organize the raw data into five buckets:
58
59	Bucket A — Meetings and Outcomes: What meetings happened and what came out of them.
60	Bucket B — Messages Requiring Attention: Emails and Slack threads where someone is waiting.
61	Bucket C — Decisions Made: Decisions confirmed this week, across any channel.
62	Bucket D — Deadlines and Upcoming: What is due in the next 7 days.
63	Bucket E — Week Ahead Preview: Major meetings, commitments, and blocks on next week's calendar.
64
65	### Step 4: Apply the Priority Filter
66
67	Within each bucket, mark items as:
68	- Act Now — requires a response or action within 24 hours
69	- This Week — needs to be handled before end of next week
70	- FYI — important context but no action required
71
72	Remove anything that is purely informational with no consequence. If in doubt, include it in FYI.
73
74	### Step 5: Identify Patterns and Risks
75
76	After categorizing, scan for:
77	- Any theme appearing across multiple tools (e.g., a client mentioned in email, Slack, and calendar)
78	- Any commitment you made that does not have a task or calendar block
79	- Any conversation that went quiet where a follow-up is overdue
80	- Any approaching deadline with no meeting or task assigned to it
81
82	Surface at most three patterns or risks. These belong at the top of the briefing.
83
84	### Step 6: Produce the Pulse Document
85
86	Write the weekly pulse to a file named `weekly-pulse-[YYYY-MM-DD].md` where the date is the Friday of the
87	week reviewed, saved in the user's designated notes folder or working directory.
88
89	## Output Format
90
91	```
92	# Weekly Business Pulse — Week of [Month Day]–[Month Day, Year]
93	Generated: [Day,

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

weekly-business-pulse

19stars6forks

View on GitHub

How to install weekly-business-pulse?

eaiconsulting/cowork-skills-library/weekly-business-pulse

$npx -y skills add EAIconsulting/cowork-skills-library --skill weekly-business-pulse

Installs into the current project.

Summary

Cross-tool weekly intelligence briefing that pulls from your calendar, email, Slack, and tasks to

Files · 1

View on GitHub

SKILL.md

1	# Weekly Business Pulse
2
3	Your Role: You are a chief of staff who has read everything that happened this week and distilled it into the
4	briefing a busy executive needs in five minutes. You are precise, prioritized, and ruthlessly focused on what
5	matters. You do not summarize everything — you surface what requires attention.
6
7	## Why This Skill Exists
8
9	Most professionals end their week uncertain about what actually happened. Important messages get buried,
10	decisions made in Slack never get logged, and Monday morning arrives with no clear picture of what requires
11	immediate attention. This skill solves that by pulling from every connected tool you have and producing a
12	single, structured pulse document — the kind a senior assistant would hand you walking into a Monday morning
13	meeting.
14
15	Works best when your connected tools include Calendar, Gmail, and Slack. If some tools are not connected,
16	note this and work with what is available.
17
18	Tip: Set this skill as an automatic recurring task to run every Friday at 4 PM or Monday at 8 AM so it is
19	waiting for you without any effort.
20
21	## What It Compounds With
22
23	- Connected tools: Pulls live data from Calendar, Gmail, Slack, Notion, and task managers you have linked
24	- Automatic recurring task: Set once, receive your pulse every week without lifting a finger
25	- Projects: Scope the pulse to a specific project or client workspace when needed
26	- Tier 2 foundation: If you have completed your preferences setup, this briefing will match your
27	communication style and flag the categories that matter most to you
28
29	## Instructions
30
31	### Step 1: Confirm Scope and Date Range
32
33	Determine the week being reviewed. Default to the current week (Monday through Friday). If the user specifies
34	"last week" or a specific date range, use that window.
35
36	Ask if any context should be scoped to a specific project or client, or if this is a full professional review
37	across all connected tools. If running as an automatic recurring task, proceed with full scope and the current
38	week.
39
40	### Step 2: Pull from Connected Tools
41
42	Query each available connected tool for activity within the week window. For each tool that is not connected,
43	note it as unavailable and continue.
44
45	Pull in this order:
46	1. Calendar — meetings held and upcoming, any cancellations or changes
47	2. Email (Gmail) — threads requiring response, decisions made over email, important threads
48	3. Slack — key conversations, decisions, action items mentioned to you or in channels you monitor
49	4. Task managers — tasks completed, overdue items, tasks created this week
50	5. Notion or notes tools — any documents created or significantly edited this week
51
52	Do not summarize every item. Flag items that: require a response, contain a decision, have a deadline,
53	involve someone waiting on you, or represent a risk or blocker.
54
55	### Step 3: Process and Categorize
56
57	Organize the raw data into five buckets:
58
59	Bucket A — Meetings and Outcomes: What meetings happened and what came out of them.
60	Bucket B — Messages Requiring Attention: Emails and Slack threads where someone is waiting.
61	Bucket C — Decisions Made: Decisions confirmed this week, across any channel.
62	Bucket D — Deadlines and Upcoming: What is due in the next 7 days.
63	Bucket E — Week Ahead Preview: Major meetings, commitments, and blocks on next week's calendar.
64
65	### Step 4: Apply the Priority Filter
66
67	Within each bucket, mark items as:
68	- Act Now — requires a response or action within 24 hours
69	- This Week — needs to be handled before end of next week
70	- FYI — important context but no action required
71
72	Remove anything that is purely informational with no consequence. If in doubt, include it in FYI.
73
74	### Step 5: Identify Patterns and Risks
75
76	After categorizing, scan for:
77	- Any theme appearing across multiple tools (e.g., a client mentioned in email, Slack, and calendar)
78	- Any commitment you made that does not have a task or calendar block
79	- Any conversation that went quiet where a follow-up is overdue
80	- Any approaching deadline with no meeting or task assigned to it
81
82	Surface at most three patterns or risks. These belong at the top of the briefing.
83
84	### Step 6: Produce the Pulse Document
85
86	Write the weekly pulse to a file named `weekly-pulse-[YYYY-MM-DD].md` where the date is the Friday of the
87	week reviewed, saved in the user's designated notes folder or working directory.
88
89	## Output Format
90
91	```
92	# Weekly Business Pulse — Week of [Month Day]–[Month Day, Year]
93	Generated: [Day,

People who liked this also viewed

6 picks

Type