reporting-situation

Aggregate and summarize data from Google Workspace, Notion, and Jira into situation reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aufrank/agent-skills --skill reporting-situation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reporting-situation
Source: https://github.com/aufrank/agent-skills/tree/main/skills/reporting-situation
Command: npx skills add https://github.com/aufrank/agent-skills --skill reporting-situation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill provides a persistent, evolving view of your work environment by tracking collaborators, topics, and teams across multiple platforms, reducing redundant API calls and providing historical context.

Core Features & Use Cases

  • Entity-Based Tracking: Monitors activity for specific collaborators, topics, and teams.
  • Persistent Cache: Remembers mappings and previously seen items for efficiency.
  • Smart Summarization: Fetches and summarizes new items and discussions automatically.
  • Deduplication: Merges signals from multiple sources into unique work items.
  • Use Case: Get a daily digest of all relevant activity related to the "ML Platform" topic across Google Workspace, Notion, and Jira, with summaries of new documents and discussions.

Quick Start

Run the situation report orchestrator to gather and update data.

Frequently Asked Questions about reporting-situation

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

FAQPage Schema
How do I generate a situation report across Google Workspace, Notion, and Jira?

A situation report aggregates and summarizes activity from Google Workspace, Notion, and Jira into a comprehensive view. The skill fetches new items, deduplicates signals from multiple sources, and merges them into unique work items for deep situation awareness.

How does situation tracking maintain historical context without redundant API calls?

Situation tracking maintains historical context and avoids redundant API calls by using a persistent cache. This cache remembers previously seen items and entity mappings for collaborators, topics, and teams, enabling efficient data retrieval and an evolving view of your work environment.

Can I track specific collaborators and topics across multiple platforms like Notion and Jira?

Yes, you can track specific collaborators, topics, and teams across multiple platforms. The skill uses entity-based tracking to monitor activity for these specific elements, automatically fetching and summarizing new discussions and documents related to them.

What is the best way to get a daily digest of activity for a specific topic across my work environment?

The best way to get a daily digest is to use the situation report orchestrator. It aggregates relevant activity for a specific topic across Google Workspace, Notion, and Jira, providing smart summaries of new documents and discussions while maintaining a persistent knowledge graph.

Does situation reporting deduplicate work items when signals come from different sources?

Yes, situation reporting deduplicates work items by merging signals from multiple sources into unique work items. This ensures that activity tracked across Google Workspace, Notion, and Jira is consolidated, preventing redundant entries in your comprehensive situation report.