SkillAgentSearch skills...

daily-production-report

Produces the morning production report: output against plan by line, cell and product; OEE with availability, performance and quality shown separately; the downtime log ranked both by minutes and by frequency; scrap and downtime priced in dollars; week-over-week movers; and the exceptions needing a…

Install / Use

npx skills add anthropics/claude-plugins-official --skill daily-production-report

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

96/100

Category

Marketing

Supported Platforms

Universal

Tags

Our assessment of daily-production-report

daily-production-report scores 96/100 on our quality scale, 41st of 642 Marketing skills we index (top 7%).

Its SKILL.md is 27 KB long, well organised into 20 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 47,209 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
17/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so daily-production-report is actively maintained.
  • Our last check on 2026-11-14 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-14. Automated pattern scan on 2026-11-14. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

daily-production-report compared with similar skills

All 4 of these similar skills score higher than daily-production-report; compare them before choosing.

SkillScoreStarsUpdatedFormat
daily-production-report (this skill)by anthropics9647.2k3d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install daily-production-report?
Run npx skills add anthropics/claude-plugins-official --skill daily-production-report. The install tabs above show the steps for each supported agent.
Which AI agents does daily-production-report work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is daily-production-report safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is daily-production-report still maintained?
The repository was last updated 3 days ago, so daily-production-report is actively maintained.

name: daily-production-report description: "Produces the morning production report: output against plan by line, cell and product; OEE with availability, performance and quality shown separately; the downtime log ranked both by minutes and by frequency; scrap and downtime priced in dollars; week-over-week movers; and the exceptions needing a decision today. For each significant exception it drafts a specific reschedule or changeover move with its consequences traced, never a re-optimised day. Reads the consolidated dataset and leads with data freshness. When the plant has a floor plan on file, or attaches one, it also draws each machine's OEE, availability and downtime on a schematic of the floor. Use when someone says "morning report," "production report," "how did we do yesterday," "what's our OEE," "downtime report," "what's late," or "what do I take into the production meeting."" compatibility: "Requires a consolidated dataset from data-consolidate. Reads the ERP (Oracle NetSuite or Infor M3) for standard cost and open work orders, and a CMMS connector (Limble is the worked example) for maintenance work orders in progress, when connected. Runs on export-only data. Writes nothing to any system of record."

Daily Production Report

Every plant runs a morning production meeting, and somebody spends 60 to 90 minutes before it assembling the same report by hand out of the same four or five exports. This is that report.

Chain 3 runs this overnight, so the page exists before anyone asks for it. The run is built to be safe unattended — it asks nothing, it is idempotent, and it reports its own gaps. The trigger is the host's, not the plugin's: see ../../shared/scheduling.md. Never tell a user the report has been scheduled. That is the clearest demonstration of the plugin's concept, and it is why the run must be idempotent — a re-run rewrites the same report for that production day rather than producing a second one.

Quick start

→ Confirm freshness; if last night's export didn't land, lead with that
→ Output against plan by line, cell, product, with variances
→ OEE per asset or line, three components always shown separately
→ Downtime ranked by minutes and by frequency, both
→ Price scrap and downtime in dollars, with the rate assumption stated
→ Week-over-week movers from history: the pulse's day records, or the exports
→ Fold in any breakdown diagnoses
→ Exceptions, each with its impact on a commitment
→ One traced reschedule move per significant exception, drafted not applied
→ Floor view: each machine's figures drawn where it sits; set up once from a
  floor plan, confirmed by a person, saved on the plant setup page
→ Page saved to report-output/; the reply is a ~150-word summary naming it
→ Run alone: never publishes. End with the placement line, "save it over yesterday's"

Inputs

First, find the plant setup: from the task's own folder (never cd into the plugin), run python3 -I <this skill's folder>/../../shared/scripts/plant_setup.py find, do its setup_page_first step, then read the profile at profile_path and any rate at rates_path, per ../../shared/replies.md.

| Input | Source | Form | |---|---|---| | Consolidated dataset | data-consolidate | Primary input. ../../shared/contracts/consolidated-dataset.md | | New breakdown diagnoses | breakdown-diagnosis | ../../shared/contracts/downtime-record.md | | Production plan / schedule | Planning export to the M365 folder | CSV / XLSX | | Actual output, good and scrap | MES export to the M365 folder | CSV / XLSX | | Downtime events with reason codes | MES or historian export | CSV | | Standard cost per part | The ERP. Infor M3 gives none (../../shared/erp-connectors.md): the profile's cost read order applies | Connector | | Open work orders and due dates | The ERP | Connector | | Maintenance work orders in progress | CMMS | CMMS connector, else the maintenance export | | Stored day history, inside Chain 3 only | morning-plant-pulse | ../../shared/contracts/pulse-day-record.md | | Floor layout (optional) | The ### Floor layout - <site> section of the plant profile at profile_path (the plant setup page) | ../../shared/contracts/floor-layout.md | | Floor plan (optional, setup only) | A PDF or image the user attaches | Read once, in the setup turn of step 9a; never stored | | OEE thresholds (optional) | The plant profile's OEE thresholds line | Defaults apply, labelled not confirmed, when absent |


Workflow

Step 1 — Confirm freshness

Confirm freshness via data-consolidate — the data quality report and each row's as_of. If last night's export did not land, say so at the top of the report, directly under any safety block. Nothing about data age goes above a safety-flagged record, not even a one-line note.

A source whose timestamps run later than now is flagged future_timestamp: say its dates can't be trusted and give it no age. A production report built on stale data is worse than no production report, because it gets believed and acted on. Never silently reuse yesterday's data. The rule is ../../shared/absent-is-not-zero.md.

