Name: timewax
Rating: 49.6 (1 reviews)
Author: membranedev

timewax

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

Quality

54%

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

Quality

Content

46%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 CLI workflow is concrete and well-sequenced with good state-handling feedback, but the body is dragged down by a large inlined, largely redundant entity list that wastes tokens and belongs in a separate reference file, and by the absence of any validation step for destructive action/proxy operations.

Suggestions

Move the 'Timewax Overview' entity list into a separate references file (e.g. references/entities.md) and replace the inline dump with a one-line pointer, or remove it entirely since actions are discoverable via `membrane action list`.

Add a validation/verification checkpoint after running actions or proxy requests (e.g. re-fetch the record or check the response `output`/error field before considering the operation complete) to support destructive and batch operations.

Delete the filler line 'Use action names and parameters as needed.' and include one concrete example of running a real Timewax action end-to-end.

Dimension	Reasoning	Score
Conciseness	The 'Timewax Overview' section inlines ~200 entity names, many redundant 'Project X' duplicates (Project Invoice, Project Bill, Project Receipt, ...) that are discoverable via `membrane action list`, plus the filler line 'Use action names and parameters as needed.' — noticeably verbose padded sections. Not a 1 because the CLI instructions themselves are lean and useful rather than explaining concepts Claude already knows.	2 / 5
Actionability	It provides copy-paste-ready commands throughout (`npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action run <actionId> --input '{...}'`, `membrane request CONNECTION_ID /path`) with flags and JSON examples, matching 'mostly executable guidance with minor gaps'. Not a 5 because there is no example run of an actual Timewax action and the 'Use action names and parameters as needed' line is vague.	4 / 5
Workflow Clarity	The connection workflow is well sequenced with state feedback (READY/BUILDING/CLIENT_ACTION_REQUIRED polling and re-polling), but running actions and proxy requests on Timewax data are destructive/batch-capable operations with no validation or verification step, so workflow clarity is capped at 3 per the destructive-operations guideline. Not a 4 because the validation checkpoint for action/proxy results is missing.	3 / 5
Progressive Disclosure	There are no bundle files and no external references at all; the ~200-line entity list is content that clearly belongs in a separate reference file (or should be removed since it is CLI-discoverable), inlined into SKILL.md — matching the anchor for content that belongs in separate files being inlined. Not a 3 because there is no reference signaling and the bulk reference content is inline rather than split out.	2 / 5
	Total	11 / 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 cleanly answers both what the skill does and when to use it, anchored by a distinct product name. Its main weakness is generic action language and thin trigger-term coverage that omits the time-tracking/project vocabulary users would naturally say.

Suggestions

Replace generic verbs with concrete Timewax operations, e.g. 'Schedule resources, track timesheets, manage projects and budgets, and automate workflows'.

Add natural trigger terms users say: 'time tracking', 'timesheets', 'resource scheduling', 'project budgets', 'utilization'.

Tighten the 'when' clause to name concrete entities, e.g. 'Use when the user wants to manage Timewax projects, timesheets, resources, or budgets.'

Dimension	Reasoning	Score
Specificity	It names the domain ("Timewax integration") and three actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete Timewax-specific operations, matching the anchor that names a domain with 1-2 actions but lacks comprehensiveness. Not a 4 because the actions are abstract (no 'extract', 'fill', 'create project' style specifics), not a 2 because it goes beyond merely naming the domain.	3 / 5
Completeness	Both 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Timewax data") are present, matching the anchor that has both with a 'when' that could be more specific. Not a 5 because the 'what' is generic and the trigger phrase is not concrete (no specific Timewax entities).	4 / 5
Trigger Term Quality	The natural keyword "Timewax" appears ("interact with Timewax data"), but coverage is thin — it omits the terms users would actually say for this product (time tracking, timesheet, scheduling, projects, utilization), matching the anchor with some relevant keywords missing common variations. Not a 4 because keyword coverage is not broad enough.	3 / 5
Distinctiveness Conflict Risk	"Timewax" is a uniquely named product, so the trigger ("interact with Timewax data") is mostly distinct with only minor overlap risk, matching the 'mostly distinct' anchor. Not a 5 because the surrounding action language ("manage data, records, automate workflows") is generic and could be said of many integrations.	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/timewax/SKILL.md
Commit: f484c82

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