cascade-summarize-document-content

Summarize Jira, Confluence, and Google Docs content into structured -summary.md files.

24|3|Updated Jul 17, 2025
One-click install
npx skills add https://github.com/bitovi/cascade-mcp --skill cascade-summarize-document-content
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cascade-summarize-document-content
Source: https://github.com/bitovi/cascade-mcp/tree/main/plugins/cascade-mcp/skills/cascade-summarize-document-content
Command: npx skills add https://github.com/bitovi/cascade-mcp --skill cascade-summarize-document-content

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Summarize and categorize raw content fetched by load-linked-resource-content, producing structured summaries and surfacing newly discovered links to feed downstream skills.

Core Features & Use Cases

  • Analyzes raw content in .temp/cascade/context/ to extract key information from Jira, Confluence, and Google Docs sources
  • Generates -summary.md files alongside each source to enable iterative analysis and reuse
  • Discovers and records new links for subsequent loading and processing

Quick Start

Run the cascade-summarize-document-content skill after load-linked-resource-content to produce -summary.md files for each .md in .temp/cascade/context.

Frequently Asked Questions about cascade-summarize-document-content

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

FAQPage Schema
How do I summarize Jira issues and Confluence pages stored as markdown?

Run the cascade-summarize-document-content skill after fetching content with load-linked-resource-content. It analyzes each .md file in .temp/cascade/context/ and generates structured -summary.md files alongside each source for iterative analysis.

How does link discovery work when processing Confluence and Jira content?

Yes, the skill formats summaries according to a prescribed schema while preserving scope markers from the original markdown content. This ensures structured, consistent output for downstream skills to consume.

Do I need a specific tool to fetch content before summarizing markdown files?

The skill generates -summary.md files alongside each source markdown file. These structured summaries contain extracted key information, newly discovered links, and formatted content that enables iterative analysis and reuse by downstream skills.

What is the best way to extract key information from Google Docs content for downstream processing?

The best way to extract key information from Google Docs content is using this skill to generate structured markdown summaries. It categorizes the raw content and formats it according to a prescribed schema, preserving scope markers for downstream consumption.