Name: rescuetime
Rating: 60 (1 reviews)
Author: membranedev

rescuetime

RescueTime integration. Manage Persons, Activities, Categories, Goals, Reports. Use when the user wants to interact with RescueTime data.

Quality

70%

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/rescuetime/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 concrete, executable Membrane CLI commands and a well-sequenced connection workflow with state-based validation. It loses points mainly on conciseness from introductory context Claude already knows and on a dangling 'Step 2' reference.

Suggestions

Trim the opening overview paragraph and the 'This skill uses the Membrane CLI' explanation, which restate context Claude already has.

Define or relabel the 'Step 2' the text repeatedly skips to (e.g. add a '### Step 2: Search and run actions' heading) so the cross-reference resolves.

Fill the 'Popular actions' heading with a few concrete example actions or rename it, since it currently only restates the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what RescueTime is and how it is used, plus explanatory sentences like 'This skill uses the Membrane CLI to interact with RescueTime', are unnecessary context Claude largely already knows, matching the level-3 anchor of mostly efficient with some over-explanation.	3 / 5
Actionability	The content is fully executable with copy-paste-ready commands (npm install, membrane login, connection ensure, action run, request) including real flags, a proxy-options table, and JSON output guidance, matching the level-5 anchor of fully executable commands covering common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and an explicit poll-again feedback loop, matching the level-4 anchor; the repeated 'skip to Step 2' reference points to a heading that is never labeled, a minor validation/navigation gap keeping it below 5.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested or broken references, matching the level-4 anchor of good structure with minor organization gaps; some inline reference material (proxy flags, clientAction states) could live in a separate file but is reasonable inline.	4 / 5
	Total	16 / 20 Passed

Description

66%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 clearly identifies the RescueTime niche and provides both a 'what' and a 'when', but relies on a single generic verb ('Manage') and offers little trigger-term variety beyond the product name. Strengthening it with concrete verbs and richer trigger phrasing would lift specificity and trigger quality.

Suggestions

Replace the generic verb 'Manage' with specific actions, e.g. 'List, create, update, and delete Persons, Activities, Categories, Goals, and Reports'.

Broaden trigger terms beyond the product name, e.g. 'Use when the user wants to track time, review productivity reports, or manage RescueTime goals and activities'.

Consider naming concrete operations per resource (e.g. 'fetch Daily Summary and Highlights, set and check Goals') to make capabilities more explicit.

Dimension	Reasoning	Score
Specificity	Names the domain (RescueTime) and five concrete resource types (Persons, Activities, Categories, Goals, Reports), but the only action verb is the generic 'Manage', so it names resources rather than several distinct specific actions like the level-4 anchor requires.	3 / 5
Completeness	Both 'what' ('Manage Persons, Activities, Categories, Goals, Reports') and 'when' ('Use when the user wants to interact with RescueTime data') are present and explicit, though the 'when' clause is somewhat generic, matching the level-4 anchor.	4 / 5
Trigger Term Quality	The natural term 'RescueTime' appears, but the trigger surface is essentially just 'RescueTime' and 'RescueTime data' with no synonyms or variations, matching the level-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	RescueTime is a specific named product with distinctive resource types and an explicit 'interact with RescueTime data' trigger, giving it a clear niche with minimal conflict risk as in the level-5 anchor.	5 / 5
	Total	15 / 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/rescuetime/SKILL.md
Commit: f484c82

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