bamboohr-automation

Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas.

1.27x

Quality

62%

Does it follow best practices?

Impact

79%

1.27x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/bamboohr-automation/SKILL.md

Quality

Content

63%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 delivers concrete, well-sequenced MCP guidance with real parameter detail and useful pitfall callouts, but it pays for that with significant duplication between workflow-level pitfalls, the 'Known Pitfalls' section, and the Quick Reference table. Consolidating the detail into a one-level-deep reference file would improve both conciseness and progressive disclosure.

Suggestions

Deduplicate the pitfalls: keep them once, either inline per workflow or in the 'Known Pitfalls' section, and cross-reference instead of repeating (employee IDs, date formats, permissions, and sensitive-data notes each currently appear twice).

Move the per-workflow detail (or at least the Quick Reference table) into a references/ file (e.g. TOOL_REFERENCE.md) and have SKILL.md link to it, making the overview one level deep.

Add explicit recovery loops for the destructive workflow, e.g. after BAMBOOHR_UPDATE_EMPLOYEE: re-fetch the employee, confirm the changed fields, and revert/patch if values differ from intended.

Dimension	Reasoning	Score
Conciseness	The per-workflow 'Pitfalls' blocks are substantially duplicated by the standalone 'Known Pitfalls' section (employee IDs, date formats, permissions, and PII each appear twice), and the Quick Reference table re-lists the same tools and parameters — accurate but noticeably redundant, matching anchor 3 rather than anchor 4's minor trims.	3 / 5
Actionability	Concrete tool slugs, exact parameter names, formats with worked examples ('2024-01-15T00:00:00Z', 'firstName,lastName,department,jobTitle'), and step-numbered ID-resolution patterns make the guidance mostly executable; it stays below anchor 5 only because no example request payloads or response shapes are shown.	4 / 5
Workflow Clarity	Tool sequences are ordered and labeled ([Prerequisite]/[Required]/[Optional]) with validation checkpoints ('Verify current values with GET_EMPLOYEE before updating to avoid overwriting', 'Confirm connection status shows ACTIVE before running any workflows'); destructive/batch operations do carry validation guidance, but explicit fix-and-retry recovery loops are absent, matching anchor 4.	4 / 5
Progressive Disclosure	Sections are well-organized with headers and a summary table, but this is a ~220-line single-file monolith whose per-workflow detail catalog and Quick Reference clearly belong in a separate reference file — no bundle files exist, matching anchor 3's 'content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

61%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 identifies a distinct, well-scoped niche (BambooHR via Rube MCP) and enumerates the data objects it covers, but it never says when the skill should be invoked and compresses all capability into a single generic verb. Adding an explicit 'Use when...' trigger clause and per-object actions would raise completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions BambooHR, employee directories, PTO/time-off requests, dependents, or benefit coverage.'

Replace the single generic verb 'Automate' with per-object actions, e.g. 'Look up employees, check time-off balances, submit and approve time-off requests, update employee fields, list dependents and benefit coverages.'

Include natural synonyms users say (PTO, leave, HR records) alongside the existing keywords to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('BambooHR') and a concrete list of objects ('employees, time-off, benefits, dependents, employee updates') but offers only one generic action verb ('Automate BambooHR tasks') — no distinct per-object actions, so it matches anchor 3 rather than anchor 4's several specific actions.	3 / 5
Completeness	The 'what' is clear (automating BambooHR operations across listed objects), but there is no 'Use when...' clause or equivalent trigger guidance — 'Always search tools first for current schemas' is behavioral instruction, not a when-to-use trigger, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('BambooHR', 'employees', 'time-off', 'benefits', 'dependents', 'employee updates') that users would plausibly say, but common synonyms and variations like 'PTO', 'leave', or 'HR' are missing, placing it just below anchor 5's comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	'BambooHR' plus the Rube MCP/Composio framing establishes a clear niche with minimal conflict risk, but generic triggers like 'employees', 'time-off', and 'employee updates' could overlap with other HR-related skills, matching anchor 4 rather than anchor 5.	4 / 5
	Total	14 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/bamboohr-automation/SKILL.md
Commit: c9856ea

Reviewed: 6 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.