Weekly Status Report logo

Weekly Status Report

Community
sgharlow
weekly-status-report

Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities. Use when the user says "write my status report", "weekly update", "summarize my week for my manager", or pastes a raw dump of what happened this week.

Overview

Publishersgharlow
Repositoryclaude-code-recipes
Skill nameweekly-status-report
Stars
393
Forks
50
Bundled files
1
Links
  • 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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by sgharlow on GitHub. Read the source before you install it.

Installation

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

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/sgharlow/claude-code-recipes/tree/main/skills/weekly-status-report
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/sgharlow/claude-code-recipes.git /tmp/claude-code-recipes
mkdir -p .claude/skills
cp -r /tmp/claude-code-recipes/skills/weekly-status-report .claude/skills/weekly-status-report
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Weekly Status Report 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 Status Report 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 Status Report 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 Status Report

Synthesize a week of scattered raw inputs into one scannable, audience-ready status report. Report only what the inputs support — never invent accomplishments, metrics, or dates, and never upgrade routine work into a highlight without evidence of impact.

Steps

  1. Get the raw material. Accept pasted notes, forwarded emails, task-tool exports, meeting notes, and last week's report if available. Ask for: report period, the user's role, the audience (manager / leadership / client), and any required template.
  2. Classify every item, citing the input it came from:
    • Highlights — only items with stated impact (shipped, resolved, approved, measured).
    • Progress — grouped by project/workstream, with % or state only if the inputs give it.
    • Blockers & risks — each with severity (High/Medium/Low) and what unblocks it. If the inputs don't support a severity, ask rather than guess.
    • Next week — priorities, deadlines, dependencies.
  3. Render the report under one page: HIGHLIGHTS (3–5) → PROGRESS → BLOCKERS & RISKS (table: Item | Severity | Status | Needed) → NEXT WEEK → optional NOTES/FYI. Bold key items.
  4. Verify before presenting: every claim traces to a line of input; anything the user's raw notes mention that was dropped is listed back ("omitted: …") so nothing disappears silently. If last week's report was provided, note carryover items explicitly.
  5. Offer audience variants from the same material on request (3-bullet skip-level version, client-toned version, team-detail version) — same facts, different framing.

Constraints

  • The user reviews and sends the report themselves; never deliver it anywhere.
  • No metric appears unless it is in the inputs verbatim; flag wanted-but-missing metrics.
  • If the inputs are thinner than ~5 items, say so and produce a short-form update instead of padding a full template.

Full walkthrough, examples, and variations: recipes/Recipe-002-Weekly-Status-Report-Generation.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Weekly Status Report AI skill do?

Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities. Use when the user says "write my status report", "weekly update", "summarize my week for my manager", or pastes a raw dump of what happened this week.

Why use Weekly Status Report on TypingMind?

Because you install it once and use it with any model. Weekly Status Report 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 Status Report in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/sgharlow/claude-code-recipes/tree/main/skills/weekly-status-report. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Weekly Status Report?

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 Status Report?

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

Is the Weekly Status Report AI skill free?

It is published on GitHub by sgharlow. 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