Token导航 LogoToken导航TokenDH.com
开发只读github未标认证来源可访问许可证需确认审计提醒

slack-workflowsSlack workflows 开发

Agent Skill

用于处理 Slack 工作区里的频道、消息、线程、用户和通知信息。它适合让 Agent 查询团队沟通记录、整理上下文、回复线程或辅助协作提醒。使用时需要确认机器人或用户 token 是否具备目标频道访问权,私有频道和历史消息通常有额外权限限制;发送消息、@成员或批量读取对话时,应避免泄露内部讨论和敏感工作信息。

总安装

16,475

周安装

673

GitHub Stars

89

下载量

5,330
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:slack-workflows(Slack workflows 开发)
来源仓库:https://github.com/claude-office-skills/skills
仓库路径:skills/slack-workflows
安装命令:
npx skills add https://github.com/claude-office-skills/skills --skill slack-workflows
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/claude-office-skills/skills --skill slack-workflows

简介

用于处理 Slack 工作区里的频道、消息、线程、用户和通知信息。

  • 适合让 Agent 查询团队沟通记录、整理上下文、回复线程或辅助协作提醒。
  • 使用时需要确认机器人或用户 token 是否具备目标频道访问权,私有频道和历史消息通常有额外权限限制。
  • 发送消息、@成员或批量读取对话时,应避免泄露内部讨论和敏感工作信息。
  • 安装前建议确认权限范围和维护状态,以及是否会触发联网或文件读写操作。

SKILL.md

Slack Workflows

Automate Slack with intelligent workflows for notifications, standup collection, approval processes, and cross-platform integrations. Based on n8n automation patterns.

Overview

This skill covers:

  • Automated notifications and alerts
  • Daily standup collection
  • Approval workflows
  • Cross-platform integrations
  • Channel management automation

Core Workflows

1. Daily Standup Bot

workflow: "Async Standup"
schedule: "9:00 AM weekdays"

steps:
  1. send_prompt:
      channel: each team member (DM)
      message: |
        👋 Good morning! Time for standup.

        Please share:
        1️⃣ What did you complete yesterday?
        2️⃣ What are you working on today?
        3️⃣ Any blockers?

        Reply in this thread 👇

  2. collect_responses:
      timeout: 2_hours
      reminder: at_1_hour

  3. compile_summary:
      time: "11:00 AM"
      channel: "#team-standup"
      format: |
        📋 *Daily Standup - {date}*

        {for_each_member}
        *{name}*
        ✅ Yesterday: {yesterday}
        📌 Today: {today}
        🚧 Blockers: {blockers}

        ---
        {end_for}

        *Summary:*
        • {total} team members responded
        • {blockers_count} blockers flagged

  4. flag_blockers:
      if: blockers_count > 0
      notify: manager
      action: create_thread_for_discussion

2. Approval Workflow

workflow: "Expense Approval"
trigger: form_submission OR slash_command

steps:
  1. receive_request:
      data:
        - requester
        - amount
        - category
        - description
        - receipt_url

  2. route_approval:
      rules:
        - if: amount < 100
          approver: direct_manager

        - if: amount >= 100 AND amount < 1000
          approver: department_head

        - if: amount >= 1000
          approver: [department_head, finance]
          type: sequential

  3. send_approval_request:
      channel: DM to approver
      message: |
        📝 *Expense Approval Request*

        *From:* {requester}
        *Amount:* ${amount}
        *Category:* {category}
        *Description:* {description}

        [View Receipt]({receipt_url})

      actions:
        - button: "✅ Approve"
          action: approve
        - button: "❌ Reject"
          action: reject
        - button: "💬 Ask Question"
          action: request_info

  4. handle_response:
      approved:
        - notify_requester: "Your expense was approved! 🎉"
        - create_task: in_accounting_system
        - log: in_expense_tracker

      rejected:
        - notify_requester: "Expense not approved. Reason: {reason}"
        - log: with_rejection_reason

  5. escalate_if_no_response:
      timeout: 24_hours
      action: remind_approver
      final_escalation: 48_hours

