manifest-reader

Aggregate sub-agent manifest files into structured summary reports.

12|4|Updated Mar 14, 2026

Search Tags:#debugging #agents #aggregation #manifest #report #summarize

Ready to run

npx skills add https://github.com/mshadmanrahman/pm-pilot --skill manifest-reader

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: manifest-reader
Source: https://github.com/mshadmanrahman/pm-pilot/tree/main/skills/productivity/manifest-reader
Command: npx skills add https://github.com/mshadmanrahman/pm-pilot --skill manifest-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly aggregate and summarize results from sub-agent manifest files to produce a clear, auditable briefing.

Core Features & Use Cases

Aggregation: Read manifests from .claude/manifests/ and extract key fields from frontmatter (task, status, agent) and body findings.
Summarization: Generate a concise report that highlights total counts, statuses, and notable findings or errors.
Use Case: After an orchestrator wave or parallel agent runs, produce a session recap or debugging digest.

Quick Start

Run the manifest reader after an orchestration wave to generate a structured summary of all sub-agent results.

Frequently Asked Questions about manifest-reader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I summarize sub-agent manifest files after parallel agent runs?▼

To summarize sub-agent manifest files after parallel agent runs, you can aggregate frontmatter fields like task, status, and agent to generate a concise, auditable report of session results and errors.

What is the best way to generate an auditable report from orchestrator wave manifests?▼

Generating an auditable report from orchestrator wave manifests involves parsing frontmatter fields and extracting body findings, errors, and modified files to deliver a structured summary with total counts and statuses.

How do I aggregate debugging results from multiple sub-agent manifests?▼

Aggregating debugging results from multiple sub-agent manifests requires reading files from the .claude/manifests/ directory and parsing key fields to produce a structured debugging digest of notable findings.

Can I extract task status and modified files from frontmatter for a session recap?▼

Yes, you can extract task status, agent information, and modified files from manifest frontmatter to automatically produce a structured session recap highlighting total counts and notable findings.

Does manifest aggregation work without external dependencies for session recaps?▼

Manifest aggregation works without external dependencies, directly parsing frontmatter fields like task, status, and agent from manifest files to deliver structured summaries for session recaps.