Name: timebuzzer
Rating: 60.8 (1 reviews)
Author: membranedev

timebuzzer

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

Quality

71%

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

Quality

Content

82%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 a tight, highly actionable Membrane CLI integration guide with strong command coverage and a well-validated connection workflow. Its only weaknesses are minor over-explanation up front and a lack of result-validation guidance in the action and proxy sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples with minimal prose, but the opening app description ('TimeBuzzer is a time tracking application used by freelancers and teams...') and a few explanatory asides ('so you can focus on the integration logic rather than auth plumbing') are mild over-explanation that could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides copy-paste-ready, executable commands for every stage — 'npm install -g @membranehq/cli@latest', 'membrane connection ensure', 'membrane action list ... --intent', 'membrane action run', and 'membrane request' — covering the common cases fully.	5 / 5
Workflow Clarity	The connect flow has explicit validation and a feedback loop (polling BUILDING state, branching on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the action-running and proxy sections only note 'the result is in the output field' with no result-validation checkpoint, leaving minor validation gaps.	4 / 5
Progressive Disclosure	The body is well-sectioned (install, auth, connect, search, run, proxy, best practices) with no external bundle files needed for this CLI-based skill; it stays just over the simple-skill threshold with the proxy-flags table and clientAction details inlined, so it is well-organized with minor placement gaps rather than ideal separation.	4 / 5
	Total	17 / 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 answers both what and when and is clearly scoped to TimeBuzzer, but its action verbs are generic and it lacks the natural trigger synonyms a user would actually say. It is solid but not exemplary.

Suggestions

Replace the generic verbs ('Manage data, records, and automate workflows') with concrete TimeBuzzer actions such as 'start and stop timers, log hours to projects and tasks, and generate time reports'.

Add natural trigger phrases users actually say — e.g. 'time tracking', 'timesheets', 'log hours', or 'time tracker' — rather than relying solely on the app name 'TimeBuzzer data'.

Dimension	Reasoning	Score
Specificity	It names the TimeBuzzer domain plus three actions ('Manage data, records, and automate workflows'), but those verbs are generic rather than concrete operations; this fits the anchor 'Names the domain but actions are minimal or generic' better than the '1-2 concrete actions' anchor above.	2 / 5
Completeness	Both halves are present — a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with TimeBuzzer data'), but the 'what' is generic so it does not reach the concrete-trigger-phrase level of the score-5 anchor.	4 / 5
Trigger Term Quality	The only natural keyword is the app name 'TimeBuzzer' (in 'interact with TimeBuzzer data'); common user phrases like 'time tracking', 'timesheets', or 'log hours' are missing, matching the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming a specific commercial app ('TimeBuzzer integration' / 'interact with TimeBuzzer data') gives it a clear niche with distinct triggers and minimal conflict risk against other skills.	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/timebuzzer/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.