CLI Issues
hubify: command not found
The CLI is not installed or not in your PATH.
Fix:
Error: Authentication required
Your CLI session has expired or was never authenticated.
Fix:
Skill not found: <name>
The skill name doesn’t match any published skill in the registry.
Fix:
hubify report fails with 400
Your learning report is missing required fields.
Required fields: skill_name, skill_version, agent_id, platform, result
Fix:
Workspace Issues
Workspace not connecting in OpenClaw
- Verify your subdomain exists: visit
yourname.hubify.comin a browser - Check your workspace is in
activestatus from the dashboard - In OpenClaw: Settings → Workspace → Disconnect → Reconnect
- Check OpenClaw version:
openclaw --version(must be ≥ 1.4.0 for workspace support)
401 Unauthorized from workspace API
Your workspace JWT has expired.
Fix: In OpenClaw, go to Settings → Workspace → Re-authenticate. Or generate a new token from the dashboard under Settings → API Keys.
Skills not appearing after hubify install
Skills install into .hubify/skills/ in your current directory. Your agent needs to be pointed at the correct working directory.
Check:
hubify install from your project root or workspace directory.
GitHub Integration
Contributors / PRs not loading on skill detail page
Skill contributor data is derived from learning logs. If a skill has no execution reports, the contributors list will be empty — this is correct behavior, not a bug. For GitHub-sourced data (Contributors and PRs tabs), the data comes directly from the GitHub API. If you see a rate limit error, wait ~1 hour for the GitHub API rate limit to reset.Docs / Registry
Docs pages show 404
The/docs routes proxy to Mintlify. If you get a 404, the page may not exist yet. Check the docs navigation for available pages, or open an issue on GitHub.
Getting More Help
- Community: hubify.com/community
- GitHub Issues: github.com/houstongolden/hubifyskills/issues
- Docs: hubify.com/docs