Run any Skill in Manus with one click

$pwd:

slack-cli

Name: Slack Cli
Author: ericmjl

// Use Slack CLI (`slack`) for app lifecycle and workspace operations including login/logout, create/init, run/deploy, manifest validation, trigger management, app install/uninstall, environment management, and diagnostics. Use when users ask to run or troubleshoot commands like `slack create`, `slack run`, `slack deploy`, `slack trigger`, `slack manifest`, `slack auth`, `slack activity`, `slack datastore`, `slack env`, or request help-first progressive discovery with `slack help` and `slack SUBCOMMAND --help`, plus version/documentation alignment and stale-skill refresh.

Run Skill in Manus

$ git log --oneline --stat

stars:34

forks:2

updated:May 7, 2026 at 23:51

File Explorer

2 files

SKILL.md

readonly

name	slack-cli
description	Use Slack CLI (`slack`) for app lifecycle and workspace operations including login/logout, create/init, run/deploy, manifest validation, trigger management, app install/uninstall, environment management, and diagnostics. Use when users ask to run or troubleshoot commands like `slack create`, `slack run`, `slack deploy`, `slack trigger`, `slack manifest`, `slack auth`, `slack activity`, `slack datastore`, `slack env`, or request help-first progressive discovery with `slack help` and `slack SUBCOMMAND --help`, plus version/documentation alignment and stale-skill refresh.
license	MIT

Slack CLI

Use this skill when working with the Slack command-line tool (slack) for local development, app lifecycle, deployment, and command troubleshooting.

Default mindset: discover progressively with --help, verify against official docs, and keep both local CLI and this skill content current.

Requirements

Slack CLI installed and available as slack
Slack account/team authorization for operations that require workspace access

What This Skill Covers

Command discovery and flag lookup via help output
Local project setup (create, init, run)
Deployment and lifecycle operations (deploy, install, uninstall, delete)
App metadata and configuration (manifest, env, function, external-auth)
Operational support (activity, doctor, version, upgrade)
Version and documentation alignment (installed CLI vs official docs)
Self-maintenance when skill guidance is stale

Official Documentation

Main docs: https://docs.slack.dev/tools/slack-cli/
Command guide: https://docs.slack.dev/tools/slack-cli/guides/running-slack-cli-commands
Command reference root: https://docs.slack.dev/tools/slack-cli/reference/commands/slack

Default Workflow

Clarify intent (discover command syntax, debug, or execute lifecycle action).
Start from help and progressively narrow:
- slack help
- slack SUBCOMMAND --help
- slack SUBCOMMAND SUBCOMMAND --help (when nested commands exist)
Cross-check syntax/flags with official docs before recommending final commands.
Identify whether the task is read-only/help-only or state-changing.
For state-changing commands, confirm target workspace/app context (--team, --app) before execution.
Prefer explicit flags over interactive prompts for reproducibility.

Help-Only Study Mode

If a user asks to "study the CLI" or "do not run real operations":

Restrict work to help output and documentation.
Do not execute commands that create, modify, deploy, install, uninstall, or delete resources.
Build a command map from help pages and global flags.
Cross-check discovered commands against official docs links.
Return recommended command templates and safe next steps.

Version and Documentation Alignment

Before making strong command recommendations:

Determine the installed CLI version (slack version) when command execution is allowed.
Compare installed behavior/help output with the current official docs.
If docs and local help conflict, prefer local --help as runtime truth and explicitly report the mismatch.
If the installed CLI appears older than docs, recommend that the user upgrade the local Slack CLI before continuing.

If command execution is not allowed, state that version validation was not performed and recommend the user run slack version.

Self-Improving Maintenance Rules

If this skill appears stale relative to current --help output or official docs:

Update SKILL.md and references/command-map.md with corrected commands, flags, and workflows.
Keep --help-first progressive discovery as the primary workflow.
Record new or changed commands in the reference summary.
Call out meaningful behavioral changes (renamed commands, deprecated flags, new subcommands).
If stale guidance could cause user errors, prioritize fixing the skill before running high-risk operations.

Global Flags to Check First

-a, --app: target app ID or environment
-w, --team: target workspace/org
--token: token for a team context
-f, --force: continue on warnings
-v, --verbose: debug output
--no-color: plain output
-s, --skip-update: skip CLI update checks

Common Command Patterns

slack help
slack <subcommand> --help
slack create <name>
slack run
slack deploy --team <TEAM_ID_OR_NAME>
slack manifest validate
slack trigger list

References

For a command overview and frequently used flags, read references/command-map.md.

related-skills.json

same repository

atomic-commits.md

from "ericmjl/skills"

Break unstaged or mixed changes into small, atomic, logical git commits with Conventional Commit messages. Use when the user asks to commit, stage, or split changes — e.g. 'help me commit', 'commit my changes', 'break these into logical commits', 'what should I commit first', 'stage my changes', 'commit atomically', or 'make atomic commits'. Uses git diff, git add -p, and Conventional Commits (feat:/fix:/refactor:/chore:/docs:/test:/style:/perf:/build:/ci).

2026-05-1834

stacked-pr-decomposition.md

from "ericmjl/skills"

Break long-lived pull request branches into a mergeable stack of small PRs with clear dependency order and story flow. Use when a branch has grown too large, when the user asks to split a PR into stacked PRs, or when each PR must be reviewable in about 5 minutes while preserving logical narrative across the stack.

2026-05-1534

coherent-writing.md

from "ericmjl/skills"

Improve coherence in drafts by diagnosing broken flow, rewriting transitions, aligning paragraph purpose, and preserving author voice. Use when a user says things like 'make this coherent', 'tighten the flow', 'this feels choppy', 'can you smooth transitions', or asks to revise prose in Markdown, notes, essays, blog posts, emails, or docs so ideas connect cleanly from sentence to sentence and section to section.

