Name: hub-planner
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

hub-planner

HUB Planner integration. Manage Organizations. Use when the user wants to interact with HUB Planner 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/hub-planner/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 body is highly actionable with executable Membrane CLI commands and a well-structured connection workflow that includes state-based validation and a retry loop. It loses points mainly on a padded product-introduction paragraph and minor missing verification steps on mutating actions.

Suggestions

Trim the opening overview paragraph that explains what HUB Planner is — Claude does not need a product description, and the entity list already implies the domain.

Add an explicit verify/re-fetch step after create/update examples (e.g. re-run get-<entity> to confirm the change applied) to strengthen the workflow's feedback loops.

Consider moving the Popular-actions table into a references file and linking to it from the body, keeping SKILL.md as a lean overview with one-level-deep references.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but the opening paragraph ("HUB Planner is a resource scheduling and project planning software...") over-explains what the product is, and a few prose passages restate what the flags already convey.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request proxy) plus a flags table and a worked --input JSON example covering the common cases.	5 / 5
Workflow Clarity	The connection flow is a clear sequenced workflow with state-based checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop after the user acts; minor gaps are that some create/update examples lack an explicit verify step.	4 / 5
Progressive Disclosure	Single well-sectioned SKILL.md with clear headers and no bundle files; the inline Popular-actions table is compact enough to stay inline, though it is borderline reference material that could be split out.	4 / 5
	Total	16 / 20 Passed

Description

62%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 specific to a named product and answers both what and when, with an explicit Use-when clause. Its main weakness is thin action coverage (only "Manage Organizations") and generic trigger phrasing that omits the richer entity vocabulary the skill actually supports.

Suggestions

Replace or expand "Manage Organizations" with the broader action set the skill supports, e.g. "Manage bookings, projects, resources, timesheets, and clients in HUB Planner".

Make the Use-when clause more concrete by listing natural trigger terms users would say, e.g. "Use when the user wants to schedule resources, create bookings, track time, or manage projects in HUB Planner".

Dimension	Reasoning	Score
Specificity	Names the domain ("HUB Planner integration") plus one concrete action ("Manage Organizations"), but coverage is not comprehensive — only Organizations is named while the body covers many more entities.	3 / 5
Completeness	States a clear "what" ("Manage Organizations") and an explicit "when" ("Use when the user wants to interact with HUB Planner data"), though the trigger clause is fairly generic.	4 / 5
Trigger Term Quality	Includes the natural product name "HUB Planner" and the phrase "interact with HUB Planner data", but misses common variations or synonyms a user might say (e.g. bookings, scheduling, resources, timesheets).	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "HUB Planner" gives it a clear niche with minimal overlap risk against other skills; only minor overlap risk with sibling Membrane app skills.	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: membranedev/application-skills
Path: skills/hub-planner/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.