weekly-status

weekly-status is a skill for Claude Code, Codex from Mr-pixle/jira-mcp. It costs 95 tokens per session (947 once invoked), scanned A, original, MIT.

A Jira-based tool for turning a team’s completed work, progress, and risks from the past week into a short update. Jira is a work-tracking system used to manage tasks and projects.

In plain words
What is it for?
Use it to prepare weekly updates, summarize team work, report progress, and identify blocked or overdue tasks.
Why use it?
It removes the need to manually gather and rewrite weekly Jira activity for a manager or stakeholder.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare weekly updates, summarize team work, report progress, and identify blocked or overdue tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mr-pixle/jira-mcp/weekly-status
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 Mr-pixle/jira-mcp --skill weekly-status
Clone the repo
git clone --depth 1 https://github.com/Mr-pixle/jira-mcp

Made for: Claude Code, Codex.

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.

agentmods badge for weekly-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/mr-pixle/jira-mcp/weekly-status/github.svg)](https://agentmods.dev/skills/mr-pixle/jira-mcp/weekly-status)
Your own site
<a href="https://agentmods.dev/skills/mr-pixle/jira-mcp/weekly-status"><img src="https://agentmods.dev/badge/skills/mr-pixle/jira-mcp/weekly-status/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.

agentmods 80×15 button for weekly-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/mr-pixle/jira-mcp/weekly-status"><img src="https://agentmods.dev/badge/skills/mr-pixle/jira-mcp/weekly-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 947 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00095 $0.00947
Opus 5 $0.00048 $0.00474
Sonnet 5 $0.00019 $0.00189
Haiku 4.5 $0.00010 $0.00095

Measured 11d ago against content hash c0fe8912a403, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

weekly-status 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 11d 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.

skills/weekly-status/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Weekly Status Update

Keywords

weekly update, status report, weekly status, stakeholder update, management update, what did we do this week, progress report, status meeting, گزارش هفتگی, گزارش وضعیت, آپدیت هفتگی

Turn a week of Jira activity into an update a manager can read in two minutes.

Read-only. This skill produces text; it changes nothing.

Workflow

Step 1 — Establish the scope and reader

Ask if not stated:

  • Which projects or teams? One project, or several.
  • Who reads it? This changes everything:
    • Their manager — outcomes and risks, no issue keys in the prose
    • A stakeholder outside the team — plain language, no Jira vocabulary at all
    • An engineering lead — specifics are welcome, issue keys are useful
  • What period? Default to seven days; confirm if they say "this week" mid-week.

Step 2 — Gather

Run in this order and stop early if the answer is already clear:

  1. Report.team_performance with days=7 — what shipped, and how fast.
  2. Report.executive_summary if more than one project.
  3. Report.blocked_issues — the risks worth naming.
  4. Report.overdue_issues — only if the team actually uses due dates; if the report says they do not, drop this section rather than reporting a hollow zero.

For a single project, Issue.search with project = X AND resolutiondate >= -7d ORDER BY resolutiondate DESC gives the specific list to describe.

Step 3 — Find the story

A status update is not a list. Before writing, answer for yourself:

  • What is the single most important thing that happened?
  • Is anything different from last week — better, worse, newly stuck?
  • What does the reader need to do, if anything?

If nothing needs the reader's attention, say so explicitly. "No decisions needed this week" is a valuable sentence and managers rarely get it.

Step 4 — Write

## [Team] — week ending [date]

[One or two sentences: the headline. What moved, what matters.]

**Delivered**
- [Outcome, in the reader's language, not the ticket title]
- [...]

**In progress**
- [What is underway and roughly where it stands]

**Risks**
- [Only real ones. Each with what would resolve it.]

**Needs a decision**
- [Only if true. Otherwise write "Nothing this week."]

Read the full file on GitHub · 92 lines

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.

  1. 11d ago First seen · 92 lines · 95 tokens per session scan A c0fe8912a403

Subscribe to this mod's changes

weekly-status is a skill published in the GitHub repository Mr-pixle/jira-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 947 once invoked, about $0.0005 per session on Opus 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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 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

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

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

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

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens