Axiom SRE Investigator
openclaw/clawhub
Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.
Leverage Slack user profiles, presence, DND status, and workspace context to personalize responses, route escalations, and coordinate team operations.
Install Slack User Context
$ npx skills add automateyournetwork/netclaw --skill slack-user-context -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw slack-user-context --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/slack-user-context .claude/skills/slack-user-context && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "slack-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-user-context into .claude/skills/slack-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-user-context", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-user-contextType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automateyournetwork/netclaw --skill slack-user-context -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw slack-user-context --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/slack-user-context .agents/skills/slack-user-context && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "slack-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-user-context into .agents/skills/slack-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-user-context", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill slack-user-context -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw slack-user-context --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/slack-user-context .cursor/skills/slack-user-context && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "slack-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-user-context into .cursor/skills/slack-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-user-context", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/slack-user-context--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automateyournetwork/netclaw --skill slack-user-context -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw slack-user-context --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/slack-user-context .gemini/skills/slack-user-context && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "slack-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-user-context into .gemini/skills/slack-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-user-context", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automateyournetwork/netclaw slack-user-contextInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automateyournetwork/netclaw --skill slack-user-context -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/slack-user-context .github/skills/slack-user-context && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "slack-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-user-context into .github/skills/slack-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-user-context", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill slack-user-context -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automateyournetwork/netclaw slack-user-context --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/slack-user-context .opencode/skills/slack-user-context && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "slack-user-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/slack-user-context into .opencode/skills/slack-user-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slack-user-context", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
slack-user-context- GitHub stars
- 676
- Token cost
- ~1.5k tokens
- SKILL.md length
- 542 words
- Files
- 1
- Skills in repo
- 120
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Leverage Slack user profiles, presence, DND status, and workspace context to personalize responses, route escalations, and coordinate team operations.
- Works in 4 steps: Escalation Routing → Personalized Response Depth → Timezone-Aware Scheduling → …
- Checking who is on-call
- SKILL.md covers Slack OAuth Scopes Used, User-Aware Behaviors, Team Awareness Features and NetClaw Presence Management, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Slack User Context is an agent skill from automateyournetwork/netclaw. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Incident response. It works with Slack. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.
When your agent uses it
- Checking who is on-call
- Routing an escalation
- Personalizing responses based on user role
- Respecting Do Not Disturb before paging someone
Example prompts
- “/slack-user-context”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 95bb17e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Slack User Context loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 542 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from automateyournetwork/netclaw at commit 95bb17e, republished under its Apache-2.0 licence (© automateyournetwork). 542 words, ~1,497 tokens.
Download SKILL.mdSave it as
.claude/skills/slack-user-context/SKILL.md (or your agent's skills folder).- name
- slack-user-context
- description
- 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.
- license
- Apache-2.0
- user-invocable
- true
Slack User Context
Slack OAuth Scopes Used
| Scope | Purpose |
|---|---|
users:read | View workspace members and their basic info |
users.profile:read | View detailed profiles (title, department, timezone) |
users:write | Set NetClaw's own presence status |
dnd:read | Check Do Not Disturb before escalating |
im:read | View DM channel info |
im:history | Read DM context for personalized responses |
channels:read | Know which channels exist and their purposes |
search:read.public | Search public channels for relevant discussions |
User-Aware Behaviors
1. Escalation Routing
Before escalating an alert to a specific person:
- Check DND status — Is the engineer in Do Not Disturb mode?
- Check presence — Are they active, away, or offline?
- Check timezone — Is it their working hours?
- Check profile title — Are they the right role for this issue?
Escalation Decision Matrix:
| DND | Presence | Severity | Action |
|---|---|---|---|
| Off | Active | Any | Mention directly |
| Off | Away | P1/P2 | Mention (they'll see notification) |
| Off | Away | P3/P4 | Post to channel, don't mention |
| On | Any | P1 | Mention anyway (override DND for P1) |
| On | Any | P2 | Try next person in rotation |
| On | Any | P3/P4 | Post to channel only |
2. Personalized Response Depth
Adjust response complexity based on who's asking:
From user profile title/department:
| Title Contains | Response Style |
|---|---|
| "Network Engineer", "CCIE" | Full technical detail, CLI output, protocol specifics |
| "NOC", "Operations" | Actionable steps, severity, impact summary |
| "Manager", "Director" | Executive summary, business impact, timeline |
| "Security", "InfoSec" | Focus on security implications, CVEs, compliance |
| "Developer", "DevOps" | API perspectives, connectivity impact, service mapping |
| "Help Desk", "Support" | Simple status, ETA, who to contact |
3. Timezone-Aware Scheduling
When scheduling reports or maintenance windows:
- Read the requesting user's timezone from their Slack profile
- Present times in THEIR timezone (not just UTC)
- Warn if proposed maintenance window is outside their business hours
- Suggest alternatives that work across timezones for multi-region teams
4. Context from Previous Conversations
When a user asks a follow-up question:
- Check recent DM and channel history for context
- Reference previous reports or investigations
- Don't re-explain concepts they've already discussed
- Build on previous analysis rather than starting fresh
Team Awareness Features
Show full SKILL.md (218 more words)Show less
On-Call Roster Awareness
When NetClaw needs to escalate:
:telephone_receiver: *Escalation Attempt*
Checking team availability...
• @engineer1 — :green_circle: Active (Network Engineer) — *SELECTED*
• @engineer2 — :red_circle: DND until 08:00 EST (Senior NetEng)
• @engineer3 — :yellow_circle: Away (NOC Analyst) — last active 2h ago
• @manager1 — :green_circle: Active (Net Ops Manager) — CC'd on P1
Escalating to @engineer1...Workload Context
If NetClaw sees a user is already active in multiple incident threads:
:information_source: Note: @engineer1 is currently active in 2 other incident threads.
Consider routing to @engineer3 if this is non-urgent.Handoff Between Shifts
When a shift change is approaching:
:arrows_counterclockwise: *Shift Handoff Summary for @nightshift_engineer*
*Active Items:*
1. :warning: R2 memory trending high (78% → 82% over 8h) — monitoring
2. :wrench: SW1 firmware upgrade scheduled for 02:00 UTC — prep done
3. :white_check_mark: R1 Loopback99 change completed and verified
*Pending:*
4. :hourglass: Waiting on ISP ticket #45678 for R3 circuit
5. :clipboard: Security audit scheduled for SW2 tomorrow
_Full context in #netclaw-reports thread →_NetClaw Presence Management
Set NetClaw's own presence to reflect its status:
| NetClaw Status | Slack Presence | Meaning |
|---|---|---|
| Idle | :green_circle: Active | Ready for requests |
| Running health check | :green_circle: Active | Processing (responsive) |
| Running fleet-wide ops | :yellow_circle: Away | Batch processing (may be slow) |
| Error / unreachable MCP | :red_circle: DND | Degraded — some skills unavailable |
Search for Context
Before answering questions about the network, search public channels for recent discussions:
- Search for device names mentioned in recent messages
- Find previous troubleshooting threads about the same device
- Reference prior decisions about the network architecture
- Link to relevant existing threads instead of duplicating information
Privacy and Boundaries
- Never expose user DND details, exact schedules, or personal info to other users
- Only use profile information to improve routing and response quality
- Don't track user activity patterns beyond immediate operational needs
- Respect when users don't want to be disturbed — follow the escalation matrix
- Be transparent about what context you're using when personalizing responses
Integration with Other Skills
| Skill | User Context Enhancement |
|---|---|
| slack-network-alerts | Route to active, available engineers |
| slack-incident-workflow | IC assignment based on availability |
| slack-report-delivery | Adjust detail level per audience |
| All pyATS skills | Include requestor context in GAIT trail |
© automateyournetwork, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in workspace/skills/slack-user-context of automateyournetwork/netclaw.
Open the folder on GitHubat commit 95bb17e
Compare with similar skills
Slack User Context next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Slack User Context this skillautomateyournetwork/netclaw | 676 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Axiom SRE Investigatoropenclaw/clawhub | 9.5k | — | ~7.1k | Automated safety check: Pass | MIT | |
| Alerting Irmgrafana/skills | 281 | 1 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Doordash Group Ordersdavila7/claude-code-templates | 32k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Oncall Irmgrafana/skills | 281 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Incident Runbookjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Alerting Irm
grafana/skills
Configure Grafana Alerting, Incident Response Management (IRM), and SLOs end-to-end — provisions Grafana-managed and data-source-managed alert rules, contact points (Slack/PagerDuty/email/webhook)…
Doordash Group Orders
davila7/claude-code-templates
Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster.
- Official
Oncall Irm
grafana/skills
Route alerts, run on-call rotations, and drive incidents in Grafana IRM / OnCall — integrations (Alertmanager / Grafana Alerting / generic webhook / PagerDuty), Jinja2 routing + grouping templates…
Vercel Incident Runbook
jeremylongshore/tons-of-skills-marketplace
Vercel incident response procedures with triage, instant rollback, and postmortem.
Sentry Alert Tuner
LeoYeAI/openclaw-master-skills
Reduce Sentry alert fatigue by surgically tuning issue grouping, fingerprint rules, severity mapping, sample rates, before-send filters, sourcemap pipelines, and release-health gates.
More from automateyournetwork/netclaw
All 120 skills in this repoEVE-NG Lab Topology Design
automateyournetwork/netclaw
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
ACI Policy Change Deployment
automateyournetwork/netclaw
Deploys Cisco ACI policy changes only behind an approved ServiceNow Change Request, capturing pre and post-change fault baselines and rolling back automatically on a fault delta.
Cisco ACI Fabric Health Audit
automateyournetwork/netclaw
Runs a phased health audit of a Cisco ACI fabric through MCP tools: node status, links, tenant and policy review, faults and endpoint learning.
Anta Validation
automateyournetwork/netclaw
Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.
Arista Cvp
automateyournetwork/netclaw
Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).
AWS Cloud Monitoring
automateyournetwork/netclaw
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
Related
Works with
Categories
Questions about Slack User Context
What does Slack User Context do?
Leverage Slack user profiles, presence, DND status, and workspace context to personalize responses, route escalations, and coordinate team operations. Slack User Context is an agent skill from automateyournetwork/netclaw. Leverage Slack user profiles, presence, DND status, and workspace context to personalize responses, route escalations, and coordinate team operations.
When should I use Slack User Context?
Slack User Context fits situations like: checking who is on-call; routing an escalation; personalizing responses based on user role; respecting Do Not Disturb before paging someone.
How do I install Slack User Context in Claude Code?
Run `npx skills add automateyournetwork/netclaw --skill slack-user-context -a claude-code`. Or copy the skill folder (workspace/skills/slack-user-context in automateyournetwork/netclaw) into .claude/skills/slack-user-context in your project. Claude Code loads it when a task matches its description.
How do I install Slack User Context in Codex?
Run `npx skills add automateyournetwork/netclaw --skill slack-user-context -a codex`. Or copy the skill folder (workspace/skills/slack-user-context in automateyournetwork/netclaw) into .agents/skills/slack-user-context in your project. Codex loads it when a task matches its description.
Can I use Slack User Context in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill slack-user-context -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slack-user-context, .gemini/skills/slack-user-context, .github/skills/slack-user-context and .opencode/skills/slack-user-context in your project.
What does Slack User Context need to run?
SKILL.md names no scripts, command-line tools or credentials: Slack User Context is instructions for the agent only.
Does Slack User Context access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Slack User Context safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Slack User Context use?
Slack User Context is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Slack User Context use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Slack User Context?
Skills that share tags, products or a category with Slack User Context: Axiom SRE Investigator (openclaw/clawhub, 9.5k stars), Alerting Irm (grafana/skills, 281 stars), Doordash Group Orders (davila7/claude-code-templates, 32k stars) and Oncall Irm (grafana/skills, 281 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Slack User Context?
automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 676 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 5, 2026.
Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.