breezy-hr-automation

Automate Breezy HR tasks via Rube MCP (Composio). Always search tools first for current schemas.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/breezy-hr-automation/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, well-structured guide with concrete tool-call patterns and a sensible discover-connect-execute workflow, appropriately deferring exact schemas to runtime discovery. Its main weaknesses are repeated search-first guidance, a padded footer, and the absence of post-execution validation steps for batch HR operations.

Suggestions

State the search-first rule once (e.g., in Known Pitfalls) and remove the duplicates in Prerequisites and Tool Discovery.

Add a post-execution verification step to the Core Workflow, e.g., check the RUBE_MULTI_EXECUTE_TOOL response for errors and confirm the operation actually succeeded before proceeding, which would lift the workflow_clarity cap.

Remove the '*Powered by Composio*' footer line — it is advertising padding that adds no guidance.

Dimension	Reasoning	Score
Conciseness	The body is efficient and well-sectioned, but the search-first rule is stated three times (Prerequisites 'Always call RUBE_SEARCH_TOOLS first', Tool Discovery 'Always discover available tools', Pitfalls 'Always search first') and the 'Powered by Composio' footer is padding. Matches anchor 4 ('minor instances of over-explanation that could be trimmed'), not 5 due to this repetition.	4 / 5
Actionability	Every step has a concrete tool call with parameter structure (e.g., 'queries: [{use_case: ...}]', 'toolkits: ["breezy_hr"]'). Placeholders like TOOL_SLUG_FROM_SEARCH are justified by 'Tool schemas change. Never hardcode tool slugs', but no fully executable end-to-end example is given, keeping it at anchor 4.	4 / 5
Workflow Clarity	A clear 3-step sequence exists with a connection checkpoint ('If connection is not ACTIVE, follow the returned auth link'), but there is no post-execution validation of results. Since the skill drives batch/external-state operations via RUBE_MULTI_EXECUTE_TOOL and lists 'Bulk ops', the missing-validation cap of 3 applies — this takes precedence over the sequence's otherwise good structure.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are all absent) and none are needed: the ~85-line body is self-contained with clear sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Known Pitfalls, Quick Reference) and no buried or nested references. Matches the well-organized, self-contained top anchor.	5 / 5
	Total	16 / 20 Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names a clear, distinct niche (Breezy HR via Rube MCP) but is thin: it lists no concrete capabilities and omits any 'Use when...' trigger guidance. It reads more like a usage instruction ('Always search tools first') than a capability declaration.

Suggestions

List 2-3 concrete capabilities in the description, e.g., 'Create and manage candidates, job postings, and pipelines in Breezy HR'.

Add an explicit trigger clause, e.g., 'Use when the user mentions Breezy HR, recruiting tasks, candidates, or job postings'.

Drop the imperative 'Always search tools first for current schemas' from the description — it is workflow guidance, not capability or trigger information.

Dimension	Reasoning	Score
Specificity	"Automate Breezy HR tasks" names the domain but the action is generic — no concrete operations (e.g., create candidates, post jobs, manage pipelines) are listed. Matches anchor 2 ('Names the domain but actions are minimal or generic'); not 3 because no specific concrete actions are enumerated.	2 / 5
Completeness	The 'what' is stated (automate Breezy HR via Rube MCP) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Matches anchor 3 ('Has a clear what but when is missing').	3 / 5
Trigger Term Quality	"Breezy HR", "Rube MCP", and "Composio" are relevant keywords, but natural recruiting synonyms users would say (candidates, hiring, job postings, recruiting) are missing. Matches anchor 3 ('Some relevant keywords but missing common variations or synonyms').	3 / 5
Distinctiveness Conflict Risk	Breezy HR is a specific product niche giving mostly distinct triggers, but the generic 'HR' scope and absence of a when-clause leave minor overlap risk with other HR/recruiting automation skills. Matches anchor 4, not 5 because triggers are not fully sharpened.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: ComposioHQ/awesome-claude-skills
Path: composio-skills/breezy-hr-automation/SKILL.md
Commit: be2a406

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.