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

tmetric

TMetric integration. Manage data, records, and automate workflows. Use when the user wants to interact with TMetric 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/tmetric/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 an efficient, actionable CLI integration guide with a well-sequenced connection workflow and clear sections. Its main weaknesses are the misleadingly empty "Popular actions" heading and a couple of minor structural/numbering inconsistencies.

Suggestions

Either populate "Popular actions" with a few concrete example TMetric actions (e.g. list time entries, create a project) or rename the section to reflect that it only points to discovery.

Fix the step cross-references: label "Step 1a"/"Step 2" consistently so "Skip to Step 2" resolves to a real heading.

Trim the one-line "TMetric is a work time tracking app..." intro or move it to the overview, since Claude can treat the rest as the operative guidance.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and command-focused with only minor over-explanation (e.g. the opening "TMetric is a work time tracking app..." line and a few explanatory sentences about URL normalization), fitting the efficient-with-minor-trim anchor.	4 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands for install, login, connection, action list/run, and proxy with a flags table, but placeholders (CONNECTION_ID, QUERY, <actionId>) and the thin "Popular actions" section leave minor gaps.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED, check error on CONFIGURATION_ERROR/SETUP_FAILED) and a retry loop after user action, but the "Skip to Step 2" reference points to an unlabeled step and the 1b numbering is slightly inconsistent.	4 / 5
Progressive Disclosure	The single self-contained file is well-organized into clearly headed sections (Overview, Working with TMetric, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with easy navigation; no bundle files exist so all content is appropriately inline, with only minor organization gaps like the empty "Popular actions" section.	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 has an explicit Use-when trigger and a distinct TMetric niche, but its action language is generic and keyword coverage is thin. Tightening the verbs and adding concrete trigger variations would lift it.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete TMetric actions such as "track time, manage projects, tasks, clients, and pull reports".

Expand trigger terms with natural variations users say, e.g. "time tracking, timesheets, TMetric time entries, or TMetric reports".

Make the when-clause more specific than "interact with TMetric data" — tie it to the concrete tasks users request.

Dimension	Reasoning	Score
Specificity	It names the domain ("TMetric integration") but the listed actions "Manage data, records, and automate workflows" are generic and minimal rather than concrete, matching the anchor where the domain is named but actions are minimal/generic.	2 / 5
Completeness	It states both a "what" (TMetric integration, manage data/records/automate workflows) and an explicit "when" ("Use when the user wants to interact with TMetric data"), but the trigger could be more specific, matching the anchor that has both with room for sharper when-guidance.	4 / 5
Trigger Term Quality	The description relies on the single natural keyword "TMetric" (and "interact with TMetric data") but is missing common variations or synonyms, fitting the anchor with some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	TMetric is a specific named app giving it a clear niche with minimal conflict risk, but the generic action phrasing ("Manage data, records, and automate workflows") leaves minor overlap with other productivity/time-tracking skills.	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/tmetric/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.