Name: timekit
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

timekit

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/timekit/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 commands and a well-sequenced connection state machine, and it is reasonably well-structured. Its main weaknesses are mild redundancy in the action-discovery sections and a broken 'Step 2' cross-reference that slightly fragments the workflow.

Suggestions

De-duplicate the action-discovery instructions: keep one canonical `membrane action list --intent=QUERY` example and remove the redundant 'Popular actions' section.

Fix the 'Step 2' cross-reference by labeling the downstream section (e.g. '## Step 2 — Searching for actions') so the connection flow reads as one numbered sequence.

Trim the introductory Timekit background paragraph to the one fact Claude cannot infer (it is a scheduling/booking platform) to reclaim tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and lean, but it repeats the action-discovery command in both 'Searching for actions' and 'Popular actions', and the overview CRUD tree plus intro paragraph add mild padding; this fits 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4 due to the noticeable duplication.	3 / 5
Actionability	It provides copy-paste-ready commands throughout — install, login (incl. headless completion), connection ensure, polling, action list/run, request proxy — plus a full flag table, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection workflow is a clear state machine with validation checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-and-retry feedback loop, but it references an unlabeled 'Step 2' and the overall flow is not a clean numbered sequence, leaving it just below the 5 anchor.	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers in a single file with no bundle files present and only an external docs link, giving good structure and easy navigation; it does not reach 5 because the 'Popular actions' section overlaps with the overview and no deeper reference material is signaled despite the breadth of the API.	4 / 5
	Total	16 / 20 Passed

Description

57%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 third-person and provides an explicit 'Use when' trigger tied to a distinct product niche, but its capability language is generic and lacks concrete Timekit operations. Strengthening the action list and trigger synonyms would lift it toward the top anchors.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Timekit actions such as 'create and manage bookings, availability, events, projects, and services'.

Add natural trigger synonyms users would actually say, e.g. 'Use when the user wants to book appointments, check availability, or manage Timekit scheduling data'.

Tighten the 'when' clause with specific triggers (booking, scheduling, appointments) rather than the generic 'interact with Timekit data'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Timekit) but its actions are generic — 'Manage data, records, and automate workflows' are abstract verbs with no concrete operations, matching the 'Names the domain but actions are minimal or generic' anchor; it does not reach 3 because no genuinely concrete action (e.g. create booking, list availability) is stated.	2 / 5
Completeness	Both halves are present — 'what' via 'Manage data, records, and automate workflows' and 'when' via the explicit 'Use when the user wants to interact with Timekit data' clause; it stays at 4 rather than 5 because the 'when' is generic and lacks concrete trigger phrases, and the 'what' is vague.	4 / 5
Trigger Term Quality	'interact with Timekit data' supplies the relevant keyword 'Timekit' but lacks natural synonyms or variations a user might say (e.g. booking, scheduling, appointments), fitting 'Some relevant keywords but missing common variations'; it is above 2 because 'Timekit' is a specific natural term, not generic jargon.	3 / 5
Distinctiveness Conflict Risk	The Timekit niche and its named trigger are clearly distinct from other skills with only minor overlap risk; it does not reach 5 because the surrounding action language ('manage data, records') is broad enough to blur the niche.	4 / 5
	Total	13 / 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/timekit/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.