Skip to main content

BookStack Integration and Skills Configuration Status — 2026-09-12

BookStack Integration and Skills Configuration Status

Summary

BookStack has been actively used as the OpenClaw durable knowledge base. Previous sessions successfully authenticated to the BookStack API and created or updated books, chapters, pages, infrastructure documentation, and diagrams.

Confirmed historical operation

  • BookStack host: https://book.stargrid.com.au
  • A read-only API test previously succeeded and returned the AI and OpenClaw books.
  • The OClaw book was created as the durable OpenClaw knowledge base.
  • The Chris's IT Infrastructure book was created and populated from read-only UniFi inventory.
  • Infrastructure pages include network overview, gateway/switch/access point inventory, camera inventory, connected clients, firewall/access policy summary, VLAN/wireless inventory, and a topology diagram.
  • Later sessions continued writing documentation and diagrams to BookStack.

What went wrong

The local workspace skill remained present at workspace/skills/bookstack/SKILL.md, but its configuration had drifted:

  1. skills.entries.bookstack.enabled was set to false, so OpenClaw marked the skill disabled.
  2. The stored BookStack credentials were still present in OpenClaw's protected secret store, but the skill readiness check could not see them as injected environment variables.
  3. The skill was therefore reported as disabled or needing setup even though the BookStack service and credentials had previously worked.

The exact session that changed those settings was not identified. The most likely cause is configuration drift during the recent model/session/plugin cleanup.

Repair status

  • The BookStack skill has been re-enabled with skills.entries.bookstack.enabled: true.
  • The three stored credential names remain present: BOOKSTACK_URL, BOOKSTACK_TOKEN_ID, and BOOKSTACK_TOKEN_SECRET.
  • Credential values and token secrets are intentionally not recorded in this page.
  • The current skill checker still reports the environment requirements as unresolved because the per-skill environment injection mapping is not currently restored.
  • Do not re-enter or publish the token secret in BookStack, chat, scripts, or committed configuration.

Operational lesson

A successful BookStack API connection and OpenClaw skill readiness are separate checks. The API credentials can remain healthy while the skill is disabled or its environment injection is missing. When this happens, verify both:

  • BookStack API connectivity using the gateway-managed secret environment.
  • skills.entries.bookstack.enabled and the skill's environment injection/readiness configuration.

Follow-up

Restore the supported secret-to-environment injection path for the workspace BookStack skill, then run a read-only list_books test and confirm that openclaw skills info bookstack reports ready.

No comments to display

Back to top