Name: wisetime
Rating: 55.2 (1 reviews)
Author: membranedev

wisetime

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

Quality

62%

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

Quality

Content

67%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 strong, command-driven integration guide with a clear connection workflow and state-handling feedback loop. Its main weaknesses are minor filler/redundancy and a dangling 'Step 2' reference.

Suggestions

Remove filler ('Use action names and parameters as needed.') and deduplicate the action-list command that already appears under 'Searching for actions' to tighten conciseness.

Resolve the dangling 'skip to Step 2' by labeling an actual 'Step 2: Search and run actions' section or rewording the pointer.

Add one complete worked example of `membrane action run` with a realistic `--input` JSON and the expected `output` field to push actionability toward fully copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but includes filler ('Use action names and parameters as needed.'), a redundant repeated action-list command under 'Popular actions', and an intro paragraph explaining what WiseTime is — fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides copy-paste-ready CLI commands with real flags throughout (install, login, connection ensure, action list/run, request) plus a proxy flags table, fitting 'mostly executable guidance; concrete commands with minor gaps' — kept from 5 by placeholder-only examples without a full real input/output run.	4 / 5
Workflow Clarity	The connection lifecycle is a clear sequenced flow (install → login → ensure → poll state → act on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR → search → run) with state checkpoints and a re-poll feedback loop, fitting 'clear sequence with most checkpoints present'; a minor gap is the dangling 'skip to Step 2' with no labeled Step 2.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-organized under clear section headers with no nested references, fitting 'good structure; most content appropriately placed; minor organization gaps' — some inline detail (full state-handling, proxy flag table) could split into references but is reasonable inline.	4 / 5
	Total	15 / 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 correctly pairs a what-statement with a 'Use when' trigger and anchors itself to a distinct app name, but its action language is generic and the trigger phrase lacks synonyms or concrete triggers. It is functional but not exemplary.

Suggestions

Replace generic verbs with concrete WiseTime operations, e.g. 'Manage time entries, projects, and activities; generate time reports; automate time-tracking workflows.'

Add concrete trigger phrases and synonyms, e.g. 'Use when the user wants to query WiseTime time entries, projects, activities, teams, or generate time reports.'

Mirror the entity list from the body (Time Entry, Project, Activity, User, Team, Report) in the description to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the WiseTime domain but the actions are generic ('Manage data, records, and automate workflows') rather than concrete operations, matching the 'names domain but actions are minimal or generic' anchor and falling short of the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	It states a 'what' ('WiseTime integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with WiseTime data'), but the 'when' is generic rather than concrete trigger phrases, so it lands at 'both present, when could be more specific' rather than a 5.	4 / 5
Trigger Term Quality	The trigger phrase 'Use when the user wants to interact with WiseTime data' surfaces the natural keyword 'WiseTime', but it is a single generic phrasing with no synonyms (time tracking, time logs, time entries) or extensions, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app 'WiseTime' gives it a clear niche with minimal conflict risk, though the generic 'manage data, automate workflows' tail keeps slight overlap with other data-integration skills, fitting 'mostly distinct; minor overlap risk'.	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/wisetime/SKILL.md
Commit: f484c82

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