ワンクリックでManusで任意のスキルを実行

始める

messaging

スター2

フォーク0

更新日2026年2月25日 19:36

Meta-skill for messaging/channel onboarding. Routes to setup-slack, setup-discord, setup-telegram, and setup-neovim.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

femtomc

femtomc/mu

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

messaging

Use this meta-skill when the user asks to onboard, repair, or verify channel messaging integration.

Subskills

setup-slack — Slack adapter setup, verification, and identity linking.
setup-discord — Discord adapter setup, verification, and identity linking.
setup-telegram — Telegram adapter setup, webhook flow, and identity linking.
setup-neovim — Neovim (mu.nvim) channel setup and identity linking.

Selection guide

Pick the channel-specific setup skill that matches the target adapter.
Run setup in an inspect -> patch config -> reload -> verify loop.
Confirm identities and delivery behavior before declaring completion.

Common patterns

Agent-First Bootstrap: Rather than asking the user for all details upfront, start the correct setup-* skill to investigate the current mu config, generate generic adapter secrets locally (if possible), and only ask the user for web-portal-specific secrets (e.g. Discord bot tokens or Slack bot tokens).
Verification Loop: After rewriting the channel configuration dict, use the setup-* pattern to reload the mu controller (mu cron ...) and explicitly check the latest service logs or remote test (/mu health) to ensure connectivity works before ending the run.
Identity Context Tying: During adapter onboarding, link the local OS user identity with their remote Slack/Discord/Telegram IDs so that subsequent mu exec jobs running offline can accurately ping the user back.

このリポジトリの他の Skills

同じリポジトリ

femtomc/mu

Runs core mu operator workflows for bounded investigation, CLI-first state operations, and session handoffs. Use when general mu execution or state-management guidance is needed.

2026-03-022

core

femtomc/mu

Meta-skill for core mu operating primitives. Routes to mu, programmable-ui, memory, tmux, and code-mode based on task shape.

2026-03-022

technical-writing

femtomc/mu

Produces clear, argument-driven technical prose. Use when drafting or reviewing systems papers, design docs, READMEs, PR descriptions, error messages, API references, or other technical communication.

2026-03-022

programmable-ui

femtomc/mu

Builds and debugs mu_ui UiDocs with schema-valid payloads, interaction wiring, and status/snapshot verification.

2026-02-262

memory

femtomc/mu

Runs cross-store memory retrieval and index maintenance workflows with bounded filters and timeline anchors. Use when querying prior context or repairing memory index health.

2026-02-262

control-flow

femtomc/mu

Defines compositional control-flow policies for orchestration DAGs (for example review-gated retry loops) using protocol-preserving transitions.

2026-02-262

name	messaging
description	Meta-skill for messaging/channel onboarding. Routes to setup-slack, setup-discord, setup-telegram, and setup-neovim.

messaging

Use this meta-skill when the user asks to onboard, repair, or verify channel messaging integration.

Subskills

setup-slack — Slack adapter setup, verification, and identity linking.
setup-discord — Discord adapter setup, verification, and identity linking.
setup-telegram — Telegram adapter setup, webhook flow, and identity linking.
setup-neovim — Neovim (mu.nvim) channel setup and identity linking.

Selection guide

Pick the channel-specific setup skill that matches the target adapter.
Run setup in an inspect -> patch config -> reload -> verify loop.
Confirm identities and delivery behavior before declaring completion.

Common patterns

Agent-First Bootstrap: Rather than asking the user for all details upfront, start the correct setup-* skill to investigate the current mu config, generate generic adapter secrets locally (if possible), and only ask the user for web-portal-specific secrets (e.g. Discord bot tokens or Slack bot tokens).
Verification Loop: After rewriting the channel configuration dict, use the setup-* pattern to reload the mu controller (mu cron ...) and explicitly check the latest service logs or remote test (/mu health) to ensure connectivity works before ending the run.
Identity Context Tying: During adapter onboarding, link the local OS user identity with their remote Slack/Discord/Telegram IDs so that subsequent mu exec jobs running offline can accurately ping the user back.