work-fire-watch

Routes items from the daily-fire-watch Slack report to the current repo for dispatch.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill work-fire-watch-sassy-dog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-fire-watch
Source: https://github.com/Sassy-Dog/sassydog-skills/tree/main/skills/work-fire-watch
Command: npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill work-fire-watch-sassy-dog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After the org-wide daily-fire-watch routine posts its morning report to Slack, each repo still needs its share of the findings turned into actionable work. Re-running a full survey in every repo to rediscover the same items wastes tokens and time. This Skill reads the already-published report, extracts only the items routed to the repo you are in, and hands them to the work-recommendations delegate in the report's own priority order. ## Core Features & Use Cases - Report consumption: Fetches the newest Daily Fire Watch post from the pinned routine poster in Slack #daily-fire-watch and parses only its fenced fire-watch-v1 machine block, never the prose. - Exact repo filtering: Matches item lines to the current repo by bare name equality, preserving the report's Top-5 ranking and tier ordering (P0 through unranked). - Safe delegation: Normalizes items into handles (issue, PR, Sentry, cron, ci-red) and delegates all filing and dispatch to work-recommendations behind its preview and approval gates. - Use Case: You open your repo Monday morning and say "work the fire watch" — the Skill pulls today's report, finds the three items routed to your repo, and ships them through the standard dispatch flow without re-surveying anything. ## Quick Start Work the fire watch for this repo using today's daily-fire-watch Slack report.

Frequently Asked Questions about work-fire-watch

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

FAQPage Schema
How do I work items from the daily fire watch report?

Say "work the fire watch" in the target repo. The Skill reads the newest Daily Fire Watch post in Slack #daily-fire-watch, filters its machine block to items routed to your repo, and delegates them to work-recommendations in the report's priority order.

What is the fire-watch-v1 machine block in Slack reports?

It is a fenced code block the fire-watch routine appends to its Slack post, containing pipe-separated item lines with repo, kind, id, tier, labels, and title fields. It is the only part of the report parsed; the prose is for humans and never interpreted.

Does work-fire-watch post to Slack or re-run the org sweep?

No. It is strictly read-only toward Slack — never posting, reacting, or threading — and it never re-runs the sweep. A missing or unreadable report is a stop condition, not a reason to invoke whats-on-fire locally.

Why does work-fire-watch stop with a NO_CONFIG error?

The Skill requires the repo's .claude/sassy-dog/take-it.md config to exist before reading Slack, since nothing found could be shipped without it. Run sassy-dog:setup-config first to generate the config, then retry.

What happens if the fire watch report is more than a day old?

The Skill states the report's age in one line and asks before continuing, since a stale fire may already be out. It never silently falls back to an older post when today's report is missing or malformed.