On reading both the dataset and the raw exports. The dataset is the primary input — it carries the freshness picture and the classified key mismatches. The plan, output and downtime exports give rows at their native grain. Where the two disagree on a count, report both and name which is which; a discrepancy is a finding about the export, not a number to choose between. See What this dataset is authoritative for in ../../shared/contracts/consolidated-dataset.md.

Step 2 — Output against plan

By line, cell and product, with variances. Use the plant's own word for the organizational unit, from the ## Plant context block.

Where plan and output spell a part differently, do not match them silently, and do not refuse to match them. Run on raw exports, the plan says PN-4471-B and the MES says 4471B. Dropping the row makes output against plan look broken; joining it without a word applies a fix nobody approved. So:

  1. Use any normalization already approved — in the consolidated dataset, or on the profile's ### Approved normalizations list — as it stands.
  2. For every other match that depends on a normalization, show the variance labelled provisional, and beside it each normalization it rests on, with both spellings verbatim — 4471B → PN-4471-B, format drift.
  3. Ask for a yes on each, the same "apply?" gate data-consolidate uses. Until then the rows stay provisional, in the table and in any total built on them.

An unattended run cannot ask: it carries the same provisional table and lists the normalizations as proposed, awaiting approval. Per ../../shared/approval-gates.md.

Step 3 — Compute OEE

Per asset or line, with the three components always shown separately. Read reference/oee.md first — the denominators carry real traps, and a missing component is never substituted with 1.0.

State the quality convention on every run, as a line under the OEE table: "quality = good ÷ (good + scrap)". Only when the export has no rework column does the line continue: "no rework column, so first-pass yield could not be applied." Where the export does carry rework, quality is first-pass yield, good ÷ (good + scrap + rework), and the line says so instead. Never print the no-rework caveat against an export that has the column.

Step 4 — Build the downtime log

Ranked two ways, both always shown: by total minutes, and by frequency.

Other never appears in a cause ranking. Before ranking by reason code, count the events and minutes coded Other or left blank and state that share as a finding of its own: "18 of 39 events, 46%, carry no usable reason code." Then rank the named codes only, with the caveat that the picture is incomplete by that share. A table with Other in row 1, priced, tells the meeting the plant's biggest problem is a word, and it is the single most common way this report has been wrong.

A downtime row that ends before it starts, or whose duration disagrees with its own start and end, has no trustworthy minutes. It carries end_before_start or duration_mismatch from the dataset; reading the export raw, test it in code. Hold its minutes out of every total and the minutes ranking, count it as an event, and state the exclusion beside the ranking with the row: "DOOSAN-PUMA-07, 4 Aug: ends 14:01 after starting 14:05, 56 minutes stated, not counted." Never pick a figure for it.

These describe different problems. One long outage and forty chronic small stoppages can total the same minutes, and the second is usually the more fixable of the two. A single ranking hides whichever one it does not sort by.

Step 5 — Price the losses

Scrap × standard cost. Downtime × the plant's configured cost-per-hour.

Scrap dollars are an estimate at standard cost, and say so where they are printed ("$180 scrap, estimated at standard cost"): they are exposure, not a booked loss. With no rate, downtime dollars are unknown, never $0.

"47 parts scrapped" does not land in a production meeting. "$8,400 of scrap, 71% of it on one part number" does, and it is the same data multiplied by a cost.

Every quantity in the priced-losses table is the figures-block row, printed. The scrap count beside a part's dollar figure is the same number the dollar figure was multiplied from; a table that says 155 units against a figure computed from 62 has been typed, not printed. Build the table from the block, per ../../shared/computed-figures.md, and never from memory of it.

A part whose scrap is recorded in a different unit from its standard cost is unpriced, not converted. Scrap in box12 against a cost per each has no dollar figure until the plant says what a box holds: report the quantity in its own unit, mark the dollar cell "unpriced — unit conflict," and name the conflict. Never price it two ways ("$5,465 if singles, $65,584 if boxes of 12"): both numbers are guesses, and the larger one is the one that gets repeated. The rule is the same one data-consolidate applies at the join.

Always state the assumption behind the downtime rate. Resolve it per ../../shared/secret-config.md, Resolving a rate — MFG_DOWNTIME_COST_PER_HOUR if set, then a confirmed rate in the plant profile, then a placeholder there, labelled "placeholder rate — not confirmed" — and name the source next to the priced downtime. This is an unattended overnight run, so there's no one to ask. Without a rate in either route, price scrap only and say plainly that downtime is unpriced, per ../onboarding/reference/config-profile.md.

Step 6 — Week-over-week movers

Compare against earlier production days and surface the biggest improvements and deteriorations. The history comes from one of two places, never from a prior page. Inside Chain 3, morning-plant-pulse hands over the stored day records. Run alone, this skill compares only against earlier days the exports in front of it cover, and says that is the basis. Trend beats snapshot: a 68% OEE that was 61% last week is a different conversation from one that was 74%.

Compare all four: output against plan, OEE by component, downtime minutes and scrap dollars. A movers section that shows only OEE has missed the number the plant manager looks at first. Each mover names the metric, last week's value, this week's, and the change.

With no earlier day to compare against, skip the section rather than showing an empty comparison.

Step 7 — Fold in breakdown diagnoses

Any downtime record from breakdown-diagnosis appends into the downtime log and the exceptions, with no transformation step. Its contract governs how — including that an ongoing outage has a null duration rather than zero, that a safety flag leads with its safety_reason, and that an advisory

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars47.2k
CategoryMarketing
Updated3d ago
Forks4.9k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions