Stats
Actions
Tags
From devglobe
Sets a status message on your DevGlobe profile. Invoke via /status 'Your message here' (max 100 chars). Checks API key from ~/.devglobe/api_key or env var, uses bash script to update.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devglobe:statusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Update the DevGlobe status message. User arguments: $ARGUMENTS
Update the DevGlobe status message. User arguments: $ARGUMENTS
$ARGUMENTS is empty: show error explaining usage: /devglobe:status Your message here (max 100 characters)~/.devglobe/api_key file and DEVGLOBE_API_KEY env var): show error asking to run /devglobe:setup YOUR_API_KEY first. Get key at https://devglobe.xyz. Contact: contact@devglobe.xyz~/.devglobe/api_key (or env var DEVGLOBE_API_KEY)$ARGUMENTS string (preserve spaces)echo '{"api_key": "THE_KEY", "message": "THE_MESSAGE"}' | ${CLAUDE_PLUGIN_ROOT}/scripts/update-status
Replace THE_KEY with the actual API key and THE_MESSAGE with the user's message (escape JSON special characters in the message).
{"ok": true} on success, {"error": "..."} on failure/devglobe:setup if the key might be wrongnpx claudepluginhub nako0/devglobe-extension --plugin devglobeConfigures Claude Code status lines using /statusline command, settings.json, Bash/Python/Node.js scripts. Covers JSON input, git integration, ANSI colors, helper functions, and troubleshooting.
Provides Claude Code with status context. Invoked via the /Status command or automatically when relevant.
Develops custom status lines for Claude Code to display git branch, context usage, model name, and session costs using bash scripts that process JSON stdin input.