Token导航 LogoToken导航

Agent Skill · 开发

slack-workflows(Slack workflows 开发)

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

slack-workflows 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 2,532。

总安装 16,475周安装 673GitHub Stars 89下载 5,330核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

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

安装前建议确认权限范围和维护状态,以及是否会触发联网或文件读写操作。

来源仓库内路径:skills/slack-workflows

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/claude-office-skills/skills --skill slack-work…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

slack-workflows 怎么安装?

在终端执行 npx skills add https://github.com/claude-office-skills/skills --skill slack-workflows。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

slack-workflows 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

slack-workflows 需要什么权限?

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

slack-workflows 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

slack-workflows 用的人多吗?

公开数据是累计安装 16,475 次,近一周安装 673 次,下载 5,330 次,GitHub 89 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

slack-workflows 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
slack-workflows

Slack workflows 开发 · 本页

16,47589只读未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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*

平台分布

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 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills