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

about

Skill64 starsChanged 2 months agoMITView on GitHub

Show the plugin source — name, version, and repo URL. Works from CLI or messaging. Triggers on /about, /version, /agent:about, /agent:version, "qué versión", "what version", "about the plugin", "about clawcode".

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never hardcode the version — always read it at runtime.

    line 28
  2. Distinctive:

    Only respond when the user asks explicitly.

    line 73

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

/about — Plugin source & version

Show a small card with the plugin name, version, and repo URL. Answers "where does this agent come from?" / "what version am I running?".

Output format

🔌 ClawCode v<version>
Repo: https://github.com/crisandrews/ClawCode
Issues / stars: same link · feedback welcome

Steps

  1. Get the version — preferred: call the watchdog_ping MCP tool; it returns {ok, version, ts, plugins} and is the cheapest way to get the live value (no filesystem reads).

    Fallback if the tool isn't available: Bash:

    jq -r .version "$CLAUDE_PLUGIN_ROOT/.claude-plugin/plugin.json"

    Never hardcode the version — always read it at runtime.

  2. Detect the surface for bold formatting:
    • CLI / Telegram / WebChat: **bold**
    • WhatsApp: *bold* (single asterisk, no markdown headers)
    • Discord: **bold** as-is
    • iMessage: plain text, strip bold
  3. Print the card using REAL data. One card, no preamble, no persona-intro.

Format per surface

Tail-line language: the "Issues / stars …" line adapts to the user's conversation language. Default to EN if there's no clear signal. Known translations:

  • en → Issues / stars: same link · feedback welcome
  • es → Issues / stars: mismo link · feedback bienvenido
  • pt → Issues / stars: mesmo link · feedback bem-vindo

For other languages, keep the structure and translate the tail naturally.

CLI / WebChat

🔌 **ClawCode** v<version>
Repo: https://github.com/crisandrews/ClawCode
<tail-line-in-user-language>

WhatsApp

🔌 *ClawCode* v<version>
Repo: https://github.com/crisandrews/ClawCode
<tail-line-in-user-language>

Bold uses single * on WhatsApp (no markdown headers).

Telegram

Same as CLI/WebChat.

Important

  • /about and /version are aliases — same response.
  • Only respond when the user asks explicitly. Never volunteer this card unprompted.
  • One card. No extra commentary, no persona-intro ("Soy …"). The user asked for metadata, give them metadata.
  • For "what can I do?" the user wants /help, not /about — do not conflate.

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