summarize-status

Generate human-readable Markdown status summaries for Paperclip project scopes and execution workspaces.

79.8k|14.6k|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/paperclipai/paperclip --skill summarize-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summarize-status
Source: https://github.com/paperclipai/paperclip/tree/main/packages/skills-catalog/catalog/bundled/paperclip-operations/summarize-status
Command: npx skills add https://github.com/paperclipai/paperclip --skill summarize-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve?

This Skill solves the problem of information overload in complex AI agent workflows by distilling scattered issue data, blocker chains, and project updates into a single, actionable summary.

Core Features & Use Cases

  • Action-Oriented Reporting: Automatically identifies 1–3 critical tasks required to unblock work, ensuring stakeholders know exactly what to do next.
  • Contextual Summarization: Synthesizes project, workspace, and execution data into a conversational, human-readable format without jargon.
  • Use Case: A project manager needs to quickly understand the status of a multi-agent development project; this Skill reads the current issue state and writes a concise summary to the project's header slot.

Quick Start

Use the summarize-status skill to generate a header summary for the current project workspace.

Frequently Asked Questions about summarize-status

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

FAQPage Schema
How do I generate a status summary for a project?

Trigger the summarize-status skill by assigning a generation issue to the agent with the target scopeKind and scopeId. The agent will read the current issues and write a formatted Markdown summary to the header slot.

What information does the summary include?

The summary includes 1–3 concrete, actionable items to unblock work, followed by a brief, plain-language status update. It focuses on what is currently moving and what requires human intervention.

Can I use this skill to change issue states?

No, this skill is strictly for read-and-report operations. It is explicitly designed to summarize status and write revisions to slots, not to modify issue states, reassign work, or edit code.

How does the skill handle sensitive information?

The skill is instructed to never surface secrets such as API keys, tokens, or credentials that may appear in issue bodies or configurations, ensuring that summaries remain safe for general viewing.

What happens if there is no status to report?

The skill is designed to be honest and will report that nothing needs the reader's attention if the scope is quiet. It will never fabricate status or pad the report with filler actions.