octoclaw
Control OctoPrint 3D printer — monitor status, capture webcam snapshots, manage prints, analyze gcode, and detect errors. Use when the user asks about their 3D printer, print status, filament, temperatures, or wants to start/pause/cancel a print.
Best use case
octoclaw is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Control OctoPrint 3D printer — monitor status, capture webcam snapshots, manage prints, analyze gcode, and detect errors. Use when the user asks about their 3D printer, print status, filament, temperatures, or wants to start/pause/cancel a print.
Teams using octoclaw should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/octoclaw/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How octoclaw Compares
| Feature / Agent | octoclaw | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Control OctoPrint 3D printer — monitor status, capture webcam snapshots, manage prints, analyze gcode, and detect errors. Use when the user asks about their 3D printer, print status, filament, temperatures, or wants to start/pause/cancel a print.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# OctoClaw — OctoPrint Control Helper script: `scripts/octoprint.py` (relative to this skill directory). Config: `config.json` (same directory) with `octoprint_url` and `api_key`. Resolve all paths relative to this skill's directory. ## Commands All commands: `python3 <skill-dir>/scripts/octoprint.py <command> [args]` ### Status - `status-pretty` — Formatted status with temps, progress bar, ETA (show this to users) - `status` — Raw JSON - `check-errors` — Returns JSON with errors/warnings (temp anomalies, stalls, connection issues) ### Print Control - `print <filename>` — Start a print - `control <pause|resume|cancel>` — Control active print - `temp <tool0|bed> <temperature>` — Set temperature ### Files - `list-files` — List uploaded files - `upload <local-path> [remote-name]` — Upload gcode - `analyze <filepath>` — Extract gcode metadata (layers, time, filament, temps, dimensions) ### Webcam - `snapshot [output-path]` — Capture webcam image (default: /tmp with timestamp) ### Telegram (if configured) - `telegram-status` — Send formatted status to Telegram - `telegram-snapshot` — Send webcam snapshot with progress caption - `telegram-msg "message"` — Send custom message ## Workflows **Check on a print:** `status-pretty` → optionally `snapshot` → `check-errors` **Start a print:** `status-pretty` (verify Operational) → `list-files` or `upload` → optionally `analyze` → `print <file>` **Error detection:** `check-errors` returns critical errors (>15°C deviation, connection lost) and warnings (5-15°C deviation, stalled prints). Recommend pausing on temp issues, cancelling on critical errors. ## Formatting - Use `status-pretty` output for user display - Always show progress %, time remaining, ETA for active prints - Include temperature actual/target
Related Skills
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
reviewing-documentation
Use when reviewing documentation quality, auditing README or CLAUDE.md files, or standardizing AI instruction files.
review-docs
Review documentation (README.md and CLAUDE.md) for quality, completeness, and consistency. Use when asked to review docs, check documentation, validate README files, or audit CLAUDE.md coverage.
review-changelog
Review and complete new changelog entries after automated PR creation. Use when there's a new changelog PR with entries that have placeholder URLs or empty fields that need review. Triggers on phrases like "review changelog", "complete changelog entries", "fix changelog PR", or when user mentions a PR with changelog updates.
research-documentation
Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Trigger on "노션 검색", "조사해줘", "리서치 정리". For meeting prep use meeting-intelligence; for saving knowledge use knowledge-capture; for spec breakdown use spec-to-implementation.
release-manager
Assists with Morphir release management, including pre-release verification, changelog generation, and release coordination. Use when preparing releases, checking release readiness, or managing version bumps.
reindex-docs
Re-index all PDF and HTML documents, update index.html, and commit/push changes to the repository
readme-standards
README template structure and required sections
readme-generator
Generate a production-quality README.md by analyzing project structure, framework, and code
readme-generate
Generate comprehensive README files from code analysis
quality-documentation-manager
Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.
protocol-reverse-engineering
Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocol...