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.
npx skills add mohitagw15856/pm-claude-skills --skill status-report-pipeline --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ## Re
- What This Skill Produces
- Required Inputs
- Framework: The Pipeline Rules
- Output Format
- Collection
- Translation Rules
- The Skeleton + Routine
- Chase Elimination
- Quality Checks
- Anti-Patterns
What does the status-report-pipeline skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill status-report-pipeline --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.