Wiki.js

What This Skill Does

The Wiki.js skill for OpenClaw provides an automated interface to deploy, configure, and manage Wiki.js instances. It acts as an expert assistant that navigates the common pitfalls of Wiki.js setups, ensuring your documentation infrastructure is performant, secure, and maintainable from the outset. Whether you are setting up a personal knowledge base or a multi-user corporate technical reference, this skill automates the complex configuration steps that often lead to broken links or performance degradation.

Installation

To integrate this skill into your environment, use the OpenClaw command-line interface: clawhub install openclaw/skills/skills/ivangdavila/wiki-js Ensure you have the necessary credentials for your infrastructure provider before execution.

Use Cases

• Rapid deployment of Wiki.js instances with PostgreSQL backends for high-concurrency environments.
• Configuring granular permission structures to prevent accidental lockouts or security vulnerabilities.
• Managing Git synchronization settings for documentation version control.
• Troubleshooting common post-deployment issues like redirect loops, broken asset paths, and search indexing delays.
• Migrating content while adhering to strict URL and path formatting guidelines.

Example Prompts

1. "Deploy a new Wiki.js instance using PostgreSQL for a team of 50 users and ensure HTTPS is handled at the reverse proxy level."
2. "Analyze my current Wiki.js permissions and identify any overlapping patterns that might be causing user lockouts in the /engineering path."
3. "Troubleshoot my Wiki.js instance; I'm experiencing constant redirect loops after moving the site to a new domain."

Tips & Limitations

Success with Wiki.js requires attention to detail during the initial installation. The most critical constraint is the Site URL, which cannot be easily changed once set; verify your DNS and reverse proxy settings before initialization. When managing content, always prefer the Markdown editor over the Visual Editor to avoid irreversible formatting loss. Be aware that the Default 'Users' group permissions are global; configure these before inviting team members to avoid unintended access. For storage, leverage S3 or GCS for assets to keep database backups lean. Finally, remember that search results honor permission constraints, so users may report 'missing' pages that are simply restricted by your access controls. Always check Admin > Utilities if the wiki feels sluggish after large data imports, as the system may be busy reindexing.