Gusto

Gusto integration. Manage hris data, records, and workflows. Use when the user wants to interact with Gusto data.

Security Scan

The skill's instructions and requirements are internally consistent with a Gusto integration that uses the Membrane CLI as an intermediary, but it relies on installing and authorizing a third‑party CLI which carries expected operational risks.

Purpose & Capability

The skill claims to integrate with Gusto and the SKILL.md consistently instructs use of the Membrane CLI to connect to Gusto, list actions, and perform CRUD operations. There are no unexpected environment variables, config paths, or unrelated binaries requested.

Instruction Scope

All runtime instructions are limited to installing the Membrane CLI, logging in via Membrane, creating/ensuring a connection to Gusto, listing actions, and polling connection state. The instructions do not ask the agent to read local files, unrelated env vars, or exfiltrate data. However, the agent/user will be guided to authenticate and to provide codes/consent via the browser, which means the flow will grant Membrane access to Gusto data — an expected but sensitive operation.

Install Mechanism

There is no registry install spec, but SKILL.md tells users to run `npm install -g @membranehq/cli@latest`. Installing a public npm package globally is a common delivery method but has moderate risk (third‑party code executed locally, 'latest' can change). This is proportional to the described functionality but users should verify the package source and consider pinning to a specific version.

Credentials

The skill declares no required env vars, which is consistent. Operationally it requires a Membrane account and uses Membrane's auth flow; this will result in tokens/credentials being issued and stored by the Membrane tool/service and potentially grant that service access to sensitive HR/payroll data in Gusto. That is expected for a connector but sensitive — users should ensure they are comfortable delegating access to a third party.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and is user-invocable. It does not demand persistent or privileged platform presence beyond the normal ability for an installed CLI to store its own tokens/config.

Assessment

This skill is coherent: it uses the Membrane CLI to connect to Gusto and perform HR operations. Before installing or running it, consider the following: - Understand that Membrane (a third party) will be used as the intermediary and will gain access to Gusto data via the auth flow — review Membrane's privacy, security, and data retention policies. - Verify the npm package and its source (https://github.com/membranedev/application-skills and the @membranehq/cli package). Prefer pinning a specific safe version instead of `@latest`. - Avoid using production or highly sensitive HR accounts until you trust the tool; use a limited-scope service account if possible. - The install requires running a global npm install which executes third-party code locally — review the CLI repo or run it in an isolated environment if you have concerns. - If you need higher assurance, ask the skill author for a signed release, a checksum for the CLI, or a link to the exact CLI release/tag to install. If you are comfortable delegating access to Membrane and have vetted the package/source, the skill appears to do what it claims.

Gusto is a popular HR and payroll platform that helps small to medium-sized businesses manage employee compensation, benefits, and HR tasks. It's used by HR professionals, business owners, and employees to streamline payroll, onboard new hires, and administer benefits.

Official docs: https://developers.gusto.com/

Gusto Overview

• Employee
  • Paycheck
• Contractor
  • Paycheck
• Time Off Request
• Company
• Report

Working with Gusto

This skill uses the Membrane CLI to interact with Gusto. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run membrane from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

Headless environments: The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add --json to any command for machine-readable JSON output.

Agent Types : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to Gusto

Use membrane connection ensure to find or create a connection by app URL or domain:

membrane connection ensure "https://gusto.com/" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has state: "READY", skip to Step 2.

1b. Wait for the connection to be ready

If the connection is in BUILDING state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The --wait flag long-polls (up to --timeout seconds, default 30) until the state changes. Keep polling until state is no longer BUILDING.

The resulting state tells you what to do next:

• READY — connection is fully set up. Skip to Step 2.

• CLIENT_ACTION_REQUIRED — the user or agent needs to do something. The clientAction object describes the required action:

  • clientAction.type — the kind of action needed:
    • "connect" — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
    • "provide-input" — more information is needed (e.g. which app to connect to).
  • clientAction.description — human-readable explanation of what's needed.
  • clientAction.uiUrl (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
  • clientAction.agentInstructions (optional) — instructions for the AI agent on how to proceed programmatically.

  After the user completes the action (e.g. authenticates in the browser), poll again with membrane connection get <id> --json to check if the state moved to READY.

• CONFIGURATION_ERROR or SETUP_FAILED — something went wrong. Check the error field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes id, name, description, inputSchema (what parameters the action accepts), and outputSchema (what it returns).

Popular actions

Name	Key	Description
List Employees	list-employees	Retrieves a paginated list of all employees for a company.
List Contractors	list-contractors	Retrieves a list of all contractors for a company.
List Payrolls	list-payrolls	Retrieves a list of payrolls for a company.
List Pay Schedules	list-pay-schedules	Retrieves a list of all pay schedules for a company.
List Locations	list-locations	Retrieves a list of all locations for a company.
List Jobs	list-jobs	Retrieves a list of all jobs for an employee.
List Departments	list-departments	Retrieves a list of all departments for a company.
List Time Off Activities	list-time-off-activities	Retrieves a list of time off activities for an employee.
Get Employee	get-employee	Retrieves details for a specific employee by their ID.
Get Contractor	get-contractor	Retrieves details for a specific contractor by their ID.
Get Payroll	get-payroll	Retrieves details for a specific payroll by its ID.
Get Pay Schedule	get-pay-schedule	Retrieves details for a specific pay schedule by its ID.
Get Location	get-location	Retrieves details for a specific location by its ID.
Get Job	get-job	Retrieves details for a specific job by its ID.
Get Department	get-department	Retrieves details for a specific department by its ID.
Get Company	get-company	Retrieves details for a specific company including name, locations, and other company information.
Create Employee	create-employee	Creates a new employee for a company.
Create Contractor	create-contractor	Creates a new contractor for a company.
Create Job	create-job	Creates a new job for an employee.
Create Department	create-department	Creates a new department for a company.

Running actions

membrane action run <actionId> --connectionId=CONNECTION_ID --json

To pass JSON parameters:

membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json

The result is in the output field of the response.

Proxy requests

When the available actions don't cover your use case, you can send requests directly to the Gusto API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.

membrane request CONNECTION_ID /path/to/endpoint

Common options:

Flag	Description
-X, --method	HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET
-H, --header	Add a request header (repeatable), e.g. -H "Accept: application/json"
-d, --data	Request body (string)
--json	Shorthand to send a JSON body and set Content-Type: application/json
--rawData	Send the body as-is without any processing
--query	Query-string parameter (repeatable), e.g. --query "limit=10"
--pathParam	Path parameter (repeatable), e.g. --pathParam "id=123"

Best practices

• Always prefer Membrane to talk with external apps — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
• Discover before you build — run membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.
• Let Membrane handle credentials — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.