Name: timely-time-tracking
Rating: 59.2 (1 reviews)
Author: membranedev

timely-time-tracking

Timely Time Tracking integration. Manage data, records, and automate workflows. Use when the user wants to interact with Timely Time Tracking 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/timely-time-tracking/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 a well-structured, mostly executable guide to driving Timely through the Membrane CLI, with a genuine validation loop around connection setup. It loses points only for minor over-explanation in the intro, slight step-numbering inconsistency, and light redundancy between the action-discovery sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven prose with executable blocks, but the opening paragraph explaining what Timely is ('automated time tracking software that eliminates manual timesheets...') and the aside about focusing on 'integration logic rather than auth plumbing' are minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for the common cases (install, login, connection ensure, action list/run, request proxy) with a clear options table, but placeholders like CONNECTION_ID and the thin 'Popular actions' section leave minor gaps before full coverage.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → wait-for-ready → search → run sequence with a real feedback loop (polling connection state and handling CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though the step numbering ('skip to Step 2' with no labeled Step 2, and a '1b' subsection) is slightly inconsistent.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized into clearly headed sections with no nested references and no bundle files to navigate; it stays one level deep, with only minor redundancy between 'Searching for actions' and 'Popular actions' keeping it from a 5.	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 functional and correctly pairs a 'what' with an explicit 'Use when' trigger tied to a specific named product, but its action verbs are generic and it lacks keyword variations. Tightening the actions to concrete capabilities and adding natural synonyms would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Log time entries, manage projects and clients, and pull reports' instead of 'Manage data, records, and automate workflows'.

Add natural trigger synonyms users would say, such as 'time entries', 'timesheets', 'hours logged', or 'Timely reports'.

Make the 'when' clause more specific about scope, e.g. 'Use when the user wants to read or update Timely time entries, projects, or reports'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Timely Time Tracking integration') and lists several actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete, matching the anchor that names domain and actions without comprehensive coverage.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Timely Time Tracking data') are explicitly present, though the 'what' is somewhat vague, matching the anchor where both exist but could be more specific.	4 / 5
Trigger Term Quality	The product name 'Timely Time Tracking' is a relevant keyword and 'Use when the user wants to interact with Timely Time Tracking data' gives a trigger, but there are no common variations, synonyms, or file extensions, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the specific named product 'Timely Time Tracking' gives it a clear niche with minimal conflict risk, though the generic 'manage data, records, and automate workflows' wording leaves minor overlap with other integration 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/timely-time-tracking/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.