3. New Hire Onboarding

workflow: "Employee Onboarding"
trigger: new_employee_added_to_HRIS

timeline:
  day_minus_7:
    - create_channels:
        - "#welcome-{name}"
        - add_to: ["#general", "#team-{department}"]
    - notify_it: "Set up laptop for {name}"
    - notify_manager: "Onboarding starts in 7 days"

  day_1:
    - morning:
        - post_welcome: "#general"
          message: |
            🎉 Please welcome *{name}* to the team!

            Role: {title}
            Team: {department}
            Location: {office}

            Fun fact: {fun_fact}

            Say hi and make them feel welcome! 👋

        - dm_new_hire:
            message: |
              Welcome to {Company}! 🚀

              Here are your first steps:
              1. [Complete HR paperwork]({hr_link})
              2. [Set up your accounts]({it_link})
              3. [Meet the team]({org_chart})

              Your buddy is @{buddy_name} - reach out anytime!

    - afternoon:
        - schedule_intros: with_key_stakeholders

  day_3:
    - check_in:
        dm: "How's your first week going? Any questions?"

  day_7:
    - survey:
        question: "How was your onboarding experience?"
        scale: 1-5

  day_30:
    - feedback_request:
        dm: "You've been here a month! What could we improve?"

4. Incident Response

workflow: "Incident Alert"
trigger: monitoring_alert OR manual

severity_levels:
  critical:
    - create_channel: "#incident-{timestamp}"
    - notify: "@channel in #engineering"
    - page: on_call_engineer
    - create_war_room: video_link
    - start_timer: for_resolution_tracking

  high:
    - notify: "#engineering-alerts"
    - assign: on_call_engineer
    - create_ticket: in_jira

  medium:
    - notify: "#engineering-alerts"
    - create_ticket: in_jira

  low:
    - create_ticket: in_jira
    - notify: next_business_day

incident_channel_template: |
  🚨 *INCIDENT: {title}*

  *Severity:* {severity}
  *Status:* Investigating
  *Started:* {timestamp}
  *Commander:* @{commander}

  ---

  *Affected Systems:*
  {systems}

  *Customer Impact:*
  {impact}

  ---

  📋 *Actions:*
  • [ ] Identify root cause
  • [ ] Implement fix
  • [ ] Verify resolution
  • [ ] Communicate to stakeholders

  🔗 *Links:*
  • [Runbook]({runbook_url})
  • [Dashboard]({dashboard_url})
  • [Video Room]({video_url})

resolution_flow:
  1. commander_declares: "resolved"
  2. notify_stakeholders: resolution_message
  3. archive_channel: after_24_hours
  4. create_postmortem: in_notion
  5. schedule_review: in_calendar

5. Cross-Platform Sync

workflow: "CRM to Slack Notifications"

triggers:
  hubspot_deal_won:
    channel: "#wins"
    message: |
      🎉 *Deal Closed!*

      *Company:* {company}
      *Value:* ${amount}
      *Rep:* @{sales_rep}
      *Product:* {product}

      Congrats! 🚀

  hubspot_deal_lost:
    channel: "#sales-team"
    message: |
      📊 *Deal Lost*

      *Company:* {company}
      *Value:* ${amount}
      *Reason:* {loss_reason}
      *Competitor:* {competitor}

      Thread for learnings 👇

  github_pr_merged:
    channel: "#engineering"
    message: |
      ✅ PR merged: *{pr_title}*
      by @{author}

      {pr_description_summary}

  stripe_payment_failed:
    channel: "#revenue-alerts"
    message: |
      ⚠️ *Payment Failed*

      *Customer:* {customer_email}
      *Amount:* ${amount}
      *Reason:* {failure_reason}

      [View in Stripe]({stripe_link})

Slash Commands

Custom Commands

