Weekly Digest

Community

Productfculty-aipm

weekly-digest

Use this skill when the user asks to "write my weekly update", "weekly PM digest", "weekly report", "write my status update", "end of week summary", "weekly standup summary", "write the PM weekly", "update the team this week", or needs to produce a regular cadence update covering what shipped, what's in progress, and what's next.

Overview

Publisher	Productfculty-aipm
Repository	`PM-Copilot-by-Product-Faculty`
Skill name	`weekly-digest`
Stars	80
Forks	34
Bundled files	Instructions only
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Productfculty-aipm on GitHub. Read the source before you install it.

Installation

Install the Weekly Digest AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/weekly-digest
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/weekly-digest

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty.git /tmp/PM-Copilot-by-Product-Faculty
mkdir -p .claude/skills
cp -r /tmp/PM-Copilot-by-Product-Faculty/skills/weekly-digest .claude/skills/weekly-digest

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Weekly Digest in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Weekly Digest on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Weekly Digest is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Weekly Digest

You are writing the weekly PM update — a regular cadence communication that keeps the team, leadership, and stakeholders aligned on product progress without requiring a meeting.

Framework: Lenny's 14 PM habits (clarity above all), Pyramid Principle (organize by insight, not chronology).

Step 1 — Load Context

Read memory/user-profile.md for: roadmap state (Now/Next/Later), OKRs, stakeholders who receive the weekly update, and communication preferences. If Linear/Jira MCP is connected, pull current sprint state.

Step 2 — Gather This Week's Content

Extract from memory and any input the user provides:

Shipped: What was completed and deployed this week? (Pull from Linear/Jira "done" if connected)

In progress: What's actively being worked on? Any changes to status or ETA?

Metrics: What moved this week? What's the trend vs. target?

Decisions made: Any significant decisions this week (prioritization, scope changes, approach decisions)?

Blockers: Any blockers that need to be surfaced to leadership?

What you learned: Any customer conversations, data signals, or team observations worth sharing?

Next week's focus: Top 3 priorities for the coming week.

If the user hasn't provided all of this, ask for the gaps or infer from memory.

Step 3 — Write the Weekly Digest

Use the context/templates/weekly-report-template.md structure. Apply the Pyramid Principle:

Lead with the most important insight, not the chronological recap
The "headline" should be the one thing that stands out this week — not "we shipped X" but "we shipped X and retention is already responding"
Organize by impact, not by time or by team

Tone calibration:

If addressing leadership: executive-friendly, outcome-focused, decision-oriented
If addressing the whole team: warmer, more inclusive, celebration-forward
If addressing a specific stakeholder: pull their preferences from memory and adjust

Step 4 — Metrics Section

For the metrics table, pull from:

context/company/analytics-baseline.md for baseline values
Any metrics the user provides in this session
North Star Metric and supporting metrics from memory

If no current metrics are available, leave placeholders and note: "Update before sending — these are empty."

Step 5 — Weekly Cadence Check

After writing the digest:

Are there any open_questions in memory older than 7 days that should be surfaced?
Are there any tracked_risks in memory that need to be mentioned?
Are there any roadmap items approaching their target date?
Proactively include relevant items the user might have forgotten.

Step 6 — Output

Produce the weekly digest using the template. Offer to:

Save to outputs/weekly-[date].md
Post to Slack (if MCP connected and channel is known from memory)
Update memory/user-profile.md with any new items surfaced during this session

Frequently asked questions

What does the Weekly Digest AI skill do?

Why use Weekly Digest on TypingMind?

Because you install it once and use it with any model. Weekly Digest is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Weekly Digest in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/weekly-digest. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Weekly Digest?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Weekly Digest?

As many as you like. As long as a model supports skills, you can use Weekly Digest with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Weekly Digest AI skill free?

It is published on GitHub by Productfculty-aipm. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Landing Report

garrytan

CommunityPopular

Read-only queue dashboard for workspace-aware ship. (gstack)

Gstack Openclaw Ceo Review

garrytan

CommunityPopular

Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.

Caveman Stats

Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

Ci Metrics

Query PyTorch CI, GitHub Actions, HUD, Grafana, and infrastructure metrics. Use when users ask about CI duration, job failures, queue times, workflow trends, runner health, dashboard data, or PyTorch…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Weekly Digest

Step 1 — Load Context

Step 2 — Gather This Week's Content

Step 3 — Write the Weekly Digest

Step 4 — Metrics Section

Step 5 — Weekly Cadence Check

Step 6 — Output

Frequently asked questions

Related AI Skills

Set up your own AI workspace now