bamboohr-automation

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

Install with Tessl CLI

npx tessl i github:Lingjie-chen/MT5 --skill bamboohr-automation

What are skills?

Review — 51%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

40%

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 clear domain (BambooHR via Rube MCP) and lists relevant capability areas, making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and the capabilities listed are categories rather than specific actions. The description would benefit from concrete action verbs and natural language triggers users would actually say.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about HR tasks, employee records, PTO requests, or mentions BambooHR'

Replace category nouns with specific action phrases: 'create/update employee records, submit/approve time-off requests, manage benefits enrollment, add dependents'

Include common user language variations: 'PTO', 'vacation', 'leave requests', 'HR system', 'employee directory'

Dimension	Reasoning	Score
Specificity	Names the domain (BambooHR) and lists several action areas (employees, time-off, benefits, dependents, employee updates), but these are categories rather than specific concrete actions like 'create employee records' or 'approve time-off requests'.	2 / 3
Completeness	Describes what it does (automate BambooHR tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The rubric states missing trigger guidance should cap completeness at 2, and this has no trigger guidance at all.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'BambooHR', 'employees', 'time-off', 'benefits', but missing common variations users might say such as 'HR system', 'PTO', 'vacation requests', 'employee directory', or 'leave management'.	2 / 3
Distinctiveness Conflict Risk	BambooHR is a specific product name, and the mention of 'Rube MCP (Composio)' creates a clear niche. This is unlikely to conflict with other skills due to the specific platform and integration mentioned.	3 / 3
	Total	8 / 12 Passed

Implementation

62%

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

This skill provides comprehensive coverage of BambooHR operations with well-structured workflows and clear sequencing. However, it lacks executable code examples (relying on pseudocode patterns instead) and could be more concise by removing redundant sections and trusting Claude's baseline knowledge. The quick reference table is a strong addition for rapid lookup.

Suggestions

Add at least one fully executable example showing an actual MCP tool call with concrete parameters and expected response structure

Remove the 'Common Patterns' section as it largely duplicates the Core Workflows content, or consolidate into a single presentation

Move detailed pitfalls and edge cases to a separate PITFALLS.md or REFERENCE.md file, keeping SKILL.md focused on core workflows

Remove explanations of basic concepts like PII handling and rate limiting that Claude already understands

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy - the 'Common Patterns' section repeats information already covered in Core Workflows, and some explanations (like what PII is or basic API concepts) assume less of Claude's intelligence than necessary.	2 / 3
Actionability	Provides tool names and parameter lists but lacks executable code examples. The patterns shown use pseudocode-style numbered steps rather than actual API call examples with concrete parameter values. No copy-paste ready examples with real data structures.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit prerequisite steps marked. The time-off workflow shows proper validation flow (check types -> check balance -> create -> approve). Tool sequences clearly indicate required vs optional steps.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections and a quick reference table, but the document is quite long (~200 lines) with no references to external files. Some detailed pitfalls and patterns could be split into separate reference documents for better navigation.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

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