Name: hubstaff
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

hubstaff

Hubstaff integration. Manage Organizations. Use when the user wants to interact with Hubstaff data.

Quality

68%

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

Quality

Content

75%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 commands and a clear, state-driven connection workflow. Its main weakness is mild verbosity in the introductory prose and clientAction explanation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but it opens with product-explaining prose ('Hubstaff is a time tracking and workforce management software...') and a verbose clientAction state explanation that could be tightened.	3 / 5
Actionability	Copy-paste ready commands with explicit flags (e.g., 'membrane connection ensure "https://hubstaff.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --json') cover the common cases end to end.	5 / 5
Workflow Clarity	The connection flow has explicit state checkpoints (READY -> skip ahead, BUILDING -> poll with --wait, CLIENT_ACTION_REQUIRED -> act then re-poll, CONFIGURATION_ERROR -> inspect error), with only minor numbering/labeling gaps.	4 / 5
Progressive Disclosure	Sections are well organized and self-contained with no nested references, though the large inline popular-actions table could arguably live in a separate reference file.	4 / 5
	Total	16 / 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 is distinctive and answers both what and when, but it is thin on capabilities and trigger-term coverage. It leans almost entirely on the brand name rather than enumerating concrete actions or natural user phrases.

Suggestions

Expand 'Manage Organizations' to list the skill's main capabilities (e.g., time entries/timers, projects, screenshots, time off, clients, teams, tasks) so the description reflects actual coverage.

Add natural trigger phrases users would say, such as 'time tracking', 'timesheets', 'employee hours', or 'Hubstaff screenshots', instead of only 'interact with Hubstaff data'.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage Organizations' names the domain (Hubstaff) but offers only a single, generic action, even though the body reveals many more capabilities (time entries, projects, screenshots, time off, clients, teams, tasks).	2 / 5
Completeness	Both a 'what' ('Hubstaff integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Hubstaff data.') are present, though the 'when' could be more specific.	4 / 5
Trigger Term Quality	'interact with Hubstaff data' relies on the brand name alone and misses natural synonyms users would say such as 'time tracking', 'timesheets', or 'screenshots'.	3 / 5
Distinctiveness Conflict Risk	Hubstaff is a named product with a distinct trigger ('Hubstaff data'), giving it a clear niche and minimal risk of firing for the wrong skill.	5 / 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: membranedev/application-skills
Path: skills/hubstaff/SKILL.md
Commit: f484c82

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