[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BXSE8C3FXB4450NW55Z2PZ":3,"skill-same:01M7BXSE8C3FXB4450NW55Z2PZ":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BXSE8C3FXB4450NW55Z2PZ","slack-cli",null,"Use when a developer works with the Slack CLI (slack command) to create, run, or manage a Slack app from the terminal: logging in or authenticating (slack login), adding a team or switching workspaces, running locally (slack run), deploying, editing the app manifest, calling Web API methods (slack api), or searching Slack docs (slack docs search).","CognitionAI\u002Fdevin-marketplace","CognitionAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163493330?v=4","01M7BVSRD98NC4FG8T3EZS6V5M","Cognition","01M7BVSRDX111C2XPWJ0E6MY26",29,"MIT","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fslack-remote\u002Fskills\u002Fslack-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: slack-cli\ndescription: \"Use when a developer works with the Slack CLI (slack command) to create, run, or manage a Slack app from the terminal: logging in or authenticating (slack login), adding a team or switching workspaces, running locally (slack run), deploying, editing the app manifest, calling Web API methods (slack api), or searching Slack docs (slack docs search).\"\n---\n\n# Slack CLI\n\nUse the Slack CLI to create, run, and manage Slack apps — including calling Web API methods directly and searching Slack developer documentation from the terminal.\n\nFor initial setup (sandbox creation, project scaffolding from templates), use the `slack:create-slack-app` skill instead.\n\n---\n\n## Step 1: Detect the Slack CLI\n\nResolve the path to the **public** Slack CLI before running any other command. We refer to the resolved value as `SLACK_CMD` — substitute it everywhere below. **Try 1a → 1b → 1c in order; do not skip ahead.**\n\n### 1a. Standard install path (preferred — no verification needed)\n\nThe official install scripts place the binary at a fixed per-user path. If the file exists, use it directly: only the install script writes to that path.\n\n- macOS \u002F Linux: `~\u002F.slack\u002Fbin\u002Fslack`\n- Windows: `%USERPROFILE%\\AppData\\Local\\slack-cli\\bin\\slack.exe` (or `%USERPROFILE%\\.slack-cli\\bin\\slack.exe` as a fallback)\n\nPOSIX shell:\n\n```bash\n[ -x \"$HOME\u002F.slack\u002Fbin\u002Fslack\" ] && echo \"$HOME\u002F.slack\u002Fbin\u002Fslack\"\n```\n\nPowerShell:\n\n```powershell\n$p = \"$env:USERPROFILE\\AppData\\Local\\slack-cli\\bin\\slack.exe\"\nif (Test-Path $p) { $p } elseif (Test-Path \"$env:USERPROFILE\\.slack-cli\\bin\\slack.exe\") { \"$env:USERPROFILE\\.slack-cli\\bin\\slack.exe\" }\n```\n\nIf a path is returned, set `SLACK_CMD` to that **absolute path** and proceed to Step 2. Do not also run `_fingerprint`.\n\n### 1b. `slack` on PATH (verify with fingerprint)\n\nIf 1a found nothing, try `slack` on PATH:\n\n```bash\nslack _fingerprint 2>\u002Fdev\u002Fnull\n```\n\nIf it outputs `d41d8cd98f00b204e9800998ecf8427e`, set `SLACK_CMD=slack` and proceed.\n\n### 1c. Ask about an alias, or install\n\nIf 1b fails or returns a different value, ask the developer using AskUserQuestion:\n\n- \"The `slack` command on your system doesn't appear to be the public Slack CLI. Do you have it installed under a different name or alias?\"\n- Options: \"Yes, it's aliased as...\" (let them provide the alias), \"No, I need to install it\"\n- If they provide an alias, verify it with `\u003Calias> _fingerprint 2>\u002Fdev\u002Fnull` and set `SLACK_CMD=\u003Calias>`.\n- If they need to install it, run:\n\n  ```text\n  curl -fsSL https:\u002F\u002Fdownloads.slack-edge.com\u002Fslack-cli\u002Finstall.sh | bash\n  ```\n\n  Then re-run **1a** — the install script will have written `~\u002F.slack\u002Fbin\u002Fslack`.\n\n**Common mistakes:** Don't use `which slack` to discover the binary — `which` resolves any shell alias and defeats the point of 1a. In Git Bash on Windows, use the POSIX probe form, not PowerShell.\n\n---\n\n## Step 2: Command Discovery via Help\n\n**Always run `SLACK_CMD \u003Ccommand> --help` before constructing a command you have not used in the current session.** Do not guess at flags — the help output is the source of truth.\n\n- `SLACK_CMD help` — lists all available command groups\n- `SLACK_CMD \u003Ccommand> --help` — shows subcommands, flags, and usage examples\n\n### Resolving `--app` and `--team` values\n\nWhen a command requires `--app` or `--team`:\n\n- **App ID**: Run `SLACK_CMD app list` from the project directory to see installed apps and their IDs.\n- **Team ID**: Run `SLACK_CMD auth list` to see authenticated workspaces and their team IDs.\n\n---\n\n## Step 3: Searching Documentation (`slack docs search`)\n\nSearch Slack's developer documentation directly from the terminal.\n\n```bash\nSLACK_CMD docs search \"\u003Cquery>\" --output=text --limit=5\n```\n\nUse `--output=text` for concise terminal-readable results. Use this when you are already running CLI commands and want to:\n\n- Check a Slack feature before implementing it\n- Verify API behavior or required scopes\n- Look up Block Kit elements, event types, or method parameters\n\n---\n\n## Step 4: Calling Web API Methods (`slack api`)\n\nCall any Slack Web API method directly. Run `SLACK_CMD api --help` for full details and examples.\n\nParameters are passed as positional `key=value` pairs (NOT `--key=value` flags):\n\n```bash\nSLACK_CMD api chat.postMessage channel=C0123456789 text=\"Hello from the CLI\"\n```\n\n**Important distinction**: `--team`, `--token`, `--json`, and `--data` are meta-flags (prefixed with `--`). API method parameters use positional `key=value` syntax without dashes.\n\n**Reference**: Full method list at \u003Chttps:\u002F\u002Fdocs.slack.dev\u002Freference\u002Fmethods.md>.\n\n---\n\n## Step 5: Authentication (`slack auth`)\n\n### When to run this flow\n\nSlack auth is **per-team**, not a single boolean. Run the seamless login flow below whenever any of these is true:\n\n- The developer is not authenticated to any team yet.\n- The developer wants to **add a new team \u002F workspace \u002F sandbox**, even if `SLACK_CMD auth list` already shows other teams.\n- The developer asks to log in, switch teams, or re-authenticate.\n\n`SLACK_CMD auth list` showing other teams is **not** a reason to skip login — those are different teams. Ask the developer which team they want, then run the flow.\n\n### Inspect existing auth (optional)\n\n```bash\nSLACK_CMD auth list\n```\n\nUse this to show the developer which teams are already authenticated, or to confirm a successful login. Do not treat a non-empty list as \"auth complete\" when the developer asked to log in to a new team.\n\n### Run the seamless login flow\n\nThe agent drives this end-to-end — **no separate terminal window, no browser confirmation**.\n\n`SLACK_CMD login --no-prompt` makes the CLI emit a single-use ticket and exit immediately instead of waiting on stdin. Slack itself renders the challenge code **inside a workspace modal** when the developer sends the `\u002Fslackauthticket` slash command — there is no browser step. The agent submits the challenge back to the CLI to complete login.\n\n**1. Start login and capture the ticket**\n\n```bash\nSLACK_CMD login --no-prompt\n```\n\nThe CLI prints a `\u002Fslackauthticket \u003Cticket>` slash command and exits. Capture the ticket — you will need it in step 4. Sample output:\n\n```text\n📋 Run the following slash command from any Slack channel in the workspace\n   you'd like to authenticate\n\n   \u002Fslackauthticket eyJ0eXAiOiJKV1QiLCJh…\n\n? Slack will then show you a challenge code. Submit it via:\n   slack login --ticket \u003Cticket> --challenge \u003Ccode>\n```\n\n**2. Hand the slash command to the developer**\n\nShow the full `\u002Fslackauthticket …` line and ask the developer to paste it into the message box of the Slack workspace they want to authenticate, then send it. Slack responds with a modal containing a short challenge code (e.g. `JDt1IK7X`).\n\n**3. Collect the challenge code**\n\nUse `AskUserQuestion` to ask the developer for the challenge code shown in the Slack modal. Wait for their answer — do not guess or default.\n\n**4. Complete login**\n\n```bash\nSLACK_CMD login --ticket \u003Cticket> --challenge \u003Ccode>\n```\n\nOn success the CLI returns the team name and ID. Verify with `SLACK_CMD auth list` and report the team back to the developer.\n\n**Troubleshooting**: tickets are single-use and time-limited. If step 4 fails with an invalid\u002Fexpired ticket or wrong challenge, restart from step 1 with a fresh `SLACK_CMD login --no-prompt` — do not retry the same ticket.\n\nUse `--team \u003Cteam_id>` on individual commands to target a specific workspace without switching globally.\n\n### Red flags — STOP\n\nIf you catch yourself thinking any of these, you are about to regress to the old broken flow:\n\n| Rationalization | Reality |\n|---|---|\n| \"`auth list` already shows teams, so login isn't needed.\" | Auth is per-team. The developer asked for a _new_ team — drive the flow. |\n| \"`slack login` needs browser confirmation, so I can't drive it.\" | False with `--no-prompt`. The challenge code appears in Slack's modal, not a browser. The agent runs both `slack login` invocations itself. |\n| \"I should tell the developer to run `slack login` in a separate terminal.\" | Never. Step 5 is the agent's job from start to finish. |\n\n**All of these mean: run `SLACK_CMD login --no-prompt` yourself and follow the four numbered steps above.**\n\n---\n\n## Step 6: Running an App Locally (`slack run`)\n\nRun `SLACK_CMD run --help` for all available flags.\n\n### Resolve the app or team target\n\nRun `SLACK_CMD app list` from the project directory to check for installed apps:\n\n- **If an app exists**: Use `--app=\u003Capp_id>` in the run command.\n- **If no apps are listed**: Use `--team=\u003Cteam_id>` instead (get the team ID from `SLACK_CMD auth list`).\n\n### Start the dev server in the background\n\nRun this command as a **background process** so the developer can continue working:\n\n**If an app ID was found:**\n\n```bash\ncd \u003Cproject-dir> && SLACK_CMD run --org-workspace-grant=all --app=\u003Capp_id>\n```\n\n**If no apps — use the team ID:**\n\n```bash\ncd \u003Cproject-dir> && SLACK_CMD run --org-workspace-grant=all --team=\u003Cteam_id>\n```\n\nTell the developer the app is running in the background. They can ask:\n\n- \"What's the status of the dev server?\" — to check on it\n- \"Show me the output from slack run\" — to see activity logs\n- \"Stop the dev server\" — to terminate the process\n\n---\n\n## Step 7: Managing the Manifest\n\nRun `SLACK_CMD manifest --help` for subcommands (`validate`, `info`) and the `--source local|remote` flag.\n\nUse `SLACK_CMD manifest validate` before deploying or when something seems wrong with the app configuration.\n\n---\n\n## Step 8: Other Commands\n\nFor any other command group (e.g., `trigger`, `datastore`, `env`, `collaborator`, `external-auth`, `deploy`), run `SLACK_CMD \u003Ccommand> --help` to discover subcommands and flags. Run `SLACK_CMD help` to see all available command groups.\n\n---\n\n## Notes\n\n- `SLACK_CMD` is a placeholder — always substitute the actual command name resolved in Step 1.\n- **Always run `--help`** before constructing a command you have not used in the current session.\n- Interactive commands (e.g., `slack trigger create` without `--trigger-def`) cannot be run in the background. Tell the developer to run these in a **new terminal window**. `slack login` is **not** in this category — drive it inline using the `--no-prompt` \u002F `--ticket` \u002F `--challenge` flow in Step 5.\n- `slack run` runs locally for development. `slack deploy` deploys to Slack's hosted infrastructure. These are different operations — do not confuse them.\n","# Slack CLI\n\nUse the Slack CLI to create, run, and manage Slack apps — including calling Web API methods directly and searching Slack developer documentation from the terminal.\n\nFor initial setup (sandbox creation, project scaffolding from templates), use the `slack:create-slack-app` skill instead.\n\n---\n\n## Step 1: Detect the Slack CLI\n\nResolve the path to the **public** Slack CLI before running any other command. We refer to the resolved value as `SLACK_CMD` — substitute it everywhere below. **Try 1a → 1b → 1c in order; do not skip ahead.**\n\n### 1a. Standard install path (preferred — no verification needed)\n\nThe official install scripts place the binary at a fixed per-user path. If the file exists, use it directly: only the install script writes to that path.\n\n- macOS \u002F Linux: `~\u002F.slack\u002Fbin\u002Fslack`\n- Windows: `%USERPROFILE%\\AppData\\Local\\slack-cli\\bin\\slack.exe` (or `%USERPROFILE%\\.slack-cli\\bin\\slack.exe` as a fallback)\n\nPOSIX shell:\n\n```bash\n[ -x \"$HOME\u002F.slack\u002Fbin\u002Fslack\" ] && echo \"$HOME\u002F.slack\u002Fbin\u002Fslack\"\n```\n\nPowerShell:\n\n```powershell\n$p = \"$env:USERPROFILE\\AppData\\Local\\slack-cli\\bin\\slack.exe\"\nif (Test-Path $p) { $p } elseif (Test-Path \"$env:USERPROFILE\\.slack-cli\\bin\\slack.exe\") { \"$env:USERPROFILE\\.slack-cli\\bin\\slack.exe\" }\n```\n\nIf a path is returned, set `SLACK_CMD` to that **absolute path** and proceed to Step 2. Do not also run `_fingerprint`.\n\n### 1b. `slack` on PATH (verify with fingerprint)\n\nIf 1a found nothing, try `slack` on PATH:\n\n```bash\nslack _fingerprint 2>\u002Fdev\u002Fnull\n```\n\nIf it outputs `d41d8cd98f00b204e9800998ecf8427e`, set `SLACK_CMD=slack` and proceed.\n\n### 1c. Ask about an alias, or install\n\nIf 1b fails or returns a different value, ask the developer using AskUserQuestion:\n\n- \"The `slack` command on your system doesn't appear to be the public Slack CLI. Do you have it installed under a different name or alias?\"\n- Options: \"Yes, it's aliased as...\" (let them provide the alias), \"No, I need to install it\"\n- If they provide an alias, verify it with `\u003Calias> _fingerprint 2>\u002Fdev\u002Fnull` and set `SLACK_CMD=\u003Calias>`.\n- If they need to install it, run:\n\n  ```text\n  curl -fsSL https:\u002F\u002Fdownloads.slack-edge.com\u002Fslack-cli\u002Finstall.sh | bash\n  ```\n\n  Then re-run **1a** — the install script will have written `~\u002F.slack\u002Fbin\u002Fslack`.\n\n**Common mistakes:** Don't use `which slack` to discover the binary — `which` resolves any shell alias and defeats the point of 1a. In Git Bash on Windows, use the POSIX probe form, not PowerShell.\n\n---\n\n## Step 2: Command Discovery via Help\n\n**Always run `SLACK_CMD \u003Ccommand> --help` before constructing a command you have not used in the current session.** Do not guess at flags — the help output is the source of truth.\n\n- `SLACK_CMD help` — lists all available command groups\n- `SLACK_CMD \u003Ccommand> --help` — shows subcommands, flags, and usage examples\n\n### Resolving `--app` and `--team` values\n\nWhen a command requires `--app` or `--team`:\n\n- **App ID**: Run `SLACK_CMD app list` from the project directory to see installed apps and their IDs.\n- **Team ID**: Run `SLACK_CMD auth list` to see authenticated workspaces and their team IDs.\n\n---\n\n## Step 3: Searching Documentation (`slack docs search`)\n\nSearch Slack's developer documentation directly from the terminal.\n\n```bash\nSLACK_CMD docs search \"\u003Cquery>\" --output=text --limit=5\n```\n\nUse `--output=text` for concise terminal-readable results. Use this when you are already running CLI commands and want to:\n\n- Check a Slack feature before implementing it\n- Verify API behavior or required scopes\n- Look up Block Kit elements, event types, or method parameters\n\n---\n\n## Step 4: Calling Web API Methods (`slack api`)\n\nCall any Slack Web API method directly. Run `SLACK_CMD api --help` for full details and examples.\n\nParameters are passed as positional `key=value` pairs (NOT `--key=value` flags):\n\n```bash\nSLACK_CMD api chat.postMessage channel=C0123456789 text=\"Hello from the CLI\"\n```\n\n**Important distinction**: `--team`, `--token`, `--json`, and `--data` are meta-flags (prefixed with `--`). API method parameters use positional `key=value` syntax without dashes.\n\n**Reference**: Full method list at \u003Chttps:\u002F\u002Fdocs.slack.dev\u002Freference\u002Fmethods.md>.\n\n---\n\n## Step 5: Authentication (`slack auth`)\n\n### When to run this flow\n\nSlack auth is **per-team**, not a single boolean. Run the seamless login flow below whenever any of these is true:\n\n- The developer is not authenticated to any team yet.\n- The developer wants to **add a new team \u002F workspace \u002F sandbox**, even if `SLACK_CMD auth list` already shows other teams.\n- The developer asks to log in, switch teams, or re-authenticate.\n\n`SLACK_CMD auth list` showing other teams is **not** a reason to skip login — those are different teams. Ask the developer which team they want, then run the flow.\n\n### Inspect existing auth (optional)\n\n```bash\nSLACK_CMD auth list\n```\n\nUse this to show the developer which teams are already authenticated, or to confirm a successful login. Do not treat a non-empty list as \"auth complete\" when the developer asked to log in to a new team.\n\n### Run the seamless login flow\n\nThe agent drives this end-to-end — **no separate terminal window, no browser confirmation**.\n\n`SLACK_CMD login --no-prompt` makes the CLI emit a single-use ticket and exit immediately instead of waiting on stdin. Slack itself renders the challenge code **inside a workspace modal** when the developer sends the `\u002Fslackauthticket` slash command — there is no browser step. The agent submits the challenge back to the CLI to complete login.\n\n**1. Start login and capture the ticket**\n\n```bash\nSLACK_CMD login --no-prompt\n```\n\nThe CLI prints a `\u002Fslackauthticket \u003Cticket>` slash command and exits. Capture the ticket — you will need it in step 4. Sample output:\n\n```text\n📋 Run the following slash command from any Slack channel in the workspace\n   you'd like to authenticate\n\n   \u002Fslackauthticket eyJ0eXAiOiJKV1QiLCJh…\n\n? Slack will then show you a challenge code. Submit it via:\n   slack login --ticket \u003Cticket> --challenge \u003Ccode>\n```\n\n**2. Hand the slash command to the developer**\n\nShow the full `\u002Fslackauthticket …` line and ask the developer to paste it into the message box of the Slack workspace they want to authenticate, then send it. Slack responds with a modal containing a short challenge code (e.g. `JDt1IK7X`).\n\n**3. Collect the challenge code**\n\nUse `AskUserQuestion` to ask the developer for the challenge code shown in the Slack modal. Wait for their answer — do not guess or default.\n\n**4. Complete login**\n\n```bash\nSLACK_CMD login --ticket \u003Cticket> --challenge \u003Ccode>\n```\n\nOn success the CLI returns the team name and ID. Verify with `SLACK_CMD auth list` and report the team back to the developer.\n\n**Troubleshooting**: tickets are single-use and time-limited. If step 4 fails with an invalid\u002Fexpired ticket or wrong challenge, restart from step 1 with a fresh `SLACK_CMD login --no-prompt` — do not retry the same ticket.\n\nUse `--team \u003Cteam_id>` on individual commands to target a specific workspace without switching globally.\n\n### Red flags — STOP\n\nIf you catch yourself thinking any of these, you are about to regress to the old broken flow:\n\n| Rationalization | Reality |\n|---|---|\n| \"`auth list` already shows teams, so login isn't needed.\" | Auth is per-team. The developer asked for a _new_ team — drive the flow. |\n| \"`slack login` needs browser confirmation, so I can't drive it.\" | False with `--no-prompt`. The challenge code appears in Slack's modal, not a browser. The agent runs both `slack login` invocations itself. |\n| \"I should tell the developer to run `slack login` in a separate terminal.\" | Never. Step 5 is the agent's job from start to finish. |\n\n**All of these mean: run `SLACK_CMD login --no-prompt` yourself and follow the four numbered steps above.**\n\n---\n\n## Step 6: Running an App Locally (`slack run`)\n\nRun `SLACK_CMD run --help` for all available flags.\n\n### Resolve the app or team target\n\nRun `SLACK_CMD app list` from the project directory to check for installed apps:\n\n- **If an app exists**: Use `--app=\u003Capp_id>` in the run command.\n- **If no apps are listed**: Use `--team=\u003Cteam_id>` instead (get the team ID from `SLACK_CMD auth list`).\n\n### Start the dev server in the background\n\nRun this command as a **background process** so the developer can continue working:\n\n**If an app ID was found:**\n\n```bash\ncd \u003Cproject-dir> && SLACK_CMD run --org-workspace-grant=all --app=\u003Capp_id>\n```\n\n**If no apps — use the team ID:**\n\n```bash\ncd \u003Cproject-dir> && SLACK_CMD run --org-workspace-grant=all --team=\u003Cteam_id>\n```\n\nTell the developer the app is running in the background. They can ask:\n\n- \"What's the status of the dev server?\" — to check on it\n- \"Show me the output from slack run\" — to see activity logs\n- \"Stop the dev server\" — to terminate the process\n\n---\n\n## Step 7: Managing the Manifest\n\nRun `SLACK_CMD manifest --help` for subcommands (`validate`, `info`) and the `--source local|remote` flag.\n\nUse `SLACK_CMD manifest validate` before deploying or when something seems wrong with the app configuration.\n\n---\n\n## Step 8: Other Commands\n\nFor any other command group (e.g., `trigger`, `datastore`, `env`, `collaborator`, `external-auth`, `deploy`), run `SLACK_CMD \u003Ccommand> --help` to discover subcommands and flags. Run `SLACK_CMD help` to see all available command groups.\n\n---\n\n## Notes\n\n- `SLACK_CMD` is a placeholder — always substitute the actual command name resolved in Step 1.\n- **Always run `--help`** before constructing a command you have not used in the current session.\n- Interactive commands (e.g., `slack trigger create` without `--trigger-def`) cannot be run in the background. Tell the developer to run these in a **new terminal window**. `slack login` is **not** in this category — drive it inline using the `--no-prompt` \u002F `--ticket` \u002F `--challenge` flow in Step 5.\n- `slack run` runs locally for development. `slack deploy` deploys to Slack's hosted infrastructure. These are different operations — do not confuse them.\n",{"name":5,"description":7},"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fslack-remote\u002Fskills\u002Fslack-cli",156,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace","https:\u002F\u002Fgithub.com\u002FCognitionAI","https:\u002F\u002Fcognition.ai\u002F","Makers of Devin, the AI software engineer.","2026-11-13 07:08:23",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill slack-cli",{"tool":39,"command":40},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill slack-cli",{"tool":42,"command":43},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill slack-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fslack-remote\u002Fskills\u002Fslack-cli\u002FSKILL.md",true,[],[48,54,61,67,74,81],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7BYBZ0CD4CBCPZHRZ551BNK","workflow","Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of \"workflow\", \"durable functions\", \"resumable\", \"workflow sdk\", \"queue\", \"event\", \"push\", \"subscribe\", or step-based orchestration.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002Fupstream\u002FSKILL.md",[],[],{"skillNo":62,"name":56,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7BYB1XSZHKHD8JZTQJ62JN0","Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7BYASGMK935J33E21N5WTW0","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7BY9WJERKSKEH9HK6E71GW2","vercel-storage","Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7BY9N034894YV2J9DCRZHYS","vercel-services","Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[],[]]