How do I install the About skill?

Run npx skillmds@latest add crisandrews/about in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is About safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with About?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is About free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

crisandrews (@crisandrews) published this skill. Their other Agent Skills are listed on their SkillMD profile.

About by crisandrews — Agent Skill

Name: About
Author: crisandrews

File contents

/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

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

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

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

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.

---name: aboutdescription: 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".---# /about — Plugin source & versionShow 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/ClawCodeIssues / stars: same link · feedback welcome```## Steps1. **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.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 bold3. **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).### TelegramSame 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.

Frequently asked questions

About