Run any Skill in Manus with one click

ops-report

Stars3

Forks0

UpdatedJuly 10, 2026 at 01:50

Scheduled daily executive operations report for a parcel fulfillment network. Auto-pulls shipment-container and dock/dwell spreadsheets from Google Drive and dock-activity emails from Gmail, asks the duty manager for the handful of numbers that live behind interactive dashboards, then assembles a three-section executive summary with a KPI header and color-coded dwell alerts.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

trevhud

trevhud/rote

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	ops-report
description	Scheduled daily executive operations report for a parcel fulfillment network. Auto-pulls shipment-container and dock/dwell spreadsheets from Google Drive and dock-activity emails from Gmail, asks the duty manager for the handful of numbers that live behind interactive dashboards, then assembles a three-section executive summary with a KPI header and color-coded dwell alerts.

Daily Executive Operations Report

Generate the daily executive operations report for the parcel fulfillment network. This report covers three sections.

Data sources to auto-pull:

1. Shipment Containers (Google Drive MCP — read_file_content) File ID: 1ExampleShipmentContainersFileId00000000000 Parse the facility summary table with COMPLETION % column. Report active, loaded, staged, shipped counts and completion % by site. Flag any site below 75% completion. Show week-over-week trend if available.

2. Dock Pending Log (Google Drive MCP — read_file_content) File ID: 1ExampleDockPendingLogFileId0000000000000000 Count all rows where Resolved = FALSE. Break down by site (EAST1, WEST2, etc.) and issue type (PO Number, Pallet/Piece Count Discrepancy). Report total open count.

3. Dock Activity Emails (Gmail MCP — search_threads) Search query: label:dock-activity newer_than:1d Count Approved vs. Requested appointments. Flag any outstanding requests not yet approved.

4. Open Dwell Tickets (Google Drive MCP — read_file_content) File ID: 1ExampleDwellTicketLogFileId0000000000000000 Tab: Dwell Log - Form Responses. Filter rows where Open/Closed column = "Open". Report each open ticket with: date, facility, # packages, client impact, carrier impact, issue description. Flag packages >= 25 (Missort Warning), >= 41 (Missort Alert), carrier >= 80 (Possible Misload Alert).

Manual data to request from user:

After pulling the above, ask the duty manager to provide:

