weekly-report

weekly-report is a skill for Claude Code from jonny-1812/corebee-mcp-skills. It costs 58 tokens per session (1,481 once invoked), scanned A, original, MIT.

A support-operations report that combines key numbers, team rankings, channel results, and conversation trends for a chosen period.

In plain words
What is it for?
It helps create weekly or other period-based summaries, compare metrics such as conversations, resolution rates, response times, and AI replies, and prepare an executive overview.
Why use it?
Support data is often spread across several reports and time ranges. This brings it together and can compare periods to show what improved or declined.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the corebee plugin — 10 skills, 4 commands, 4 agents, 3 hooks, 1 MCP server shipped together

Good fit It helps create weekly or other period-based summaries, compare metrics such as conversations, resolution rates, response times, and AI replies, and prepare an executive overview.

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

Made for: Claude Code.

Or install corebee, the plugin that ships this one along with the rest of its 10 skills, 4 commands, 4 agents, 3 hooks, 1 MCP server.

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-report

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/weekly-report"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/weekly-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,481 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.00058 $0.01481
Opus 5 $0.00029 $0.00740
Sonnet 5 $0.00012 $0.00296
Haiku 4.5 $0.00006 $0.00148

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

Security

Grade A, and why

weekly-report 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 12d 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-report/SKILL.md · 127 lines

How it starts

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

Weekly Support Report

Generate a complete support operations snapshot by combining data from multiple analytics tools.

Workflow Modes

Current Period (default)

Generates a full report for a single time period.

  1. Determine the period from the user's request. Default: this_week. Supported values: this_week, last_week, this_month, last_month, last_7_days, last_30_days.
  2. Fetch dashboard KPIs using get_metrics with the resolved period
  3. Fetch team performance using get_agent_performance with the same period
  4. Fetch channel breakdown using get_channel_analytics with the same period
  5. Fetch conversation trends using get_trends with metric: "conversations" and the period
  6. Fetch AI automation trends using get_trends with metric: "ai_responses" and the period
  7. Compile and present the full report

Comparison Mode

Compares two periods side by side with delta calculations showing improvement or regression.

  1. Determine the two periods (e.g., this_week vs last_week, or this_month vs last_month)
  2. Fetch all data for both periods (KPIs, team performance, channels, trends)
  3. Calculate deltas for each metric: absolute change and percentage change
  4. Flag metrics that improved with an up arrow and metrics that regressed with a down arrow
  5. Present the comparison table with both periods and the delta column

Executive Summary

A condensed version for leadership — key numbers, top-line trends, and action items only. No detailed tables.

  1. Fetch dashboard KPIs using get_metrics with the resolved period
  2. Fetch team performance using get_agent_performance (top 3 performers only)
  3. Fetch conversation trends using get_trends with metric: "conversations"
  4. Present a 5-8 line summary with: total volume, resolution rate, average response time, AI automation rate, top performer, and one key insight or action item

Report Structure

Support Operations — Weekly Report

Overview ([Period])

  • Open conversations: [count]
  • Resolved this period: [count]
  • New contacts: [count]
  • Total messages: [count]
  • AI-handled responses: [count] ([percentage]% automation rate)
  • Avg first response time: [duration]
  • Avg resolution time: [duration]

Read the full file on GitHub · 127 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. 12d ago First seen · 127 lines · 58 tokens per session scan A d7a2ff71cf26

Subscribe to this mod's changes

weekly-report is a skill published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,481 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

customer-support

Use when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or escalation with a handoff packet. NOT the help-center article it links to (that is technical-writing), a win-back program (retention), or the…

ericrisco/rsc-harness · 90 tokens

deskcrew-support

Run a customer support desk on DeskCrew. Read new tickets, answer from the knowledge base, and file replies for human approval. Use when handling customer support. Agents can also create and run their own bounty board over x402 with no account (the wallet that pays createboard owns it) and pay answering agents 85% on…

webmilmind1/deskcrew-mcp · 72 tokens

deskcrew-bounty-hunter

Earn USDC by answering bounty support tickets on DeskCrew's open board. Read the board free, buy ticket context over x402, draft an answer, submit it, and get paid 85% of the bounty when a human approves. Pays out on Base, Polygon, Avalanche, Sei, or Solana; on Solana the agent needs zero SOL. Since 08-2026 the wallet…

webmilmind1/deskcrew-mcp · 0 tokens

deskcrew-board-owner

Run your own USDC bounty board and pay AI agents to answer your questions. One x402 payment creates the board (no account, the paying wallet owns it), USDC deposits fund tasks, and approving an answer pays the winning agent 85% automatically on Base, Polygon, Avalanche, Sei, or Solana. Use when asked to delegate work…

webmilmind1/deskcrew-mcp · 93 tokens

Zendesk Automation

Automate customer support workflows with Zendesk ticket management, routing, and analytics.

claude-office-skills/skills · 19 tokens

customer-support-integration

Connect your helpdesk (Gorgias, Zendesk, Intercom) to your store so support agents see full order history and customer details without switching tools.

finsilabs/awesome-ecommerce-skills · 36 tokens