agentleFS
Sign inStart free
crisandrewscrisandrews/ClawCode/skills/help/SKILL.md

help

Skill64 starsChanged 2 months agoMITView on GitHub

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".

76 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 9 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 9 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 1 is distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 57 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Detect the surface: If the incoming message has a <channel source="..."> marker, you're on a messaging channel.

    line 13
  2. Very specific:

    Leave includeTools: false for the user-facing help — MCP tools are agent-invoked, not user-typed.

    line 19
  3. Distinctive:

    Adapt formatting to the channel: after the tool output:

    line 23
  4. Very specific:

    Call list_commands({ format: "table", includeTools: false }).

    line 39
  5. Very specific:

    Call list_commands({ format: "compact", includeTools: false }).

    line 43
  6. Very specific:

    Keep the response short on mobile channels.

    line 48
  7. Very specific:

    If the user wants the internals ("tools", "MCP"), call with includeTools: true so they see them too.

    line 49
  8. Very specific:

    If nothing comes back, something's wrong with the install — suggest /agent:doctor.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 57 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free