What do I need to use Status Report Pipeline?

The chain's shape; What the audience actually reads; The inputs' current state; The authority backdrop.

Is Status Report Pipeline free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Status Report Pipeline

Q: How do I know the Status Report Pipeline output is good?

The skill verifies itself against its own quality checks: Inputs share one format in one harvestable place with a due-time; Missing updates surface visibly instead of triggering chases; Translation rules are altitude-based, with the green wall compressed; The skeleton is standing and assembly is timed under target.

🔵 Stable🕐 updated 2026-07-19 🔷 SkillSpec L3 pm-cowork

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸The chain's shape — how many inputs, from whom, to whom, at what cadence; and the current pain minutes (the before-number the pipeline gets judged against)

▸What the audience actually reads — ask them, or read the replies: which sections get questions? The rollup optimizes for the read parts and compresses the skipped ones

▸The inputs' current state — five formats? Prose emails? The collection format converges them, and the contributors need the *why* (less rework for everyone, including them)

▸The authority backdrop — can the assembler set a deadline with teeth, or does the default-mechanic have to do the enforcement alone?

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Inputs share one format in one harvestable place with a due-time

✓Missing updates surface visibly instead of triggering chases

✓Translation rules are altitude-based, with the green wall compressed

✓The skeleton is standing and assembly is timed under target

✓The synthesis sentence survived as the human's job

⚠️ What it refuses to do

Do not chase — the visible default is the enforcement; chasing trains everyone that deadlines are suggestions

Do not forward five formats upward — convergence at collection or chaos at assembly

Do not ascend the green wall — leadership reads exceptions; routine is one line

Do not summarize activity into the rollup — deltas and risks; the diary stays below

Do not automate away the synthesis — the paragraph is the report; the pipeline just clears its runway

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="status-report-pipeline"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Status Report Pipeline is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog