Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

verify-bridge

Sterne32

Forks14

Aktualisiert29. April 2026 um 10:39

Precondition check that mcp__claude-slack-bridge is installed in the current repo. Reads cwd/.mcp.json and verifies a `claude-slack-bridge` entry exists under `mcpServers`. Exits non-zero with a fix-it message if the entry is missing. Use as a standalone precondition for /process-setup, /process, or any flow that depends on the Slack bridge MCP being declared. Does not check whether the bridge container is running — only that the repo declares the server.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

tomeraitz

tomeraitz/claude-slack-bridge

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name

verify-bridge

description

verify-bridge — confirm the Slack bridge MCP is declared in this repo

Verify that mcp__claude-slack-bridge is installed in the current repo by reading cwd/.mcp.json. The file must exist and must contain a server entry whose key is claude-slack-bridge (the MCP tool prefix mcp__claude-slack-bridge__* is derived from this key).

import json, os
mcp_path = os.path.join(os.getcwd(), ".mcp.json")
if not os.path.exists(mcp_path):
    # hard fail — see message below
    ...
with open(mcp_path) as f:
    cfg = json.load(f)
if "claude-slack-bridge" not in (cfg.get("mcpServers") or {}):
    # hard fail — see message below
    ...

If either check fails, print this exact message and exit non-zero. Do not offer to write the entry yourself, do not continue:

mcp__claude-slack-bridge is not installed in this repo. Add a claude-slack-bridge entry under mcpServers in .mcp.json (see the project README for the exact docker-exec snippet), then re-run the calling workflow.

Do not check whether the bridge container is running — only that the repo declares the server. Runtime health is the caller's problem, not this skill's.

On success, print one short confirmation line and exit zero:

verify-bridge: ok (claude-slack-bridge declared in .mcp.json)

Mehr aus diesem Repository

gleiches Repository

process-setup

tomeraitz/claude-slack-bridge

One-time per-repo configuration for the /process workflow. Delegates verification that mcp__claude-slack-bridge is installed (via the verify-bridge skill), task-manager setup end-to-end (via the build-task-manager skill, which generates `.claude/skills/claude-slack-bridge_list-tasks/SKILL.md`), and the three workflow phases — design, plan, and run-plan — each via its own leaf skill (`build-design-workflow`, `build-plan-workflow`, `build-run-plan-flow`) spawned directly so AskUserQuestion is never nested more than one level deep. Use when the user runs /process-setup or asks to set up / re-configure the /process workflow for this repository.

2026-05-2732

build-process-skill

tomeraitz/claude-slack-bridge

Generate the `/process` orchestrator command for this repo. Writes `.claude/commands/process.md` — the local entry point that reads `.claude/process-template.json` and walks through the configured workflow steps in order, dispatching to each step's slash command and routing to `/required-fixes` when a `/review` step surfaces reviewer comments. Returns a status of `configured` (with the path written) or `skipped` (when the file already exists and the user opts not to overwrite). Use as the process-command phase of /process-setup.

2026-05-2132

build-plan-workflow

tomeraitz/claude-slack-bridge

Configure the plan phase of the /process workflow. Asks whether the user wants a plan step at all (skip-able), then asks whether they already have a planning process (e.g. an existing /plan command or skill). If they do, reads it and inspects whether it already commits/pushes/opens a PR; whatever is missing gets added. If they don't, asks what kind of plan doc the step should produce and bakes that prompt directly into the wrapper. The ONLY file this skill writes is `.claude/skills/claude-slack-bridge_plan/SKILL.md` — a wrapper skill that runs the user's plan flow (`<@ref-plan-flow>`) or an inline plan prompt when none exists, saves the output to the fixed path `.roadmap_features/<branch>/plan/feature_plan.md` (creating the folder if missing), commits and pushes if the inner flow didn't, opens a GitHub PR, and sends a response back to the caller. Never scaffolds a separate `/plan` slash command. Returns a status of `configured` (with the captured reference) or `skipped` (with the literal label `plan-workflow:

2026-05-1832

build-design-workflow

tomeraitz/claude-slack-bridge

Configure the design phase of the /process workflow. Asks whether the user wants a design step at all (skip-able), then asks whether they already have a design process (e.g. an existing /design command or skill). If they do, reads it and inspects whether it already commits/pushes/opens a PR; whatever is missing gets added. If they don't, asks what kind of design doc the step should produce and bakes that prompt directly into the wrapper. The ONLY file this skill writes is `.claude/skills/claude-slack-bridge_design/SKILL.md` — a wrapper skill that runs the user's design flow (`<@ref-design-flow>`) or an inline design prompt when none exists, saves the output to `.roadmap_features/<feature>/design/feature_design.md` (creating the folder if missing), commits and pushes if the inner flow didn't, opens a GitHub PR, and sends a response back to the caller. Never scaffolds a separate `/design` slash command. Returns a status of `configured` (with the captured reference) or `skipped` (with the literal label `design-w

2026-05-1832

build-run-plan-flow

tomeraitz/claude-slack-bridge

Configure the run-plan (implementation) phase of the /process workflow. Asks whether the user wants a run-plan step at all (skip-able), then asks whether they already have a run-plan process (e.g. an existing /run-plan command or skill that takes a plan doc and implements it). If they do, reads it and inspects whether it already commits/pushes/opens a PR; whatever is missing gets added. If they don't, bakes a simple inline implementation prompt directly into the wrapper. The ONLY file this skill writes is `.claude/skills/claude-slack-bridge_run-plan/SKILL.md` — a wrapper skill that runs the user's run-plan flow (`<@ref-run-plan-flow>`) or an inline implementation prompt when none exists, commits and pushes if the inner flow didn't, opens a GitHub PR, and sends a response back to the caller. Never scaffolds a separate `/run-plan` slash command. Returns a status of `configured` (with the captured reference) or `skipped` (with the literal label `run-plan-flow: skip`). Use as the run-plan-flow phase of /process-s

2026-05-1832

build-task-manager

tomeraitz/claude-slack-bridge

Set up the task manager for this repo end-to-end: pick a manager (Linear / Jira / GitHub Issues / Notion / None), pick an integration method (MCP / CLI / plugin / API), verify the chosen integration is installed (offering to help install, wait for the user, or skip), ask the user how to fetch their tasks and try it (suggesting likely configuration issues on failure), then write `.claude/skills/claude-slack-bridge_list-tasks/SKILL.md` and verify it runs end-to-end. Returns a status of `configured` (with task_manager_label, task_manager_slug, integration_method) or `skipped`. Use as the task-manager phase of /process-setup.

2026-04-2932

name

verify-bridge

description

verify-bridge — confirm the Slack bridge MCP is declared in this repo

import json, os
mcp_path = os.path.join(os.getcwd(), ".mcp.json")
if not os.path.exists(mcp_path):
    # hard fail — see message below
    ...
with open(mcp_path) as f:
    cfg = json.load(f)
if "claude-slack-bridge" not in (cfg.get("mcpServers") or {}):
    # hard fail — see message below
    ...

If either check fails, print this exact message and exit non-zero. Do not offer to write the entry yourself, do not continue:

mcp__claude-slack-bridge is not installed in this repo. Add a claude-slack-bridge entry under mcpServers in .mcp.json (see the project README for the exact docker-exec snippet), then re-run the calling workflow.

Do not check whether the bridge container is running — only that the repo declares the server. Runtime health is the caller's problem, not this skill's.

On success, print one short confirmation line and exit zero:

verify-bridge: ok (claude-slack-bridge declared in .mcp.json)