slash_commands:
  /kudos:
    description: "Give recognition to a teammate"
    usage: "/kudos @person for [reason]"
    action:
      - post_to: "#kudos"
      - format: |
          🌟 *Kudos!*

          @{sender} gave kudos to @{recipient}

          > {reason}

      - track: in_recognition_spreadsheet

  /pto:
    description: "Request time off"
    usage: "/pto [start_date] to [end_date] for [reason]"
    action:
      - create_approval: pto_approval_flow
      - update_calendar: block_dates
      - notify_team: if_approved

  /standup:
    description: "Submit async standup"
    usage: "/standup"
    action:
      - open_modal: standup_form
      - collect_responses: yesterday, today, blockers
      - post_to: "#team-standup"

  /poll:
    description: "Create a quick poll"
    usage: "/poll 'Question' 'Option 1' 'Option 2' ..."
    action:
      - create_message: with_reactions
      - track_votes: by_reaction_count
      - close_poll: after_24h_or_manual

Channel Management

channel_automation:
  project_channels:
    trigger: jira_project_created
    action:
      - create_channel: "#proj-{project_key}"
      - add_members: project_team
      - set_topic: "{project_name} - {project_description}"
      - pin_message: project_resources
      - archive: when_project_completed

  customer_channels:
    trigger: deal_closed_won
    action:
      - create_channel: "#customer-{company}"
      - add_members: [csm, sales_rep, support]
      - set_purpose: "Support channel for {company}"
      - integrate: zendesk_alerts

  cleanup:
    schedule: monthly
    rules:
      - archive_if:
          no_messages: 90_days
          AND:
            not_pinned: true
            not_customer_channel: true
      - notify_before_archive: 7_days

Output Example

Request: "Set up a deal win notification in Slack"

Output:

# Deal Win Notification Setup

## Workflow Configuration

trigger: hubspot_deal_stage_changed condition: new_stage == "Closed Won"

action: channel: "#wins" message: see_below


## Message Template

🎉 *DEAL CLOSED!*

━━━━━━━━━━━━━━━━━━━━━━

🏢 *Company:* {company_name} 💰 *Value:* ${deal_amount} 👤 *Sales Rep:* @{owner_slack_id} 📦 *Product:* {product_line}

━━━━━━━━━━━━━━━━━━━━━━

*Deal Summary:* • Sales cycle: {days_in_pipeline} days • Lead source: {lead_source} • Industry: {industry}

🎊 Congrats to the team!


## n8n Implementation

// HubSpot Trigger → Slack Node { "nodes": [ { "name": "HubSpot Trigger", "type": "n8n-nodes-base.hubspotTrigger", "parameters": { "eventsUi": { "eventValues": ["deal.propertyChange"] }, "property": "dealstage", "value": "closedwon" } }, { "name": "Format Message", "type": "n8n-nodes-base.set", "parameters": { "values": { "message": "🎉 *DEAL CLOSED!*\n\n🏢 {{$json.company}}\n💰 ${{$json.amount}}" } } }, { "name": "Slack", "type": "n8n-nodes-base.slack", "parameters": { "channel": "#wins", "text": "={{$json.message}}" } } ] }


## Sample Output

🎉 *DEAL CLOSED!*

━━━━━━━━━━━━━━━━━━━━━━

🏢 *Company:* Acme Corporation 💰 *Value:* $45,000 👤 *Sales Rep:* @alice.chen 📦 *Product:* Enterprise Plan

━━━━━━━━━━━━━━━━━━━━━━

*Deal Summary:* • Sales cycle: 45 days • Lead source: Inbound - Website • Industry: Technology

🎊 Congrats to the team!


*Slack Workflows Skill - Part of Claude Office Skills*

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.63%
按下载量换算2,006

Claude

29.05%
按下载量换算1,548

Cursor

19.44%
按下载量换算1,036

Gemini CLI

10.28%
按下载量换算548

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills