Skip to content
Skills Library
DevOps & cloud · Analysis

status-request

/status-request

Handle the human's mid-incident request for status. Use when a stakeholder asks for impact/status during an incident, AND before finishing any incident where a human was said to request status, to confirm the request has not arrived unanswered.

Licence
Apache-2.0
Last repository change
02.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Handle the human's mid-incident request for status. Use when a stakeholder asks for impact/status during an incident, AND before finishing any incident where a human was said to request status, to confirm the request has not arrived unanswered.

Original author description

Handle the human's mid-incident request for status. Use when a stakeholder asks for impact/status during an incident, AND before finishing any incident where a human was said to request status, to confirm the request has not arrived unanswered.

How it works

  1. Poll for the request
  2. Reply IN THE THREAD, not the channel
  3. What the reply must contain
  4. Before finishing
Original SKILL.md headings · 37 lines, 333 words
SKILL.md preview
---
name: status-request
description: Handle the human's mid-incident request for status. Use when a stakeholder asks for impact/status during an incident, AND before finishing any incident where a human was said to request status, to confirm the request has not arrived unanswered.
---

# Answering a mid-incident status request

A human stakeholder requests status DURING the incident, as a new message in the
incident channel. That message does not exist at the start; it appears while you
are investigating or waiting for recovery. You will not see it unless you re-read
the channel after your first read.

## Poll for the request
The request arrives as a NEW message posted after your first `world_slack_read_channel`.
Re-read the incident channel at each natural checkpoint (after each `world_wait`,
after a deploy, before you consider finishing) and look for a message from a human
user asking for status. The automated PagerDuty/bot messages are not it; the
request is prose from a person asking how things stand.

## Reply IN THE THREAD, not the channel
Reply to the human on THEIR message, not as a new top-level channel post. In this
workspace the thread anchor is the `ts` field of the human's message: pass it as the
reply's `thread_ts` (alongside `channel`) when you post. A bare channel post with no
`thread_ts` is NOT a reply in the request thread and does not satisfy the task.

## What the reply must contain
Three things, and only current fact:
- current IMPACT (what is broken / what has recovered, as observed right now),
- the ACTION in progress or just taken,
- the NEXT UPDATE (when you will report again, or what signal you are waiting on).

Preserve uncertainty: until recovery is OBSERVED (monitor back to OK and error logs
stopped), do not report recovery as done. If asked before recovery, say what you are
still waiting on. Answer with what is true at the moment you reply — do not wait for
resolution before replying.

## Before finishing
Do not call `world_finish` for an incident where a human was said to request status
until you have re-read the channel one last time and either replied in the request
thread or confirmed, from a current read, that no such request was ever posted.

Versions

The database has no other skills named status-request.

Database snapshot: 13.11.2026 · package version d774fffdb3eb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100slack-incident-workflow
    Manage network incident response workflows in Slack - incident channels, status updates, escalation, resolution tracking, and post-incident review coordination. Use when declaring a network incident, coordinating outage response in Slack, tracking incident status, or running a post-incident review.
  • 100postmortem
    Use only when the user explicitly asks for a postmortem, RCA, or incident review after an incident is resolved.
  • 85status-page-generator
    When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
  • 100incident-triage
    First-pass triage of a possible production incident for Paradev's hosted services. Gathers signals (recent deploys, Sentry spikes, health checks), proposes a severity and a status.superset.sh message, then stops for human approval. Use when someone reports an outage, errors…
  • 100incident-postmortem-template
    Manage incident postmortem template operations. Auto-activating skill for Technical Documentation. Triggers on: incident postmortem template, incident postmortem template Part of the Technical Documentation skill category. Use when working with incident postmortem template…
  • 100incident-writer
    Creates and manages incident reports for jiun.dev/status with consistent formatting. Generates frontmatter, timeline, and body sections based on severity. Use for "인시던트 작성", "장애 보고서", "incident report", "status 작성", "장애 기록" requests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.