What is weekly-progress-summary?

A weekly project report generated from Jira and Linear, tools for tracking software work. It summarises shipped work, risks or blockers, and priorities for the following week.

Use it every Friday to report completed work, explain what is at risk, identify what is needed to unblock it, and list next week's priorities.

It turns issue updates into an outcome-focused report for stakeholders instead of a list of ticket changes. Using the official connectors also handles access and rate limits.

weekly-progress-summary — Skill for Claude Code by Aibier

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Aibier/claude-em-toolkit --skill weekly-progress-summary

Clone the repo

git clone --depth 1 https://github.com/Aibier/claude-em-toolkit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aibier/claude-em-toolkit/weekly-progress-summary/github.svg)](https://agentmods.dev/skills/aibier/claude-em-toolkit/weekly-progress-summary)

Your own site

<a href="https://agentmods.dev/skills/aibier/claude-em-toolkit/weekly-progress-summary"><img src="https://agentmods.dev/badge/skills/aibier/claude-em-toolkit/weekly-progress-summary/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aibier/claude-em-toolkit/weekly-progress-summary"><img src="https://agentmods.dev/badge/skills/aibier/claude-em-toolkit/weekly-progress-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 465 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00035	$0.00465
Opus 5.5	$0.00014	$0.00186
Sonnet 5.5	$0.00007	$0.00093
Haiku 4.5	$0.00003	$0.00047

Measured 2mo ago against content hash 4ccf73392ce2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

weekly-progress-summary scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/weekly-progress-summary/SKILL.md · 51 lines

What it actually says

Weekly Progress Summary (Fridays)

A higher-altitude rollup than the twice-daily pulse — meant for stakeholders, not just yourself. Runs once a week, typically Friday afternoon.

Steps

Pull the week's activity through the official MCP servers (same connectors as jira-progress-pulse — Linear MCP and the official Atlassian Remote MCP server) rather than ad hoc API calls:
- Linear: issues completed/updated in the cycle (list_issues with date filters, list_cycles)
- Jira: JQL like project = X AND updated >= -7d, plus a sprint/board view for burndown context
- Using the official connectors means auth and rate-limit handling are already solved — and the same connection serves both this skill and the daily pulse, no duplicate setup.

Organize into:

## Week of <date> — <Project> Summary

**Shipped this week**
- <outcome-level bullets — "Shipped X", not "closed JIRA-123">

**At risk / blocked**
- <issue + why + what's needed to unblock — be specific, this is the
  section stakeholders actually act on>

**Next week**
- <top 3-5 priorities pulled from the upcoming sprint/cycle>

**Velocity note** (optional)
- <only include if the trend is notable — don't manufacture a metric>

Write for the audience: translate ticket titles into outcomes a non-engineer would understand. Group related tickets into one bullet.
Show the draft for review before sending/posting (Slack, email, Confluence — whatever the configured destination is). Don't auto-publish.

Notes

Schedule via /schedule for Friday afternoons.
"At risk" is the most valuable section — don't bury it or skip it because it's uncomfortable to report.
Keep total length to something a busy stakeholder reads in under a minute.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 51 lines · 35 tokens per session scan A 4ccf73392ce2

Subscribe to this mod's changes

weekly-progress-summary is a skill published in the GitHub repository Aibier/claude-em-toolkit (5 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 465 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

dev-console-context

Use when the user mentions Developer Console, projects, workspaces, credentials, or orgs — or uses phrases like "show my projects", "list workspaces", "get credentials", "switch project", "which org", "my org", "console", "navigate", "explore", "what projects do I have", "show credentials", "what workspace". Also use…

adobe/skills · 169 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens