Weekly Report Agent Skill
>- **WORKFLOW SKILL** — Generate weekly executive reports for the azd team. Pulls PR/issue/release data from GitHub, reads changelogs, combines with team notes, and produces a polished markdown report. summary, generate report, report time. (use changelog-generation), general docs, PRs.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/Azure/azure-dev --skill weekly-reportWhat comes with it
2 491 bytes besides the instructionThe instruction itself
14 sections, as written by the authorWeekly Executive Report Generator
Generates weekly executive reports for the Azure Developer CLI (azd) team leadership.
Prerequisites
| Tool | Purpose |
|------|---------|
| gh | GitHub CLI — authenticated with repo access |
| jq | JSON filtering for release queries |
| git | Repository data |
Report Format (strict order)
📝 TLDR
📊 Metrics
⚠️ Risks + Blockers
🎯 Changelog
📋 This Week
🔜 Next Week
🚩 Learnings
🔥 Demos/Links
Execution Flow
Step 1: Confirm date range
Cadence is Thursday to Thursday. Confirm with the user if unclear.
Step 2: Pull repo data
Replace START and END below with the dates from Step 1.
cd <repo-root> # the azure-dev repository root
git checkout main && git pull --rebase
PRs merged:
gh pr list --repo Azure/azure-dev --state merged --search "merged:START..END" --limit 200 --json number,title,mergedAt
Issues closed:
gh issue list --repo Azure/azure-dev --state closed --search "closed:START..END" --limit 200 --json number,title,closedAt
Releases:
gh api repos/Azure/azure-dev/releases --paginate | jq '[.[] | select(.published_at >= "START" and .published_at <= "END") | {name, tag_name, published_at}]'
Step 3: Read changelogs
Changelog data is maintained by the changelog-generation skill.
- Core:
cli/azd/CHANGELOG.md - Agents:
cli/azd/extensions/azure.ai.agents/CHANGELOG.md - Finetuning:
cli/azd/extensions/azure.ai.models/CHANGELOG.md
Step 4: Wait for team notes
Do NOT assemble the report until the user provides team notes from emails, Teams, meetings, etc.
Only product and engineering content.
Step 5: Assemble report
Combine repo data with team notes. Follow all rules below.
Step 6: Iterate
Expect 5–15 rounds of edits. Apply changes surgically. After removals, check for related content elsewhere (risks → next week → learnings → TLDR) and offer to clean up.
Output
Save reports to the Copilot CLI session workspace (~/.copilot/session-state/<session-id>/files/) as weekly-report-{month}{startday}-{endday}.md.
Section Rules
{{ references/SECTION-RULES.md }}
Tone and Style
{{ references/TONE-RULES.md }}
Example Report
Use the latest completed report in the session files as a format reference.
Other skills for the same job
different authors, same section of the catalogue
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.
Query openFDA API for drugs, devices, adverse events, recalls, regulatory submissions (510k, PMA), substance identification (UNII), for FDA regulatory data analysis and safety research.
MATLAB and GNU Octave numerical computing for matrix operations, data analysis, visualization, and scientific computing. Use when writing MATLAB/Octave scripts for linear algebra, signal processing, image processing, differential equations, optimization, statistics, or creating scientific visualizations. Also use when the user needs help with MATLAB syntax, functions, or wants to convert between MATLAB and Python code. Scripts can be executed with MATLAB or the open-source GNU Octave interpreter.
UMAP dimensionality reduction. Fast nonlinear manifold learning for 2D/3D visualization, clustering preprocessing (HDBSCAN), supervised/parametric UMAP, for high-dimensional data.
Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.
Access AlphaFold 200M+ AI-predicted protein structures. Retrieve structures by UniProt ID, download PDB/mmCIF files, analyze confidence metrics (pLDDT, PAE), for drug discovery and structural biology.
How to use it
Take azure/weekly-report from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.