Hub Planner
PassAudited by VirusTotal on May 11, 2026.
Overview
Type: OpenClaw Skill Name: hub-planner Version: 1.0.4 The hub-planner skill provides instructions for an AI agent to interact with the HUB Planner API using the Membrane CLI. It covers standard authentication, connection management, and execution of resource scheduling actions. The use of the '@membranehq/cli' and the Membrane proxy is transparently documented as a way to handle credentials securely, and no evidence of malicious intent, data exfiltration, or harmful prompt injection was found in SKILL.md or _meta.json.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A remote connection workflow could influence how the agent proceeds during setup.
The skill may consume provider-returned instructions for the agent during connection setup. That is useful integration plumbing, but those instructions should remain bounded to the current setup task and not override the user's request.
`clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.
Treat returned agent instructions as untrusted provider data; follow them only when they are clearly related to the user's current Hub Planner connection task.
If the agent selects or runs the wrong action, it could change Hub Planner clients, bookings, time entries, resources, or projects.
The skill delegates broad action selection and execution to Membrane and lists create/update operations for Hub Planner business data. The provided visible instructions do not add confirmation, scope, or rollback safeguards before mutations.
Search using a natural language description ... `membrane action list --connectionId=CONNECTION_ID --intent "QUERY"` ... `Create Booking` ... `Update Project`
Require explicit user confirmation before any create or update action, show the exact target object and fields, and prefer read/list actions unless the user clearly requested a change.
Installing and using the skill may grant the integration access to organization scheduling and project data in the connected account.
The skill requires delegated Membrane/HUB Planner account access and ongoing credential refresh. This is expected for the integration, but it is sensitive authority.
Membrane handles authentication and credentials refresh automatically ... `membrane login --tenant --clientName=<agentType>`
Authenticate only the intended account, use least-privilege access where possible, and know how to revoke the Membrane/HUB Planner connection.
The actual runtime behavior depends on the installed Membrane CLI version and remote connector generation, not just this SKILL.md file.
The setup depends on a globally installed moving npm package and potentially generated connector behavior outside the reviewed skill artifact. This is purpose-aligned but not fully captured by the local package contents.
`npm install -g @membranehq/cli@latest` ... `If no app is found, one is created and a connector is built automatically.`
Install the CLI from a trusted source, consider pinning a known version, and review Membrane connector details before granting production access.