SkillAgentSearch skills...

morning-plant-pulse

Runs the overnight chain that has the morning production report waiting before anyone asks for it: joins last night's planning, production and maintenance exports, flags the mismatched keys, then computes output against plan, OEE with its three components, downtime ranked two ways, priced losses and…

Install / Use

npx skills add anthropics/claude-plugins-official --skill morning-plant-pulse

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

98/100

Supported Platforms

Universal

Tags

Our assessment of morning-plant-pulse

morning-plant-pulse scores 98/100 on our quality scale, 73rd of 4,698 Development & Engineering skills we index (top 2%).

Its SKILL.md is 21 KB long, well organised into 11 sections with 2 code examples: 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
18/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so morning-plant-pulse is actively maintained.
  • 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.

morning-plant-pulse compared with similar skills

All 4 of these similar skills score higher than morning-plant-pulse; compare them before choosing.

SkillScoreStarsUpdatedFormat
morning-plant-pulse (this skill)by anthropics9847.2k3d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install morning-plant-pulse?
Run npx skills add anthropics/claude-plugins-official --skill morning-plant-pulse. The install tabs above show the steps for each supported agent.
Which AI agents does morning-plant-pulse 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 morning-plant-pulse 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 morning-plant-pulse still maintained?
The repository was last updated 3 days ago, so morning-plant-pulse is actively maintained.

name: morning-plant-pulse description: "Runs the overnight chain that has the morning production report waiting before anyone asks for it: joins last night's planning, production and maintenance exports, flags the mismatched keys, then computes output against plan, OEE with its three components, downtime ranked two ways, priced losses and the exceptions needing a decision. Stores a record per production day and keeps one Operations Command Center dashboard per site up to date, with a 14 and 30 day trend. Safe to run unattended. Use when someone says "run the morning pulse," "do the overnight report," "morning plant pulse," "update the operations dashboard," or schedules the daily production run." compatibility: "Requires none. Chains data-consolidate and daily-production-report, then publishes the site's Operations Command Center dashboard to the Claude artifact store where the artifact tools exist, else offers the page in the conversation. Reads M365 exports, NetSuite or Infor M3, and a CMMS connector where connected; runs on the export folder alone. Writes to no system of record, so it is safe to schedule. Asks nothing, is idempotent, reports its own gaps."

Morning Plant Pulse

Chain 3. data-consolidate → daily-production-report → publish.

The only scheduled chain, and the only one with no approval gate. Those two facts are the same fact: it reads, it produces a page, and it writes to no system of record. The dashboard it publishes lives in the user's own Claude artifact store, which is not a system of record either. That is precisely why it is safe to run unattended, and why no other chain in this build should ever be scheduled.

The page is rebuilt overnight so it exists before the morning meeting. A supervisor otherwise spends sixty to ninety minutes assembling it by hand out of the same four or five exports. The first run creates one dashboard per site; every later run updates that same dashboard, so nobody has to save over yesterday's page.

Quick start

→ Join last night's exports; flag mismatched keys by class
→ Compute output vs plan, OEE with its three components shown separately
→ Downtime ranked BOTH ways: by minutes and by frequency
→ Price the losses. Week-over-week movers come from the stored day records
→ Write the day record, keyed <site>_<YYYY-MM-DD>. Missing export? data_complete: false
→ Find the dashboard: stored URL, then exact title. Neither? Create it
→ Say "updated" ONLY when the publish returned a URL in this run
→ Can't publish? Page saved to pulse-output/ + "the dashboard was not updated"
→ Reply: ~150-word summary naming the page; full page in the reply only if nothing could be written
→ Export did not land? STILL RUN. Gap at the top, gap in the trend, never a zero
→ Ask nothing. There is nobody there at 4am
→ Idempotent: a re-run overwrites that day's record on the same dashboard

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 | |---|---|---| | Planning, production and maintenance exports | The M365 export folder | CSV/XLSX | | Standard cost, open work orders | The ERP (NetSuite or Infor M3) | Connector | | Maintenance work orders in progress | CMMS | CMMS connector, else the maintenance export | | Stored day records, for the trend and week-over-week | The dashboard's own pulse_days collection | ArtifactData query, per ../../shared/contracts/pulse-day-record.md | | The dashboard's URL | The ## Dashboards line on the Open work page, then an exact-title lookup | Open work page, Artifact list | | Source clocks, shift pattern, day boundary | ## Plant context | Config |


The three steps

First, run the compute engine. Steps 1 and 2 are done in code that ships with this skill, so every run computes the same numbers the same way:

python3 -I <this skill's folder>/scripts/pulse_compute.py --exports <export folder> \
  --out pulse-output [--day YYYY-MM-DD] [--profile <profile_path>] [--rates <rates_path>]

It applies the ladder, the eight classes and the integrity flags of data-consolidate, and the OEE, ranking, pricing and exception rules of daily-production-report, and writes figures.csv (the figures block, one row per number with its filter), pulse_model.json (everything the page shows, already computed) and day_records.json (one day record per covered day). Build the page from pulse_model.json and quote figures.csv. Never recompute, retype or round a number it holds. The judgment stays yours: the wording, which exceptions are significant, the reschedule move, the publish. What each key holds is reference/compute-engine.md. If the engine cannot run (no code execution) or exits non-zero, do steps 1 and 2 as written below and say which happened; never mix the two.

1. Join the exports through data-consolidate, on the records the plant already has, with mismatched keys flagged by class.

2. Compute the report through daily-production-report: output against plan, equipment losses ranked by minutes and by frequency, priced in dollars, and the exceptions that need a decision today. Week-over-week movers come from the stored day records, read at the start of step 3 before the page is built, never from a prior page. The pulse hands that history to step 6 of daily-production-report.

3. Publish the dashboard. Per ../../shared/live-dashboard.md, which names every tool call. In order:

  1. Find the dashboard. The ## Dashboards line on the Open work page first; then Artifact list for the exact title "<Site>: Operations Command Center"; only when both find nothing does this run create it. A scheduled run starts with no memory of earlier runs, so it looks every time.
  2. Build the day record for the production day, every field, per ../../shared/contracts/pulse-day-record.md, keyed <site>_<YYYY-MM-DD>. A missing export makes it data_complete: false with the gap named. Its metrics are null, never zero.
  3. Existing dashboard: read it, query pulse_days, set the day record, compute the trend from the stored records in code, then publish to the same url. First run: back-fill (below), publish with capabilities: {db: {}} and the fixed title, batch the records against the new URL, write the URL to the ## Dashboards line on the Open work page, then open the dashboard so it is what the person sees.
  4. Render the short Operations page, after the publish so it can link to the dashboard: python3 -I <this skill's folder>/scripts/render_short.py --out pulse-output [--full-page-url <url>]. It writes operations-short-<site>-<day>.html beside the figures and checks itself; on a failed check it writes nothing, and the reply says so. It is a separate page from the dashboard and never replaces it. Per reference/short-page.md.
  5. Report it, as the last line of the run: "Updated Fairview: Operations Command Center, <url>. Private to you until you share it." Or the fallback: the page saved as pulse-output/operations-<site>-<day>.html (in the reply only when no file can be written), its placement line, and "The dashboard was not updated: [reason]."

Say "updated" only when the publish returned a URL in this run. Never "shared," never "scheduled," never "posted." The dashboard is private until the user shares it, and the pulse never shares it. A run that says "updated" without a URL from this run has told the meeting to trust a page nobody rebuilt.

Only the pulse publishes the Operations dashboard. daily-production-report run alone, and Chain 4, keep offering their page in the conversation. Two dashboards showing the same numbers is how a meeting ends up arguing about which one is right.

Back-fill on the first run only. When the exports cover several production days, the run that creates the dashboard writes a record for every day the planning, production and downtime exports fully cover, so the trend opens with history. A day they only partly cover is written data_complete: false, so it shows as a gap rather than as a bad day. Later runs write their own day.

What the page holds, panel by panel, is reference/operations-dashboard.md.


What "safe to run unattended" actually requires

Three properties. Each is a real constraint, not a nicety.

It asks nobody anything. There is no one at 4am to answer. Where an attended run would ask which date range or which of several exports to use, the unattended run takes the production-day range from the ## Plant context block and says which it used. With no Plant context at all, it uses the latest complete production day present in the exports, says so in the freshness banner, and lists no plant profile among the gaps. It never blocks on the missing profile, and never picks today's date, which has no data. A run that blocks on a question produces nothing, and nothing is worse than a partial report, because the gap is only discovered at the meeting. The publish step asks nothing either: where two artifacts carry the exact title, it uses the stored URL's, or the most recently updated, and names both.

Asking nobody does not mean deciding for them. Where plan and output spell a part differently, the unattended run neither drops the row nor joins it silently. It shows the variance labelled provisional, shows both spellings verbatim, and lists each normalization it relied on as proposed, awaiting approval, for whoever reads the page to accept or reject. Normalizations on the profile's ### Approved normalizations list are used as they stand; each overnight run rebuilds the dataset, so that list is what carries a yes from one night to the next. This is not a gate — nothing is applied and nothing is written — and the rule is ../../shared/approval-gates.md, When nobody is there to ask.

A list of data problems holds problems, and it is built by class number. Take the classified mismatches from step 1 and route each class before any row is numbered:

| Class | Where it goes | |---|---| | 1 orphan, 2 format drift, 3 leading zeros, 4 revision suffix, 5 case and whitespace, 8 duplicate key | The numbered Data problems table, and its count | | 7 date window | The coverage line in the freshness banner. Not a numbered row | | 6 genuine one-sided record | "Checked, nothing wrong", a separate block after the table. Never a row number, never in the count | | 6 with contradicted_by set | The numbered Data problems table, as one-sided, contradicted by the named record, and its count. Never "Checked, nothing wrong" |

A record decides its class from its own type and dates, never from a part number someone recognises. A Class 6 record that appears in the table and in the recap has still been counted as a problem; it appears in the recap only. A duplicate key is counted by the rows that collide at the tab's grain, from the query (work order, shift and production day): if WO-88201 has three rows, and two of them (509 and 480 good, both 07:00) are the duplicate; the 95 on the 23:00 shift is its own shift. Say both numbers, and the figures block shows the filter. And a downtime record from breakdown-diagnosis with no safety_flagged is blocked: listed first under "Blocked — safety status unknown," held out of both rankings, the totals and the pricing. MES and historian rows are untouched. Both rules are ../daily-production-report/SKILL.md, steps 7 and 8. The day record carries the same split: data_problems_count is the table's count, and a blocked record is outside every downtime figure stored.

It is idempotent. A r

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars47.2k
CategoryDevelopment
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