Name: bamboohr
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bamboohr

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

Quality

72%

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 ./skills/bamboohr/SKILL.md

Quality

Content

71%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 content is highly actionable with executable Membrane CLI commands and a solid connection workflow including validation feedback loops. Its weaknesses are token bloat from the HRIS intro and entity list, inconsistent step numbering, and lack of file-based progressive disclosure.

Suggestions

Remove the "BambooHR is an HRIS platform..." intro paragraph and trim the 60-item entity list to the handful of resources users actually act on, moving the full list to a references file.

Fix the step numbering in the connection flow (label Step 1 and Step 2 explicitly instead of jumping to "1b" and referencing an unlabeled "Step 2").

Add a short validation/example for the `membrane action run` output so Claude knows how to interpret the `output` field end-to-end.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it pads tokens with an unnecessary "BambooHR is an HRIS platform..." intro and a ~60-item entity list that adds little actionable value, matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) with concrete flags, JSON examples, and a table of real action keys, fully covering the common cases.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit validation checkpoints (poll until not BUILDING, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), but step numbering is inconsistent ("1b", dangling "Step 2" references), leaving minor gaps.	4 / 5
Progressive Disclosure	Section structure is present and an external docs link is given, but with no bundle files the ~60-item inline entity list is content that should be separated or trimmed, fitting the some-structure-but-inline-bloat anchor.	3 / 5
	Total	15 / 20 Passed

Description

73%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 cleanly answers both what the skill does and when to use it, anchored on the distinctive BambooHR proper noun. Its main weakness is generic verb choice ("manage") and a thin, non-specific trigger clause.

Suggestions

Replace the generic verb "Manage" with 2-3 concrete actions (e.g., "list employees, create time-off requests, run custom reports").

Expand the "Use when" clause with concrete trigger phrases users would actually say (e.g., "when the user mentions BambooHR, employee records, time-off requests, or HRIS data").

Dimension	Reasoning	Score
Specificity	"Manage hris data, records, and workflows" names the BambooHR/HRIS domain and a few action areas, but the verb "manage" is generic rather than a concrete action, so it sits at the anchor listing 1-2 actions without being comprehensive.	3 / 5
Completeness	It states both a clear "what" ("BambooHR integration. Manage hris data, records, and workflows.") and a "when" ("Use when the user wants to interact with BambooHR data."), but the trigger clause is generic rather than listing concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	"BambooHR", "hris data", "records", "workflows", and "interact with BambooHR data" give good natural keyword coverage centered on the app name, though a few synonyms or related HR trigger phrases are missing.	4 / 5
Distinctiveness Conflict Risk	The distinct proper-noun trigger "BambooHR" carves a clear niche with minimal conflict risk against other skills, matching the clear-niche anchor.	5 / 5
	Total	16 / 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: membranedev/application-skills
Path: skills/bamboohr/SKILL.md
Commit: f484c82

Reviewed: ~1 hour 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.