breezy-hr-automation

Overview of breezy-hr-automation skill

What breezy-hr-automation does

breezy-hr-automation is a Claude skill for running Breezy HR recruiting operations through Composio’s Rube MCP server. Instead of hard-coding Breezy HR API calls, the skill tells the agent to discover the current Breezy HR tools with RUBE_SEARCH_TOOLS, verify the account connection, and then execute the selected workflow with the returned schema.

This matters because MCP tool names, required fields, and execution plans can change. The skill’s main value is not a long library of fixed commands; it is a safer operating pattern for Breezy HR automation where discovery happens before action.

Best fit for Recruiting teams and operators

The breezy-hr-automation skill is best for recruiters, recruiting coordinators, talent operations teams, and founders who already use Breezy HR and want an AI assistant to help with structured tasks such as looking up candidates, coordinating pipeline updates, retrieving job or applicant data, or preparing repeatable recruiting workflows.

It is most useful when you can describe the recruiting task clearly and have permission to connect the relevant Breezy HR workspace through Rube MCP.

What makes this skill different from a generic prompt

A normal prompt can describe a Breezy HR task, but it will not automatically know which live MCP tools are available or what fields they require. This skill adds a tool-first workflow: search available Breezy HR operations, check the connection, inspect schemas, and only then act.

That makes it better for operational recruiting work where stale assumptions can cause failed calls, missing fields, or accidental updates.

Adoption requirements and constraints

Before installing, confirm that your AI client supports MCP and can add https://rube.app/mcp as a server. You also need an active Breezy HR connection through RUBE_MANAGE_CONNECTIONS using the breezy_hr toolkit.

The repository for this skill is intentionally compact: the primary file is SKILL.md, with no bundled scripts or reference folders. Treat it as an execution protocol, not a full recruiting automation application.

How to Use breezy-hr-automation skill

breezy-hr-automation install and setup path

Install the skill from the Composio skills repository:

npx skills add ComposioHQ/awesome-claude-skills --skill breezy-hr-automation

Then configure Rube MCP in your client by adding:

https://rube.app/mcp

After MCP is available, verify that RUBE_SEARCH_TOOLS responds. Next, use RUBE_MANAGE_CONNECTIONS or the available Rube connection-management tool to connect the breezy_hr toolkit. Do not ask the agent to run Breezy HR actions until the connection status is ACTIVE.

Start every workflow with tool discovery

The most important usage rule is to search tools first. A good first call is framed around the exact recruiting operation:

RUBE_SEARCH_TOOLS with a use case such as "Find candidates in Breezy HR for a specific job and summarize their current pipeline stage"

The returned result should guide the rest of the workflow: available tool slugs, input schema, required IDs, recommended plan, and pitfalls. This is the step that prevents the agent from guessing field names or using outdated tool assumptions.

Turn a rough goal into a complete prompt

Weak prompt:

“Update Breezy HR candidates.”

Stronger prompt:

“Use the breezy-hr-automation skill. First search Rube tools for the current Breezy HR schema. Confirm the Breezy HR connection is active. Then find candidates for the Customer Support Specialist role, identify candidates in the Phone Screen stage, and prepare a proposed stage-update plan. Do not make changes until I approve the candidate list and target stage.”

This gives the agent the task, required safety gate, target object, selection rule, and approval boundary. For recruiting work, include job title or ID, candidate identifiers, desired action, whether updates are allowed, and what confirmation you want before write operations.

Files to read before relying on the skill

Read composio-skills/breezy-hr-automation/SKILL.md first. It contains the core prerequisites, setup flow, discovery call pattern, and execution expectation.

There are no extra scripts/, references/, resources/, or README.md files in the current skill folder, so do not expect prebuilt candidate-processing logic. The practical behavior comes from combining the skill instructions with live Rube MCP tool discovery.

breezy-hr-automation skill FAQ

Is breezy-hr-automation only for recruiters?

It is designed for Recruiting workflows, but the user can be anyone responsible for Breezy HR operations: talent ops, HR admins, hiring managers, agency recruiters, or startup operators. The key requirement is access to the Breezy HR workspace and enough context to specify the task safely.

Can it automate updates in Breezy HR?

Yes, if the Rube Breezy HR toolkit exposes the needed action and the connection has permission. However, you should separate read, plan, and write steps. For updates to candidates, jobs, notes, or pipeline stages, ask the agent to produce a preview and wait for approval before executing changes.

Why does the skill require searching tools first?

The skill depends on live MCP tool schemas rather than fixed commands. RUBE_SEARCH_TOOLS tells the agent what Breezy HR operations are currently available and how to call them. Skipping discovery increases the chance of failed execution, missing required fields, or incorrect assumptions about the toolkit.

When should I not use this skill?

Do not use breezy-hr-automation for unsupported Breezy HR actions, unclear bulk updates, sensitive hiring decisions without human review, or workflows where you cannot verify candidate identity and intended action. It is also a poor fit if your client cannot use MCP or your Breezy HR connection cannot be made active.

How to Improve breezy-hr-automation skill

Improve breezy-hr-automation inputs

Better inputs produce safer recruiting output. Provide role names or IDs, candidate names or IDs, pipeline stages, date ranges, desired output format, and whether the agent may write back to Breezy HR.

For example, “summarize candidates added this week for Job X, grouped by stage, with no updates” is much safer than “check applicants.” If you need changes, state the confirmation policy: “draft the changes first; execute only after approval.”

Avoid common failure modes

The most common failure is asking for an action before the agent has discovered tools and checked the connection. Another is mixing too many goals into one request, such as finding candidates, changing stages, creating notes, and sending follow-ups in a single unsupervised step.

Break the workflow into: discover tools, verify connection, retrieve data, review plan, then execute approved action.

Iterate after the first result

After the first output, ask the agent to show which tool schema it used, which required fields were supplied, and which assumptions remain. For candidate or job workflows, verify names, IDs, and stage labels before approving changes.

If the result is too broad, narrow by job, department, location, status, date, or pipeline stage. If it is too shallow, ask for a second pass using additional Breezy HR fields exposed by the discovered schema.

Extend the skill responsibly

If your team repeatedly runs the same recruiting workflow, consider adding local prompt examples or internal operating rules around approvals, audit notes, and bulk-update limits. Keep the original breezy-hr-automation pattern intact: discover current tools first, check the Breezy HR connection, then execute only with clear inputs and review boundaries.