Name: timing
Rating: 51.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

timing

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

Quality

56%

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

Quality

Content

68%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-structured connection state machine, but it carries some marketing fluff and lacks validation guidance around destructive action/proxy operations.

Suggestions

Trim the opening product-marketing paragraph and "so you can focus..."-style filler to assume Claude's competence.

Add a verification step before destructive/batch operations, e.g. dry-run or confirm the action's inputSchema and outputSchema before `membrane action run` on mutating endpoints.

De-duplicate the action-list command (shown in both "Searching for actions" and "Popular actions") to tighten the document.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but the opening marketing paragraph ("It helps freelancers, consultants... accurate billing and productivity analysis") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding, and the "Popular actions" section repeats the action-list command already shown.	3 / 5
Actionability	The skill provides copy-paste-ready, fully executable commands for every common case — install, login (incl. headless), connection ensure/wait, action list/run with JSON input, and proxy requests — plus a complete options table.	5 / 5
Workflow Clarity	The connection setup flow has strong state-based feedback loops (poll BUILDING, handle CLIENT_ACTION_REQUIRED, re-poll), but running actions and proxying API requests are destructive/batch-capable operations with no validation or verification step, capping the score per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed; the single file is organized into clear, well-labeled sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, though the Timing Overview list and proxy options table could arguably live in reference files.	4 / 5
	Total	15 / 20 Passed

Description

45%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 the right structural shape (a 'what' plus an explicit 'Use when' trigger), but the capability language is generic and Timing-specific actions and natural trigger terms are largely missing.

Suggestions

Replace "Manage data, records, and automate workflows" with Timing-specific actions such as "track time, log hours to projects and tasks, and review timesheets".

Expand the trigger clause with natural user phrases, e.g. "Use when the user wants to track time, manage time entries or timesheets, or automate Timing workflows."

Add a concrete capability anchor (e.g. "start/stop timers, manage projects and tasks, pull time reports") to distinguish the skill from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Timing integration") but the actions — "Manage data, records, and automate workflows" — are minimal and generic, applying to almost any integration rather than Timing-specific capability.	2 / 5
Completeness	Both a 'what' and an explicit 'Use when' clause are present, but the 'what' ("Manage data, records, and automate workflows") is too vague to count as a clear, specific answer of what the skill does.	3 / 5
Trigger Term Quality	"Timing data" and "Timing" are relevant keywords, but the description omits the natural terms users actually say (time tracking, time entries, timesheets, billing, project hours), missing common variations and synonyms.	3 / 5
Distinctiveness Conflict Risk	The brand name "Timing" carves out a niche, but the generic verb language ("manage data, records, automate workflows") creates real overlap risk with CRM, database, and other integration skills.	3 / 5
	Total	11 / 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/timing/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.