Hubstaff

v1.0.2

Hubstaff integration. Manage Organizations. Use when the user wants to interact with Hubstaff data.

0· 98·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Hubstaff integration) match the SKILL.md instructions, which describe using the Membrane CLI to create connections, list actions, run actions, and proxy requests to the Hubstaff API. No unrelated credentials, binaries, or capabilities are requested.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, performing login via browser, managing Membrane connections, listing/running actions, and optionally proxying requests to Hubstaff via Membrane. The instructions do not ask the agent to read unrelated files, environment variables, or system configuration.
Install Mechanism
Install is instruction-only and recommends `npm install -g @membranehq/cli`. This is a standard npm global install (no arbitrary URL downloads). As with any globally installed package, users should verify the package name/owner and be comfortable granting a third-party CLI network and local execution privileges.
Credentials
The skill does not request environment variables, local credentials, or config paths. Authentication is delegated to Membrane through an interactive browser flow, which is coherent with the described design (Membrane handles credentials server-side).
Persistence & Privilege
Skill is not marked always:true and is user-invocable. It does not request to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges.
Assessment
This skill appears coherent: it uses the Membrane CLI to manage Hubstaff connections and actions and does not request extra local credentials. Before installing, confirm you trust the @membranehq package and the Membrane service (they will proxy and store Hubstaff auth on their side). Verify the npm package owner and the repository (https://github.com/membranedev/application-skills), review Membrane's privacy/terms, and ensure you are comfortable granting a third-party service access to your Hubstaff data. If you prefer not to use an external proxy, consider a direct Hubstaff integration that you control.

Like a lobster shell, security has layers — review code before you run it.

latestvk971nvm2rsdanc1waydse743js842xzt

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments