Receber por email
← Voltar para o catálogo

about

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

61estrelas
Atualizado há 3 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add crisandrews/ClawCode

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/about-crisandrews/svg)](https://www.skillteca.com.br/skills/about-crisandrews)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

/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: ``bash jq -r .version "$CLAUDE_PLUGIN_ROOT/.claude-plugin/plugin.json" ``

Never hardcode the version — always read it at runtime.

  1. Detect the surface for bold formatting:
  2. CLI / Telegram / WebChat: bold
  3. WhatsApp: bold (single asterisk, no markdown headers)
  4. Discord: bold as-is
  5. iMessage: plain text, strip bold
  1. 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.
Compartilhar X LinkedIn