BookStack

**Quick judgment** A solid, focused integration for managing a BookStack wiki via API/CLI. It exposes the core content model (books, chapters, pages, shelves) and search, and is well‑suited for automation and synchronization workflows around documentation. It assumes you already run a BookStack instance and can configure API tokens. **Strengths** - Good coverage of core BookStack entities with explicit CRUD commands. - Supports both HTML and Markdown content, which is important for diverse documentation setups. - Clear CLI interface and usage examples make it straightforward to script and automate. - Simple configuration via environment variables; aligns with typical infra practices. **Key risks / limitations** - Destructive operations (delete_book, delete_chapter, delete_page) are exposed without any documented safeguards or dry‑run modes; misconfigured or over‑permissive use could cause data loss. - Safety and reliability rely heavily on the underlying BookStack API and the caller’s role/permissions; the skill does not appear to add its own guardrails or approval flows. - Functionality seems focused on content management; more advanced BookStack features (permissions management, attachments, user management, etc.) are not documented as supported. **Recommended scenarios** - Teams already using BookStack who want to automate documentation creation, updates, and restructuring from CI/CD, scripts, or integration services. - Building internal tools that search or surface BookStack content (e.g., knowledge bots, dashboards) where full‑text search and page retrieval are needed. - Migration or synchronization tasks where BookStack needs to stay in sync with other systems’ documentation, with programmatic control over books/chapters/pages/shelves. - Environments where documentation is treated as code and needs to be managed via scripts or infrastructure tooling rather than purely through the web UI.