Individual skill

status-report-pipeline

Build the pipeline that turns team updates into the rollup report without the Friday scramble — the collection format that aggregates cleanly, the altitude translation (team detail → leadership signal), and the automation-lite assembly that takes minutes. Use when asked I compile status from five teams every week, streamline our reporting chain, my Friday is spent chasing updates, or make the rollup write itself. Produces the collection design, the translation rules, the assembly routine, and the chase-elimination mechanics.

skills/status-report-pipeline/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Status Report Pipeline Skill

Somewhere in every org, a person spends Friday chasing five sub-team updates, translating them into one rollup, and reformatting everything because each team reports differently. The pipeline fixes the three leaks: *collection* (one shared format — [async-update-format](../async-update-format/SKILL.md) shape — due Thursday, in a place the assembler can harvest), *translation* (explicit altitude rules for what leadership needs: risks, asks, deltas — not activity), and *assembly* (a standing skeleton where harvested content drops into place in minutes). The chase disappears because the deadline-and-default replaces the reminder treadmill.

## What This Skill Produces

- **The collection design** — the input format, the due-time, the single harvest location, and the missing-update default
- **The translation rules** — what ascends (risks, asks, notable deltas), what compresses (the green wall), what never ascends (activity logs)
- **The assembly routine** — the rollup skeleton + the minutes-long Friday routine that fills it
- **The chase elimination** — the deadline norm, the visible-default mechanic, and the escalation that isn't the assembler's job

## Required Inputs

Ask for these if not provided:
Back to top