Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    slack incident sentinel

    1

    Redact sensitive PII/tokens from incident logs and generate Slack Block Kit previews with SLA impact telemetry.

    Free

    Security scanned
    slack incident sentinel

    slack incident sentinel

    Example session with this skill installed

    Sanitize these logs and calculate SLA impact for a 120-minute outage on a $50,000 contract with 99.9% uptime target. Logs: 'Database connection failed for postgres://admin:password123@db.internal'

    • Read your context and instructions
    • Compiled the slack incident sentinel

    Processed the incident diagnostics and calculated SLA telemetry. The database URI has been masked, and the Slack Block Kit preview is ready.

    Incident Sentinel Report

    MetricValue
    Redaction Audit1 match (database-uri)
    Total Cycle Minutes43,200
    Allowable Downtime43.20 minutes
    Error Budget Burn277.78%
    Estimated Penalty$277.78 USD
    Dispatch StatusNOT_SENT
    {
      "blocks": [
        {
          "type": "header",
          "text": { "type": "plain_text", "text": "🚨 Incident Severity: High" }
        },
        {
          "type": "section",
          "text": {
            "type": "mrkdwn",
            "text": "*Sanitized Diagnostics:* Database connection failed for postgres://[REDACTED]"
          }
        },
        {
          "type": "section",
          "fields": [
            { "type": "mrkdwn", "text": "*Burn:* 277.78%" },
            { "type": "mrkdwn", "text": "*Est. Penalty:* $277.78" }
          ]
        },
        {
          "type": "actions",
          "elements": [
            { "type": "button", "text": { "type": "plain_text", "text": "Acknowledge" }, "style": "primary" },
            { "type": "button", "text": { "type": "plain_text", "text": "Join War Room" } }
          ]
        }
      ]
    }
    

    Next steps

    1. Copy the Block Kit JSON into the Slack Block Kit Builder to verify the visual layout.
    2. Manually post the sanitized payload to the designated incident channel.
    3. Update the penalty_multiplier if the specific customer contract exceeds the default 2x rate.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Incident response often leaks sensitive credentials into Slack channels, and calculating the financial impact of downtime during a crisis is prone to manual error. This skill sanitizes raw diagnostic data and generates financial SLA impact reports to prepare for incident communication.

    What it does

    • Sensitive data redaction identifies and masks AWS keys, JWTs, database URIs, PII, and payment cards using pattern matching.
    • SLA telemetry calculation estimates error budget burn and financial penalties based on outage duration and contract value.
    • Block Kit generation builds a structured JSON preview for Slack messages including metadata, diagnostics, and action buttons.
    • Redaction auditing provides a summary of detected categories and the count of matches found in the payload.

    How it works

    1. Supply the raw incident diagnostics, responder details, and outage duration to the slack_incident_sentinel tool.
    2. Provide contract parameters like monthly value and uptime targets for the telemetry engine.
    3. Review the redaction_audit to verify which categories of sensitive data were identified and masked.
    4. Use the generated Block Kit JSON to preview the incident notification before manual dispatch.

    Frameworks & tools

    This skill uses the Model Context Protocol (MCP) to interface with developer environments. It generates Slack Block Kit JSON structures and performs pattern-based redaction for AWS, GitHub, Stripe, and standard PII formats.

    Why this beats prompting it yourself

    Manual prompts often miss specific credential patterns like database URIs or Luhn-valid card numbers during high-pressure incidents. This skill provides a standardized math engine for SLA penalties, ensuring financial impact estimates are calculated consistently across different responders.

    Use cases

    • Sanitizing server logs containing bearer tokens before sharing them in a public Slack channel.
    • Estimating the financial penalty of a 45-minute outage on a $100k/month enterprise contract.
    • Generating standardized Slack "War Room" invitation blocks with pre-filled severity and commander data.
    • Auditing raw incident reports for PII exposure before they are archived.

    Known limitations

    Does not call Slack APIs or send messages. Redaction is pattern-based and not a guarantee of 100% PII removal. Does not verify workspace access or channel existence.

    Does not send Slack messages. Redaction is pattern-based and cannot guarantee complete removal. Caller must provide all contract values; no external contract verification is performed.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Read Files
    Network Access
    Listed4 days ago

    What's inside

    Frequently Asked Questions

    This skill acts as a security and reporting middleware. It prevents accidental data leaks by masking credentials like AWS keys and JWTs in logs, while simultaneously calculating the financial impact of downtime based on your specific SLA contracts.

    The skill identifies and redacts AWS keys, GitHub tokens, Stripe keys, database URIs, JWTs, and PII using pattern matching. It also provides a redaction audit so you can see exactly which categories were detected and masked.

    No, this skill focuses on data preparation. It generates the Slack Block Kit JSON and telemetry reports, which your agent then uses to send messages via your own Slack integration or API setup.

    This skill uses the Model Context Protocol (MCP), making it compatible with any AI agent or IDE (like Claude Desktop) that supports the MCP standard for interfacing with developer tools.

    The telemetry engine uses the outage duration, monthly contract value, and uptime targets you provide to calculate error budget burn and estimated financial penalties for consistent reporting.

    Redaction is based on robust pattern matching rather than heuristic guessing, but it is not a 100% guarantee of PII removal; users should always review the redaction audit before final dispatch.

    New in LLM Ops