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

timetastic

Timetastic integration. Manage data, records, and automate workflows. Use when the user wants to interact with Timetastic 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/timetastic/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 well-structured, actionable guide to driving Timetastic through the Membrane CLI, with a clear connection-readiness workflow and explicit error-state handling. It loses points for some intro padding, generic placeholders instead of Timetastic-specific examples, and a slightly confusing step-numbering reference.

Suggestions

Trim the opening paragraph and the vague 'Timetastic Overview' bullets; assume Claude can infer HR/leave context or move that context to a reference file.

Add at least one Timetastic-specific worked example, e.g. `membrane action list --intent "list user absences" --connectionId=...` followed by a real `action run` call.

Fix the step numbering: either relabel '1b' and add an explicit 'Step 2' header, or remove the 'skip to Step 2' forward references in favor of inline headings.

Dimension	Reasoning	Score
Conciseness	Mostly concrete commands, but the introductory paragraph explaining what Timetastic is and who uses it, plus the bare 'Timetastic Overview' bullet list and 'Use action names and parameters as needed' filler, could be tightened.	3 / 5
Actionability	Provides copy-paste-ready membrane CLI commands for install, auth, connection, action search/run, and proxying, but examples use generic placeholders (QUERY, {'key':'value'}) rather than Timetastic-specific invocations.	4 / 5
Workflow Clarity	Clear sequence from install to auth to connection with explicit state-based validation and feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR); minor gap is the undefined 'Step 2' reference and oddly numbered '1b' header.	4 / 5
Progressive Disclosure	Well-organized into distinct sections with no nested references and no content stranded in missing files; the single-file structure is appropriate, though it runs longer than the under-50-line simple-skill exception and could split the proxy/options detail.	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 covers a named-product niche and includes an explicit 'Use when' trigger, so both what and when are present. Its weakness is generic, non-concrete action language that under-specifies what the skill actually does with Timetastic.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Timetastic actions, e.g. 'List and create absences, manage leave allowances, and query users'.

Expand the trigger clause with specific user phrases, e.g. 'Use when the user wants to book or approve time off, check leave balances, or query Timetastic absence records'.

Add file/extension-style natural synonyms where applicable (e.g. mention holidays, sick leave, PTO) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Timetastic) but the listed actions 'Manage data, records, and automate workflows' are generic abstractions rather than concrete operations like listing absences or approving leave.	2 / 5
Completeness	Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Timetastic data'); the 'when' is present but could be more specific about Timetastic use cases.	4 / 5
Trigger Term Quality	Includes the natural keyword 'Timetastic' plus 'data', but lacks common synonyms or variations a user might say; comparable to the 'Works with PDF files' single-keyword anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Timetastic' product name gives it a clear niche with minimal conflict risk, though the generic 'manage data, records, workflows' phrasing leaves minor overlap with other HR/leave 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/timetastic/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.