capabilities
/capabilities
Show what this Deus instance can do — installed skills, available tools, and system info. Read-only. Use when the user asks what the bot can do, what's installed, or runs /capabilities.
- Author
- sliamh11 ↗
- Repository
- Deus ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Show what this Deus instance can do — installed skills, available tools, and system info. Read-only. Use when the user asks what the bot can do, what's installed, or runs /capabilities.
Original author description
Show what this Deus instance can do — installed skills, available tools, and system info. Read-only. Use when the user asks what the bot can do, what's installed, or runs /capabilities.
How it works
- How to gather the information
- Report format
SKILL.md preview
--- name: capabilities description: Show what this Deus instance can do — installed skills, available tools, and system info. Read-only. Use when the user asks what the bot can do, what's installed, or runs /capabilities. --- # /capabilities — System Capabilities Report Generate a structured read-only report of what this Deus instance can do. **Main-channel check:** Only the main channel has `/workspace/project` mounted. Run: ```bash test -d /workspace/project && echo "MAIN" || echo "NOT_MAIN" ``` If `NOT_MAIN`, respond with: > This command is available in your main chat only. Send `/capabilities` there to see what I can do. Then stop — do not generate the report. ## How to gather the information Run these commands and compile the results into the report format below. ### 1. Installed skills List skill directories available to you: ```bash ls -1 /home/node/.claude/skills/ 2>/dev/null || echo "No skills found" ``` Each directory is an installed skill. The directory name is the skill name (e.g., `agent-browser` → `/agent-browser`). ### 2. Available tools Read the allowed tools from your SDK configuration. You always have access to: - **Core:** Bash, Read, Write, Edit, Glob, Grep - **Web:** WebSearch, WebFetch - **Orchestration:** Task, TaskOutput, TaskStop, TeamCreate, TeamDelete, SendMessage - **Other:** TodoWrite, ToolSearch, Skill, NotebookEdit - **MCP:** mcp__deus__* (messaging, tasks, group management) ### 3. MCP server tools The Deus MCP server exposes these tools (via `mcp__deus__*` prefix): - `send_message` — send a message to the user/group - `schedule_task` — schedule a recurring or one-time task - `list_tasks` — list scheduled tasks - `pause_task` — pause a scheduled task - `resume_task` — resume a paused task - `cancel_task` — cancel and delete a task - `update_task` — update an existing task - `register_group` — register a new chat/group (main only) ### 4. Container skills (Bash tools) Check for executable tools in the container: ```bash which agent-browser 2>/dev/null && echo "agent-browser: available" || echo "agent-browser: not found" ``` ### 5. Group info ```bash ls /workspace/group/CLAUDE.md 2>/dev/null && echo "Group memory: yes" || echo "Group memory: no" ls /workspace/extra/ 2>/dev/null && echo "Extra mounts: $(ls /workspace/extra/ 2>/dev/null | wc -l | tr -d ' ')" || echo "Extra mounts: none" ``` ## Report format Present the report as a clean, readable message. Example: ``` 📋 *Deus Capabilities* *Installed Skills:* • /agent-browser — Browse the web, fill forms, extract data • /capabilities — This report (list all found skills) *Tools:* • Core: Bash, Read, Write, Edit, Glob, Grep • Web: WebSearch, WebFetch • Orchestration: Task, TeamCreate, SendMessage • MCP: send_message, schedule_task, list_tasks, pause/resume/cancel/update_task, register_group *Container Tools:* • agent-browser: ✓ *System:* • Group memory: yes/no • Extra mounts: N directories • Main channel: yes ``` Adapt the output based on what you actually find — don't list things that aren't installed. **See also:** `/status` for a quick health check of session, workspace, and tasks.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sliamh11/Deus | 100 | MIT |
| intentic/intentic | 100 | MIT |
| harnessmd/munder-difflin | 100 | MIT |
| brocef/tcw | 100 | Apache-2.0 |
| tansuasici/claude-code-kit | 100 | MIT |
| kazukinagata/shinkoku | 95 | MIT |
| agencyenterprise/draft-detective | 90 | MIT |
Database snapshot: 13.11.2026 · package version 5767b135b2c5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100customize
Add new capabilities or modify Deus behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants. - 96guide
Ask about rp1 capabilities, discover skills, and get workflow guidance. - 100find-skills
List installed skills, search the skill registry, install new skills, and manage workspace extensions. Use when the user asks to find, install, list, or configure skills, or mentions skill registry, extensions, or workspace capabilities. - 100health
Check devkit health — which external CLIs (codex, gemini, gh, rtk, sg, gcli) are installed, which agents are available, which skills are ready to use. Use when asked about devkit health, devkit status, "is devkit working?", "what's installed?", "what devkit capabilities do I… - 81skills-registry
Use when looking up available tools, skills, commands, agents, or plugins - 100x-integration
X (Twitter) integration for Deus. Post tweets, like, reply, retweet, and quote. Use for setup, testing, or troubleshooting X functionality. Triggers on "setup x", "x integration", "twitter", "post tweet", "tweet".