- /help: Shows available commands and skills with descriptions - /status: Quick dashboard overview across all domains - System health (disk, memory, updates) - Kubernetes status (nodes, pods, alerts) - Email summary (unread, urgent) - Calendar (today's events, next meeting) Both commands added to component-registry.json with aliases: - /help: /commands, /skills - /status: /overview, /dashboard Updated commands/README.md with new entries. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
60 lines
1.5 KiB
Markdown
60 lines
1.5 KiB
Markdown
---
|
|
name: help
|
|
description: Show available commands and skills
|
|
aliases: [commands, skills]
|
|
---
|
|
|
|
# /help Command
|
|
|
|
Show available commands and skills in this Claude Code configuration.
|
|
|
|
## When Invoked
|
|
|
|
Display a formatted list of available functionality:
|
|
|
|
```
|
|
📚 Claude Code Help
|
|
|
|
═══ Commands ═══
|
|
|
|
/pa <request> Personal assistant (natural language)
|
|
/gcal [today|tomorrow|week] Calendar agenda
|
|
/usage [today|week|month] Usage statistics
|
|
|
|
/sysadmin:health System health check
|
|
/sysadmin:update Package updates
|
|
/sysadmin:autonomy Set autonomy level
|
|
|
|
/k8s:cluster-status Kubernetes health
|
|
/k8s:deploy Deploy to cluster
|
|
/k8s:diagnose Troubleshoot issues
|
|
|
|
/programmer Code development
|
|
|
|
═══ Skills (Auto-Invoked) ═══
|
|
|
|
These activate automatically based on your request:
|
|
|
|
• gmail - "check my email", "urgent emails"
|
|
• gcal - "what's on today", "tomorrow's schedule"
|
|
• k8s - "cluster status", "pod health"
|
|
• sysadmin - "system health", "disk space"
|
|
• usage - "usage stats", "how many sessions"
|
|
|
|
═══ Tips ═══
|
|
|
|
• Use /pa for natural language requests
|
|
• Skills trigger automatically - just ask!
|
|
• Run /usage to see session statistics
|
|
```
|
|
|
|
## Implementation
|
|
|
|
Read from `state/component-registry.json` and format:
|
|
|
|
1. List commands with descriptions
|
|
2. List skills with trigger examples
|
|
3. Show tips for using the system
|
|
|
|
Keep output concise - this should fit in one screen.
|