pulse

Aggregate Jira and Slack activity into a ranked priority triage output.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/cosmicdreams/claude-plugins --skill pulse-cosmicdreams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pulse
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/workflow/skills/pulse
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill pulse-cosmicdreams

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

pulse removes the friction of checking multiple tools by producing a single ranked view of what you should respond to right now across Jira and Slack.

Core Features & Use Cases

  • Cross-source priority triage: Aggregates Jira and Slack signals into one TOP PRIORITY item with a clear reason.
  • Delta since last broadcast: Produces a grouped SINCE LAST BROADCAST view showing what changed across runs.
  • Hourly/loop-ready operations: Designed to run on a schedule (for example via /loop) using workflow.json configuration and cached state.

Example use case: You’re managing a busy sprint and need to know immediately whether a blocked Jira issue needs your attention or whether you received a DM/mention in Slack—pulse surfaces the highest-priority action first and lists everything new since the last run.

Quick Start

Run workflow:pulse to generate a unified ranked snapshot of your Jira updates and Slack activity since your last broadcast.

Frequently Asked Questions about pulse

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

FAQPage Schema
How do I unify Jira and Slack activity into a single priority feed for sprint triage?

Priority triage across Jira and Slack works by spawning per-integration subagents that compute deltas since the last recorded timestamp, maintaining state to group items into a single ranked view of what changed since your last broadcast.

Can I monitor multiple Jira servers and Slack workspaces simultaneously?

Yes, you can monitor multi-server Jira environments and multi-workspace Slack channels simultaneously, as the aggregation process spawns dedicated subagents for each integration to collect and rank activity across all configured sources.

How do I automate sprint ops monitoring to run on a schedule?

You automate sprint ops monitoring by configuring workflow.json and executing the process on a schedule via a loop command, which computes deltas since the last run and writes cached state for subsequent executions.

What is stateful monitoring and how does it track changes since the last broadcast?

Stateful monitoring tracks changes by computing deltas since the last recorded timestamp, maintaining a cached state file across runs to produce a grouped SINCE LAST BROADCAST view showing exactly what is new across your Jira and Slack environments.

Does priority triage require any specific configuration before monitoring Jira and Slack?

Priority triage requires a workflow.json configuration file to define your integrations and environment parameters, ensuring the subagents can accurately connect to your multi-server Jira and multi-workspace Slack instances for stateful monitoring.

What's the best way to surface blocked Jira issues and Slack mentions during a sprint?

The best way to surface blocked Jira issues and Slack mentions is cross-source priority triage, which aggregates signals from both platforms into one TOP PRIORITY item with a clear reason and lists everything new since the last run.