2026-05-1234

gh-cli.md

from "ericmjl/skills"

Use GitHub CLI (gh) for common operations like creating PRs, viewing GitHub Actions logs, managing issues, reviewing PRs, and more. When merging PRs via gh, prefer rebase merge over squash or merge commits unless repo policy or the user explicitly requests otherwise.

2026-05-0734

mempalace.md

from "ericmjl/skills"

Use the MemPalace CLI to persist, search, and manage AI memory across sessions. Triggers whenever the user asks to remember, recall, save, store, or retrieve information that should persist across conversations — including past decisions, preferences, facts about people or projects, conversation history, and any verbatim content the user wants preserved. Also triggers when the user mentions "palace", "wings", "rooms", "drawers", "knowledge graph", "AAAK", or when they want to search through historical context, traverse connections between topics, or check what their AI knows. Mirrors the MemPalace MCP server tools: each CLI command maps to an MCP tool with an equivalent trigger condition.

2026-04-0834

design-driven-dev.md

from "ericmjl/skills"

Guide for design-driven development with prescribed folder structure. New features use full workflow (HLD → LLD → EARS). Bug fixes skip doc creation but verify intent coherence.

2026-03-2834

package.json

"author": "ericmjl"

"repository": "ericmjl/skills"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Network and Computer Systems AdministratorsComputer and Mathematical Occupations15-1244L4

name	slack-cli
description	Use Slack CLI (`slack`) for app lifecycle and workspace operations including login/logout, create/init, run/deploy, manifest validation, trigger management, app install/uninstall, environment management, and diagnostics. Use when users ask to run or troubleshoot commands like `slack create`, `slack run`, `slack deploy`, `slack trigger`, `slack manifest`, `slack auth`, `slack activity`, `slack datastore`, `slack env`, or request help-first progressive discovery with `slack help` and `slack SUBCOMMAND --help`, plus version/documentation alignment and stale-skill refresh.
license	MIT

Slack CLI

Use this skill when working with the Slack command-line tool (slack) for local development, app lifecycle, deployment, and command troubleshooting.

Default mindset: discover progressively with --help, verify against official docs, and keep both local CLI and this skill content current.

Requirements

Slack CLI installed and available as slack
Slack account/team authorization for operations that require workspace access

What This Skill Covers

Command discovery and flag lookup via help output
Local project setup (create, init, run)
Deployment and lifecycle operations (deploy, install, uninstall, delete)
App metadata and configuration (manifest, env, function, external-auth)
Operational support (activity, doctor, version, upgrade)
Version and documentation alignment (installed CLI vs official docs)
Self-maintenance when skill guidance is stale

Official Documentation

Main docs: https://docs.slack.dev/tools/slack-cli/
Command guide: https://docs.slack.dev/tools/slack-cli/guides/running-slack-cli-commands
Command reference root: https://docs.slack.dev/tools/slack-cli/reference/commands/slack

Default Workflow

Clarify intent (discover command syntax, debug, or execute lifecycle action).
Start from help and progressively narrow:
- slack help
- slack SUBCOMMAND --help
- slack SUBCOMMAND SUBCOMMAND --help (when nested commands exist)
Cross-check syntax/flags with official docs before recommending final commands.
Identify whether the task is read-only/help-only or state-changing.
For state-changing commands, confirm target workspace/app context (--team, --app) before execution.
Prefer explicit flags over interactive prompts for reproducibility.

Help-Only Study Mode

If a user asks to "study the CLI" or "do not run real operations":

Restrict work to help output and documentation.
Do not execute commands that create, modify, deploy, install, uninstall, or delete resources.
Build a command map from help pages and global flags.
Cross-check discovered commands against official docs links.
Return recommended command templates and safe next steps.

Version and Documentation Alignment

Before making strong command recommendations:

Determine the installed CLI version (slack version) when command execution is allowed.
Compare installed behavior/help output with the current official docs.
If docs and local help conflict, prefer local --help as runtime truth and explicitly report the mismatch.
If the installed CLI appears older than docs, recommend that the user upgrade the local Slack CLI before continuing.

If command execution is not allowed, state that version validation was not performed and recommend the user run slack version.

Self-Improving Maintenance Rules

If this skill appears stale relative to current --help output or official docs:

Update SKILL.md and references/command-map.md with corrected commands, flags, and workflows.
Keep --help-first progressive discovery as the primary workflow.
Record new or changed commands in the reference summary.
Call out meaningful behavioral changes (renamed commands, deprecated flags, new subcommands).
If stale guidance could cause user errors, prioritize fixing the skill before running high-risk operations.

Global Flags to Check First

-a, --app: target app ID or environment
-w, --team: target workspace/org
--token: token for a team context
-f, --force: continue on warnings
-v, --verbose: debug output
--no-color: plain output
-s, --skip-update: skip CLI update checks

Common Command Patterns

slack help
slack <subcommand> --help
slack create <name>
slack run
slack deploy --team <TEAM_ID_OR_NAME>
slack manifest validate
slack trigger list

References

For a command overview and frequently used flags, read references/command-map.md.

slack-cli

Slack CLI

Requirements

What This Skill Covers

Official Documentation

Default Workflow

Help-Only Study Mode

Version and Documentation Alignment

Self-Improving Maintenance Rules

Global Flags to Check First

Common Command Patterns

References

More from this repository

More from this repository

Slack CLI

Requirements

What This Skill Covers

Official Documentation

Default Workflow

Help-Only Study Mode

Version and Documentation Alignment

Self-Improving Maintenance Rules

Global Flags to Check First

Common Command Patterns

References