Business Intelligence
ericrisco/rsc-harness
A skill your agent uses when a metric (revenue, MRR, margin) needs defining once in a governed semantic layer so every dashboard, report and agent returns the same number, or when an LLM must answer…
Turn raw operational data into a weekly management report that answers exactly three questions - what changed, where is it concentrated, what needs a decision.
Install Weekly Ops Report
$ npx skills add davila7/claude-code-templates --skill weekly-ops-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install davila7/claude-code-templates weekly-ops-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/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/operations/weekly-ops-report .claude/skills/weekly-ops-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-ops-report" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/operations/weekly-ops-report into .claude/skills/weekly-ops-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-ops-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/davila7/claude-code-templates/tree/main/cli-tool/components/skills/operations/weekly-ops-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 davila7/claude-code-templates --skill weekly-ops-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install davila7/claude-code-templates weekly-ops-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-tool/components/skills/operations/weekly-ops-report .agents/skills/weekly-ops-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-ops-report" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/operations/weekly-ops-report into .agents/skills/weekly-ops-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-ops-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 davila7/claude-code-templates --skill weekly-ops-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install davila7/claude-code-templates weekly-ops-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-tool/components/skills/operations/weekly-ops-report .cursor/skills/weekly-ops-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-ops-report" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/operations/weekly-ops-report into .cursor/skills/weekly-ops-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-ops-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/davila7/claude-code-templates.git --path cli-tool/components/skills/operations/weekly-ops-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 davila7/claude-code-templates --skill weekly-ops-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install davila7/claude-code-templates weekly-ops-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-tool/components/skills/operations/weekly-ops-report .gemini/skills/weekly-ops-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-ops-report" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/operations/weekly-ops-report into .gemini/skills/weekly-ops-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-ops-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 davila7/claude-code-templates weekly-ops-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 davila7/claude-code-templates --skill weekly-ops-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-tool/components/skills/operations/weekly-ops-report .github/skills/weekly-ops-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-ops-report" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/operations/weekly-ops-report into .github/skills/weekly-ops-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-ops-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 davila7/claude-code-templates --skill weekly-ops-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 davila7/claude-code-templates weekly-ops-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-tool/components/skills/operations/weekly-ops-report .opencode/skills/weekly-ops-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-ops-report" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/operations/weekly-ops-report into .opencode/skills/weekly-ops-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weekly-ops-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-ops-report- GitHub stars
- 32k
- Token cost
- ~861 tokens
- SKILL.md length
- 411 words
- Files
- 1
- Skills in repo
- 478
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn raw operational data into a weekly management report that answers exactly three questions - what changed, where is it concentrated, what needs a decision.
- Works in 7 steps: Data-quality gate first. Before any KPI:… → Compute the KPI set agreed for the… → Apply movement thresholds. Only… → …
- The user mentions weekly report
- SKILL.md covers Workflow, Pitfalls to check explicitly and Output format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Weekly Ops Report is an agent skill from davila7/claude-code-templates. Turn raw operational data into a weekly management report that answers exactly three questions - what changed, where is it concentrated, what needs a decision. Use when the user mentions weekly report, haftalık rapor, yönetim raporu, ops review, KPI summary, or asks to summarize operational data for managers. Differentiator - contract-first reporting with plain-language findings and driver decomposition, never a chart dump.
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering OKRs and executive reporting and Plain language and style rules. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.
When your agent uses it
- The user mentions weekly report
- Asks to summarize operational data for managers
Example prompts
- “/weekly-ops-report”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Data-quality gate first. Before any KPI: duplicated rows, missing calendar days, impossible values (negative quantities, dates out of…
- Compute the KPI set agreed for the audience (typical core: revenue/volume, service level, stock cover; keep it under ~6). For each: this…
- Apply movement thresholds. Only movements beyond agreed thresholds (state defaults, e.g. |revenue| >= 5%, |service| >= 1.5 pts) become…
- Decompose every finding. A movement without its driver is not a finding. Break the moved metric by its main dimension (region, carrier…
- Write findings as sentences, one line each, using: METRIC moved X (vs baseline) - DRIVER is the main contributor (Y, ~Z% of the move)…
- Assemble in fixed order: headline KPI cards, findings list, trend view (13 weeks), attention lists (e.g. low-cover SKUs), data-quality…
- Validate before delivering. Recompute one headline KPI directly from raw rows and match it against the report value. If automation is…
What it can do on your machine
Read from SKILL.md and the folder at commit 46b4d8b. 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
Links to these hosts (documentation or services it may open):
github.com
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 Ops Report loads about 861 tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 411 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
The full file from davila7/claude-code-templates at commit 46b4d8b, republished under its MIT licence (© davila7). 411 words, ~861 tokens.
Download SKILL.mdSave it as
.claude/skills/weekly-ops-report/SKILL.md (or your agent's skills folder).- name
- weekly-ops-report
- description
- Turn raw operational data into a weekly management report that answers exactly three questions - what changed, where is it concentrated, what needs a decision. Use when the user mentions weekly report, haftalık rapor, yönetim raporu, ops review, KPI summary, or asks to summarize operational data for managers. Differentiator - contract-first reporting with plain-language findings and driver decomposition, never a chart dump.
Weekly Ops Report
A weekly report is a contract: what changed, where is it concentrated, what needs a decision. Anything that does not serve one of those three questions is decoration and gets cut.
Workflow
- Data-quality gate first. Before any KPI: duplicated rows, missing calendar days, impossible values (negative quantities, dates out of range). Fix what is safe to fix, and report every finding in a footer - an unattended report must audit its own inputs.
- Compute the KPI set agreed for the audience (typical core: revenue/volume, service level, stock cover; keep it under ~6). For each: this week, vs last week, and vs the trailing 8-week average. The baseline comparison prevents one unusual prior week from faking a trend.
- Apply movement thresholds. Only movements beyond agreed thresholds (state defaults, e.g. |revenue| >= 5%, |service| >= 1.5 pts) become findings. Reporting every wiggle trains readers to ignore the report.
- Decompose every finding. A movement without its driver is not a finding. Break the moved metric by its main dimension (region, carrier, category...) and name the concentrated segment with its share of the move.
- Write findings as sentences, one line each, using: METRIC moved X (vs baseline) - DRIVER is the main contributor (Y, ~Z% of the move) - SUGGESTED NEXT STEP. Tag each finding positive / negative / warning. Maximum five findings; if more qualify, keep the five largest by impact.
- Assemble in fixed order: headline KPI cards, findings list, trend view (13 weeks), attention lists (e.g. low-cover SKUs), data-quality footer. Same structure every week - familiarity is what makes deltas visible.
- Validate before delivering. Recompute one headline KPI directly from raw rows and match it against the report value. If automation is involved, this check runs inside the pipeline, not in someone's head.
Show full SKILL.md (118 more words)Show less
Pitfalls to check explicitly
- Week-over-week only (no baseline) - manufactures fake trends
- Unstated metric definitions - pair every service/on-time figure with its definition footnote
- Commentary drift - keep generated findings rule-based and auditable; human judgment belongs in a clearly separated commentary block, not mixed into computed statements
- Silent denominator changes (cancelled orders, excluded lines) between weeks
Output format
The report skeleton in order: title + period + generation stamp; 4-6 KPI cards with deltas; "What changed and where to look" findings (max 5, tagged); 13-week trends; attention table; data-quality footer listing every issue found.
Worked implementation (scheduled pipeline, rule-based insight engine): https://github.com/gulmezeren2-byte/auto-report-pipeline
Source: industrial-engineering-ai-skills by Eren Gulmez (MIT). The full method pack - entry skill, role agents, data-hygiene rules and artifact templates - lives there.
© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in cli-tool/components/skills/operations/weekly-ops-report of davila7/claude-code-templates.
Open the folder on GitHubat commit 46b4d8b
Compare with similar skills
Weekly Ops 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 Ops Report this skilldavila7/claude-code-templates | 32k | — | ~861 | Automated safety check: Pass | MIT | |
| Business Intelligenceericrisco/rsc-harness | 174 | — | ~2.5k | Automated safety check: Pass | MIT | |
| SEO Content Writerthatrebeccarae/claude-marketing | 162 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Novel Outlineeternityspring/shuohao-skills | 4.3k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Reading Guidechingswy/Skill-Research-Figure | 178 | — | ~4.5k | Automated safety check: Pass | None | |
| Exec Summarymvschwarz/openrig | 6.2k | — | ~723 | Automated safety check: Pass | Apache-2.0 |
Similar skills
SEO Content Writer
thatrebeccarae/claude-marketing
SEO-optimized content creation with brand voice analysis and platform-specific frameworks.
Novel Outline
eternityspring/shuohao-skills
把一本小说改编成短剧大纲五件套：改编说明、人物表、爽点表、分集梗概、资产清单， 产出 outline.json + Markdown + 单页评审报告（KPI 带、关键决策、爽点时间轴、调度矩阵、场景概览、质量门）。
Reading Guide
chingswy/Skill-Research-Figure
Structured learning navigator for blog posts and articles. An agent skill from chingswy/Skill-Research-Figure.
Exec Summary
mvschwarz/openrig
Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.
Okr
Prismer-AI/PrismerCloud
Draft and track a strategic OKR charter — turn a human's plain-language goal into ONE Objective + 2-5 measurable Key Results, link existing tasks, and route the commit to a human sponsor.
More from davila7/claude-code-templates
All 478 skills in this repoPerplexity Web Search
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Neuropixels Data Analysis
davila7/claude-code-templates
Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.
Scientific Venue Templates
davila7/claude-code-templates
Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
CAPA Officer
davila7/claude-code-templates
Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.
Fda Consultant Specialist
davila7/claude-code-templates
Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.
Related
Categories
Questions about Weekly Ops Report
What does Weekly Ops Report do?
Turn raw operational data into a weekly management report that answers exactly three questions - what changed, where is it concentrated, what needs a decision. Weekly Ops Report is an agent skill from davila7/claude-code-templates. Turn raw operational data into a weekly management report that answers exactly three questions - what changed, where is it concentrated, what needs a decision.
When should I use Weekly Ops Report?
Weekly Ops Report fits situations like: the user mentions weekly report; asks to summarize operational data for managers.
How do I install Weekly Ops Report in Claude Code?
Run `npx skills add davila7/claude-code-templates --skill weekly-ops-report -a claude-code`. Or copy the skill folder (cli-tool/components/skills/operations/weekly-ops-report in davila7/claude-code-templates) into .claude/skills/weekly-ops-report in your project. Claude Code loads it when a task matches its description.
How do I install Weekly Ops Report in Codex?
Run `npx skills add davila7/claude-code-templates --skill weekly-ops-report -a codex`. Or copy the skill folder (cli-tool/components/skills/operations/weekly-ops-report in davila7/claude-code-templates) into .agents/skills/weekly-ops-report in your project. Codex loads it when a task matches its description.
Can I use Weekly Ops 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 davila7/claude-code-templates --skill weekly-ops-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-ops-report, .gemini/skills/weekly-ops-report, .github/skills/weekly-ops-report and .opencode/skills/weekly-ops-report in your project.
What does Weekly Ops Report need to run?
SKILL.md names no scripts, command-line tools or credentials: Weekly Ops Report is instructions for the agent only.
Does Weekly Ops Report access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Weekly Ops 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 Ops Report use?
Weekly Ops Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Weekly Ops Report use?
About 861 tokens (SKILL.md is roughly 3.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 Ops Report?
Skills that share tags, products or a category with Weekly Ops Report: Business Intelligence (ericrisco/rsc-harness, 174 stars), SEO Content Writer (thatrebeccarae/claude-marketing, 162 stars), Novel Outline (eternityspring/shuohao-skills, 4.3k stars) and Reading Guide (chingswy/Skill-Research-Figure, 178 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Weekly Ops Report?
davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,483 GitHub stars. The repository holds 478 skills in this directory. The repository was last updated on October 9, 2026.
Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.