Dock Appointment Completion (from the dock scheduler's appointment view for the prior day): count of Green (Complete), Red (No Call/No Show), Grey (Canceled), and any other color (Non-Compliant). Non-Compliant must be escalated.
Sorter Metrics (for sites with automated divert lines): volume output and fail rate % per site. Flag if fail rate > 5% (action needed) or if volume dropped >15% day-over-day (divert adjustment may be needed).
Current Dwell (from the BI dashboard, filtered by site): shipper/brand name, carrier, site, # orders/packages dwelling. Apply thresholds: Brand 25-40 = Missort Warning (light red), 41+ = Missort Alert (bright red). Carrier 80+ missing = Possible Misload Alert (darkest red).

Report format:

Produce an executive-level summary with:

KPI header: Active sites, Dock Pending count, Avg Completion %, Open Dwell Tickets
Section 1 — Dock Compliance: Appointment tiles + Gmail summary + Pending Log table
Section 2 — Missort & Loss: Sorter metrics + container flow table by site with completion %
Section 3 — Dwell: BI-dashboard dwell alerts (color-coded) + Open Dwell Impact Log tickets

Also remind the duty manager to open the live artifact "ops-report" for the interactive version with charts. The artifact auto-refreshes Sheets and Gmail data on every open.

More from this repository

same repository

rote-graduate

trevhud/rote

Analyze an Anthropic-style skill bundle (SKILL.md + references) and produce a graduation plan that separates deterministic work into extracted Python modules, LLM-as-judge work into typed DSPy/BAML signatures, agentic work into bounded agent loops, and human-in-the-loop gates into durable suspend points. Emit the whole pipeline as a runtime-agnostic intermediate representation (pipeline.yaml) plus runnable code for a target workflow engine (Temporal, Inngest, Restate, or plain async) via pluggable adapters. Trigger phrases: "graduate this skill", "turn this skill into a workflow", "harden this skill", "extract deterministic parts of this skill", "compile skill to pipeline", "make this skill reliable in production", "analyze skill for codification", "emit this skill as a temporal workflow", "rote this skill".

2026-07-103

deal-monitor

trevhud/rote

Scheduled morning dashboard for a fulfillment brokerage's deal pipeline. Pulls the #deal-intake Slack channel and Gmail quoting threads, classifies each warehouse-quoting email thread into a 6-step pipeline, scores new (unquoted) opportunities against the deal-scoring rubric, and renders a self-contained three-tab HTML dashboard (New Opportunities | Quoting | Closed).

2026-07-103

serve

trevhud/rote

Wire a graduated rote pipeline up as an MCP tool so Claude can trigger the deployed workflow directly. Use when the user says "register my graduated pipeline", "serve my pipelines over MCP", "trigger the workflow from Claude", "hook the pipeline up to Claude", or asks what to do after `rote graduate` and deployment. Covers `rote register` and `rote serve` plus the `claude mcp add` wiring.

2026-07-033

graduate

trevhud/rote

Graduate (compile) an Anthropic-style skill — a directory with a SKILL.md and optional references/ — into a deterministic, runnable workflow via the rote CLI. Use when the user says "graduate this skill", "compile this skill", "make this skill deterministic", "make this skill faster/cheaper", "turn this skill into a workflow", "turn this skill into code", "harden this skill for production", or complains that a skill is slow, expensive, or unreliable as a background job. Output: a pipeline.yaml IR, extracted code modules, typed LLM-judge signatures, and runtime code for Temporal, Cloudflare Workflows, or DBOS.

2026-07-033

bdr-outreach

trevhud/rote

End-to-end BDR outreach campaign workflow. Use when running pharma/biotech outreach campaigns: finding leads via ZoomInfo, enriching conference attendee lists, uploading contacts to HubSpot CRM, managing lists, running exclusion checks (do-not-contact, recently emailed, active sequence), creating/editing sales email templates, and generating pre-enrollment reports. Trigger phrases: "outreach campaign", "BDR campaign", "find contacts for [drug]", "pull leads for [condition]", "who should we reach out to at [company]", "run a lead search", "find RWE contacts", "filter conference list to pharma", "enrich conference attendees", "add contacts to hubspot", "upload contacts", "campaign enrollment", "hubspot sequence", "do not contact list", "check if recently emailed", "edit sequence template", "sales template", "sequence email", "hubspot outreach", "sales sequence", "build outreach list from conference".

2026-04-073

name	ops-report
description	Scheduled daily executive operations report for a parcel fulfillment network. Auto-pulls shipment-container and dock/dwell spreadsheets from Google Drive and dock-activity emails from Gmail, asks the duty manager for the handful of numbers that live behind interactive dashboards, then assembles a three-section executive summary with a KPI header and color-coded dwell alerts.

Daily Executive Operations Report

Generate the daily executive operations report for the parcel fulfillment network. This report covers three sections.

Data sources to auto-pull:

3. Dock Activity Emails (Gmail MCP — search_threads) Search query: label:dock-activity newer_than:1d Count Approved vs. Requested appointments. Flag any outstanding requests not yet approved.

Manual data to request from user:

After pulling the above, ask the duty manager to provide:

Dock Appointment Completion (from the dock scheduler's appointment view for the prior day): count of Green (Complete), Red (No Call/No Show), Grey (Canceled), and any other color (Non-Compliant). Non-Compliant must be escalated.
Sorter Metrics (for sites with automated divert lines): volume output and fail rate % per site. Flag if fail rate > 5% (action needed) or if volume dropped >15% day-over-day (divert adjustment may be needed).
Current Dwell (from the BI dashboard, filtered by site): shipper/brand name, carrier, site, # orders/packages dwelling. Apply thresholds: Brand 25-40 = Missort Warning (light red), 41+ = Missort Alert (bright red). Carrier 80+ missing = Possible Misload Alert (darkest red).

Report format:

Produce an executive-level summary with:

KPI header: Active sites, Dock Pending count, Avg Completion %, Open Dwell Tickets
Section 1 — Dock Compliance: Appointment tiles + Gmail summary + Pending Log table
Section 2 — Missort & Loss: Sorter metrics + container flow table by site with completion %
Section 3 — Dwell: BI-dashboard dwell alerts (color-coded) + Open Dwell Impact Log tickets

Also remind the duty manager to open the live artifact "ops-report" for the interactive version with charts. The artifact auto-refreshes Sheets and Gmail data on every open.