Skip to content
Skills Library
AI & agents · Learning & explanation

help

/help

List available commands the user can invoke. Works from CLI or messaging channels. Triggers on /help, /commands, /agent:help, "qué comandos puedo usar", "help commands".

Repository
clawcode ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

List available commands the user can invoke. Works from CLI or messaging channels. Triggers on /help, /commands, /agent:help, "qué comandos puedo usar", "help commands".

Triggers from the description

qué comandos puedo usarhelp commands
Original author description

List available commands the user can invoke. Works from CLI or messaging channels. Triggers on /help, /commands, /agent:help, "qué comandos puedo usar", "help commands".

How it works

  1. Steps
  2. Example flows
  3. Notes
Original SKILL.md headings · 46 lines, 319 words
SKILL.md preview
---
name: help
description: List available commands the user can invoke. Works from CLI or messaging channels. Triggers on /help, /commands, /agent:help, "qué comandos puedo usar", "help commands".
user-invocable: true
---

# Help — list commands

Show a concise, LIVE list of all available commands. Never hardcode — always pull from the `list_commands` MCP tool so recently installed or removed skills are reflected.

## Steps

1. **Detect the surface.** If the incoming message has a `<channel source="...">` marker, you're on a messaging channel. Otherwise you're on CLI or WebChat.

2. **Call `list_commands`** with the right format:
   - **CLI / WebChat:** `list_commands({ format: "table", includeTools: false })` — grouped markdown, readable.
   - **Messaging (WhatsApp, Telegram, Discord, iMessage):** `list_commands({ format: "compact", includeTools: false })` — one line per command, mobile-friendly.

   Leave `includeTools: false` for the user-facing help — MCP tools are agent-invoked, not user-typed. Users who want the internals can ask "what MCP tools do you have?" and you call with `includeTools: true`.

3. **Print the output** from the tool as-is. Do not rewrite or reorder.

4. **Adapt formatting to the channel** after the tool output:
   - WhatsApp: strip `**bold**` → `*bold*`, remove markdown headers if too noisy
   - Telegram: keep `**bold**` or convert to HTML
   - Discord: markdown as-is
   - iMessage: strip markdown to plain text
   - CLI / WebChat: markdown as-is

5. **Append a short native-tools note** at the end (only on CLI):
   ```
   Native Claude Code commands (CLI only): /status /usage /cost /compact /clear /mcp /model /help
   ```

## Example flows

### CLI user asks `/help`

Call `list_commands({ format: "table", includeTools: false })`. Print the returned markdown. Append the native-tools note.

### WhatsApp user says "what can you do?"

Call `list_commands({ format: "compact", includeTools: false })`. Convert any `**bold**` to `*bold*`. Don't include the native-tools note (doesn't apply).

## Notes

- `/help` and `/commands` are aliases.
- Keep the response short on mobile channels. `compact` format handles that.
- If the user wants the internals ("tools", "MCP"), call with `includeTools: true` so they see them too.
- If nothing comes back, something's wrong with the install — suggest `/agent:doctor`.

Versions

RepositoryScoreLicence
This page · crisandrews/clawcode100MIT
Ovich/charrette100MIT
davepoon/buildwithclaude100MIT
lamngockhuong/aiteamkit100MIT
The01Geek/prflow100MIT
Cruna-Noise-To-Signal/cruna-plugins100Apache-2.0
wookiya1364/scv-claude-code100MIT
oliver-kriska/claude-elixir-phoenix100MIT
jeffersonvalente/cardume100MIT

Database snapshot: 13.11.2026 · package version 8c58dc0f4400 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90guide
    Lists what the Cycling Training coach can do, with one line per command and a suggestion of where to start for this athlete. Use for /guide and whenever the athlete asks "qué puedo hacer", "qué comandos hay", "ayuda", "por dónde empiezo", "what can you do", "what commands are…
  • 100agents
    List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.
  • 100prime-help
    Quick-reference card for the prime-agent plugin: which skill to use when, commands, setup, and known gotchas. One-shot display. Trigger: /prime-help, "prime help", "how do I use prime-agent", "one-shot or worker?".
  • 95kirocrew-commands
    Complete CLI reference for Kiro Crew commands. Use for help, commands, setup, how to, what can you do, getting started, onboarding.
  • 95glab-help
    Display help information for glab commands and subcommands. Use when learning glab commands, viewing command syntax, or getting usage examples. Triggers on help, command help, usage, glab help.
  • 95ponytail-help
    Quick reference for ponytail levels, skills and commands. One-shot display. Use for /ponytail-help, "ponytail help", "how do I use ponytail".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.