nm-Team/nmbot-skills / skills/nmbot-commands
nmbot-commands
VerifiedThis Skill provides a list of commands that nmBot supports. Use this Skill when you need to trigger a specific command of nmBot for the user. For feature details of each command, please refer to the nmbot-features Skill.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.6 KB |
| reference/command-list.md | markdown | 8.5 KB |
SKILL.md
View on GitHub---
name: nmbot-commands
description: This Skill provides a list of commands that nmBot supports. Use this Skill when you need to trigger a specific command of nmBot for the user. For feature details of each command, please refer to the nmbot-features Skill.
license: GPL-3.0
---
# nmBot Commands
nmBot supports a variety of commands that users can trigger to perform specific actions or access certain features of nmBot.
## Basis
Here are basic concepts related to nmBot commands:
- **Command**: A specific instruction that can be triggered by the user to perform a certain action or access a feature of nmBot. Each command is associated with a specific functionality and may require certain parameters or conditions to be met.
In Telegram, commands are typically triggered by sending a message that starts with a slash (/) followed by the command name, for example, `/help` to access the help command.
- **Specify the bot to trigger**: In group chats, users can specify which bot to trigger by including the bot's username in the command, for example, `/help@nmnmfunbot` to trigger the help command of nmBot. This is especially useful when there are multiple bots in the same group chat.
- **Command Parameters**: Some commands may require additional parameters to function properly. These parameters can be provided by the user when triggering the command, for example, `/whatis whatis` (or `/whatis@nmnmfunbot whatis`) to trigger the "whatis" command with "whatis" as the parameter to ask nmBot to explain what the "whatis" command does.
- **Command Aliases**: Some commands may have aliases, which are alternative names that can be used to trigger the same command. For example, the `/tosticker` command may also be triggered by `/ts` as an alias.
- **Command Scope**: Some commands may have a specific scope, meaning they can only be triggered in certain contexts or by certain users. For example, some commands may only be available in group chats, while others may only be available in private chats with the bot.
## Bot Usernames
nmBot is available at `https://t.me/nmnmfunbot`(aka. @nmnmfunbot). Users can interact with nmBot in private chats, groups, and channels.
nmBot Preview is the official preview version of nmBot, which may have new features that are not yet available in the stable version. It is available at `https://t.me/nmprebot`(aka. @nmprebot). Users can choose to use nmBot Preview to experience the latest features and improvements, but please note that nmBot Preview may be less stable than the stable version.
DO NOT INTERACT WITH OTHER BOTS CLAIMING TO BE nmBot, as they may be malicious and can compromise your security and privacy. Always make sure to interact with the official nmBot at the above-mentioned usernames.
## Command List
Please refer to the [command list reference](reference/command-list.md) for a comprehensive list of nmBot commands, including their descriptions, applicable chat types, required permissions, and more.
For details of each command's functionality, please refer to the nmbot-features Skill.
## Bot-to-Bot Communication
Telegram supports bot-to-bot communication, and a bot can send messages such as `/command@botusername` to another bot.
However, nmBot currently does **not** receive or respond to any messages sent by bots in group chats. This reflects nmBot's current behavior and may change in the future. Agents should not rely on another bot triggering nmBot commands in a group, even if Bot-to-Bot Communication Mode is enabled in @BotFather.
If a group workflow needs nmBot to act, ask a human user to trigger the command instead, or use the MCP API when the required capability is available there.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |