slack-user-context

Route Slack escalations using user presence, DND status, and timezone.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/dgethings/netclaw --skill slack-user-context-dgethings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack-user-context
Source: https://github.com/dgethings/netclaw/tree/main/workspace/skills/slack-user-context
Command: npx skills add https://github.com/dgethings/netclaw --skill slack-user-context-dgethings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Leverage Slack user profiles, presence, DND status, and workspace context to personalize responses, route escalations, and coordinate team operations. Use when checking who is on-call, routing an escalation, personalizing responses based on user role, or respecting Do Not Disturb before paging someone.

Core Features & Use Cases

  • Escalation Routing: Before escalating an alert, check DND status, presence, timezone, and profile title to determine the appropriate recipient or channel disclosure.
  • Personalized Response Depth: Adjust response detail based on the requestor's role and context to provide actionable insights for engineers, managers, or operators.
  • Timezone-Aware Scheduling: Present schedules and timelines in the requestor's timezone to improve response timeliness and avoid off-hours paging.
  • Context from Previous Conversations: Leverage recent DM/channel history to tailor follow-up analyses and avoid redundant explanations.

Quick Start

Initiate an escalation by checking the on-call engineer's Slack profile data and routing the incident with Do Not Disturb awareness.

Frequently Asked Questions about slack-user-context

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

FAQPage Schema
How do I route Slack escalations while respecting Do Not Disturb status?

Slack escalation routing checks Do Not Disturb status, presence, and timezone to determine the appropriate recipient or channel disclosure. It personalizes responses based on user role to ensure safe escalation decisions.

How does Slack user context personalize responses for on-call engineers?

Slack user context personalizes responses by checking profile data, presence, and role to adjust response detail. It provides actionable insights tailored for engineers, managers, or operators during team conversations.

Can I use Slack user profiles to schedule alerts in the requestor's timezone?

Slack user profiles support timezone-aware scheduling to present schedules and timelines in the requestor's timezone. This improves response timeliness and avoids off-hours paging during escalations.

What is the best way to check on-call presence before paging someone in Slack?

Checking on-call presence involves verifying Slack user profile data, Do Not Disturb status, and timezone before routing an incident. This ensures safe escalation decisions and avoids unnecessary disruptions.

Does Slack user context work with previous DM history for follow-up analyses?

Slack user context leverages recent DM and channel history to tailor follow-up analyses. This avoids redundant explanations and coordinates team operations across ongoing conversations.

When should I not use DND awareness for escalation routing in Slack?

DND awareness for escalation routing should be bypassed during critical incidents where immediate paging is required. Use profile title and presence checks to determine appropriate channel disclosure instead.