Oc Status
anthropics/claude-for-legal
Generate weekly status-request email drafts to outside counsel across the active portfolio — markdown per matter, plus Gmail drafts when the MCP is available.
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.
Install Weekly Status Report
$ npx skills add sgharlow/claude-code-recipes --skill weekly-status-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sgharlow/claude-code-recipes weekly-status-report --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sgharlow/claude-code-recipes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/weekly-status-report .claude/skills/weekly-status-report && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "weekly-status-report" agent skill from https://github.com/sgharlow/claude-code-recipes/tree/main/skills/weekly-status-report into .claude/skills/weekly-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-status-report", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sgharlow/claude-code-recipes/tree/main/skills/weekly-status-reportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sgharlow/claude-code-recipes --skill weekly-status-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sgharlow/claude-code-recipes weekly-status-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sgharlow/claude-code-recipes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/weekly-status-report .agents/skills/weekly-status-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "weekly-status-report" agent skill from https://github.com/sgharlow/claude-code-recipes/tree/main/skills/weekly-status-report into .agents/skills/weekly-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-status-report", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sgharlow/claude-code-recipes --skill weekly-status-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sgharlow/claude-code-recipes weekly-status-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sgharlow/claude-code-recipes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/weekly-status-report .cursor/skills/weekly-status-report && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "weekly-status-report" agent skill from https://github.com/sgharlow/claude-code-recipes/tree/main/skills/weekly-status-report into .cursor/skills/weekly-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-status-report", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sgharlow/claude-code-recipes.git --path skills/weekly-status-report--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sgharlow/claude-code-recipes --skill weekly-status-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sgharlow/claude-code-recipes weekly-status-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sgharlow/claude-code-recipes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/weekly-status-report .gemini/skills/weekly-status-report && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "weekly-status-report" agent skill from https://github.com/sgharlow/claude-code-recipes/tree/main/skills/weekly-status-report into .gemini/skills/weekly-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-status-report", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sgharlow/claude-code-recipes weekly-status-reportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sgharlow/claude-code-recipes --skill weekly-status-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sgharlow/claude-code-recipes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/weekly-status-report .github/skills/weekly-status-report && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "weekly-status-report" agent skill from https://github.com/sgharlow/claude-code-recipes/tree/main/skills/weekly-status-report into .github/skills/weekly-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-status-report", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sgharlow/claude-code-recipes --skill weekly-status-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sgharlow/claude-code-recipes weekly-status-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sgharlow/claude-code-recipes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/weekly-status-report .opencode/skills/weekly-status-report && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "weekly-status-report" agent skill from https://github.com/sgharlow/claude-code-recipes/tree/main/skills/weekly-status-report into .opencode/skills/weekly-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-status-report", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
weekly-status-report- GitHub stars
- 389
- Token cost
- ~602 tokens
- SKILL.md length
- 273 words
- Files
- 2
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
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.
- Works in 5 steps: Get the raw material. Accept pasted… → Classify every item, citing the input it… → Render the report under one page:… → …
- The user says write my status report
- SKILL.md covers Steps and Constraints
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Weekly Status Report is an agent skill from sgharlow/claude-code-recipes. 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.
Its SKILL.md is about 600 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/report-from-raw-notes.md`).
It sits in Writing & Content, covering Internal communications. The repository describes itself as: 100 field-tested Claude Code recipes for knowledge workers — prompts, steps, and 6 installable graded skills.
When your agent uses it
- The user says write my status report
- Summarize my week for my manager
- Pastes a raw dump of what happened this week
Example prompts
- “write my status report”
- “weekly update”
- “summarize my week for my manager”
- “/weekly-status-report”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Get the raw material. Accept pasted notes, forwarded emails, task-tool exports, meeting
- Classify every item, citing the input it came from
- Render the report under one page: HIGHLIGHTS (3–5) → PROGRESS → BLOCKERS & RISKS (table
- Verify before presenting: every claim traces to a line of input; anything the user's raw
- Offer audience variants from the same material on request (3-bullet skip-level version,
What it can do on your machine
Read from SKILL.md and the folder at commit 9157c9a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Weekly Status Report loads about 602 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 273 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 273 words (~602 tokens).
“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.”
- name
- weekly-status-report
Files
SKILL.md and 1 other file in skills/weekly-status-report of sgharlow/claude-code-recipes.
- SKILL.md
- evals/report-from-raw-notes.md
Open the folder on GitHubat commit 9157c9a
Compare with similar skills
Weekly Status Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Weekly Status Report this skillsgharlow/claude-code-recipes | 389 | — | ~602 | Automated safety check: Pass | Custom licence | |
| Oc Statusanthropics/claude-for-legal | 9.6k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Recipe Send Team Announcementgoogleworkspace/cli | 31k | — | ~198 | Automated safety check: Pass | Apache-2.0 | |
| Program Managerborghei/Claude-Skills | 891 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Internal Communications Writeranthropics/skills | 180k | 38 repos | ~378 | Automated safety check: Pass | Apache-2.0 | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Recipe Send Team Announcement
googleworkspace/cli
Send a team announcement via both Gmail and a Google Chat space.
Program Manager
borghei/Claude-Skills
Program management for multi-project coordination, portfolio governance, dependency tracking, benefits realization, charters, and steering-committee reporting.
- Official
Internal Communications Writer
anthropics/skills
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
Sc Summary
remix-run/react-router
Summarize React Router Steering Committee meeting notes from a user-provided location in GOVERNANCE.md.
More from sgharlow/claude-code-recipes
Data Cleanup
sgharlow/claude-code-recipes
Clean and standardize messy tabular data (CSV, spreadsheet paste, system exports) into an analysis-ready dataset — consistent dates and names, typed columns, duplicates identified, missing values…
Meeting Notes To Actions
sgharlow/claude-code-recipes
Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts.
Qc Checklist
sgharlow/claude-code-recipes
Turn a process description into an operational quality-control checklist — binary pass/fail checks, acceptance criteria, critical-vs-routine tiers, and failure modes with catch-points.
Research Synthesis
sgharlow/claude-code-recipes
Synthesize multiple sources — articles, reports, notes, transcripts — into one structured brief with themes, agreements, contradictions, and gaps.
Summarize Document
sgharlow/claude-code-recipes
Summarize a long document into an executive summary, key points, and role-specific implications.
Related
Questions about Weekly Status Report
What does Weekly Status Report 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. Weekly Status Report is an agent skill from sgharlow/claude-code-recipes. 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.
When should I use Weekly Status Report?
Weekly Status Report fits situations like: the user says write my status report; summarize my week for my manager; pastes a raw dump of what happened this week.
How do I install Weekly Status Report in Claude Code?
Run `npx skills add sgharlow/claude-code-recipes --skill weekly-status-report -a claude-code`. Or copy the skill folder (skills/weekly-status-report in sgharlow/claude-code-recipes) into .claude/skills/weekly-status-report in your project. Claude Code loads it when a task matches its description.
How do I install Weekly Status Report in Codex?
Run `npx skills add sgharlow/claude-code-recipes --skill weekly-status-report -a codex`. Or copy the skill folder (skills/weekly-status-report in sgharlow/claude-code-recipes) into .agents/skills/weekly-status-report in your project. Codex loads it when a task matches its description.
Can I use Weekly Status Report in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sgharlow/claude-code-recipes --skill weekly-status-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weekly-status-report, .gemini/skills/weekly-status-report, .github/skills/weekly-status-report and .opencode/skills/weekly-status-report in your project.
What does Weekly Status Report need to run?
SKILL.md names no scripts, command-line tools or credentials: Weekly Status Report is instructions for the agent only.
Does Weekly Status Report access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Weekly Status Report safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Weekly Status Report use?
Weekly Status Report has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Weekly Status Report use?
About 602 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Weekly Status Report?
Skills that share tags, products or a category with Weekly Status Report: Oc Status (anthropics/claude-for-legal, 9.6k stars), Recipe Send Team Announcement (googleworkspace/cli, 31k stars), Program Manager (borghei/Claude-Skills, 891 stars) and Internal Communications Writer (anthropics/skills, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Weekly Status Report?
sgharlow (a GitHub user) maintains it in sgharlow/claude-code-recipes, which has 389 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on August 1, 2026.
Source: sgharlow/claude-code-recipes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.