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

everhour

Everhour integration. Manage Users, Organizations, Clients, Invoices. Use when the user wants to interact with Everhour 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/everhour/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 executable Membrane commands and a clear connection-state workflow, but it carries some over-explanation in the intro and overview sections and inlines a large action table rather than splitting it into a reference file.

Suggestions

Remove the prose intro ("Everhour is a time tracking...") and the confusing nested "Everhour Overview" list; Claude already understands the domain and the action table conveys coverage.

Add an explicit validation/recovery note for create/update actions (e.g. re-fetch the resource after mutation to confirm the change applied), since the workflow section only validates connection state.

Move the full "Popular actions" table into a references/actions.md file and keep only a few representative examples inline, signaling the link clearly for progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-and-table driven, but the opening paragraph explains what Everhour is and the redundant "Everhour Overview" nested bullet list plus stray lines like "Use action names and parameters as needed." could be trimmed.	3 / 5
Actionability	Copy-paste-ready CLI commands (install, login, connection ensure/get with --wait, action list/run, request) with flag tables and a populated action catalog fully cover the common integration cases.	5 / 5
Workflow Clarity	The install→auth→connect→poll-until-READY→search→run sequence is explicit with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll loop, though batch create/update actions lack an explicit validate-or-recover step.	4 / 5
Progressive Disclosure	No bundle files exist; content is organized under clear section headers with no nested references, but the 21-row action table is inlined and a longer skill like this could offload detail to a separate reference file.	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 answers both what and when and is clearly niche-scoped to Everhour, but relies on a generic "Manage" verb and a broad "interact with Everhour data" trigger rather than concrete actions and natural user phrases.

Suggestions

Replace the generic "Manage" with concrete verbs, e.g. "List, create, and update Users, Projects, Clients, Tasks, and Invoices in Everhour."

Expand the trigger to natural phrases a user would say, e.g. "Use when the user wants to track time, manage Everhour projects/tasks, or pull time and invoice reports."

Align the listed entities (Users, Organizations, Clients, Invoices) with the actions the skill actually exposes (Projects, Tasks, Sections, Time Records) to avoid over-claiming.

Dimension	Reasoning	Score
Specificity	"Manage Users, Organizations, Clients, Invoices" names the domain and several concrete resource types, but the only action verb is the generic "Manage", so it sits between naming entities and listing specific actions.	3 / 5
Completeness	Both "what" (Everhour integration managing Users/Organizations/Clients/Invoices) and "when" ("Use when the user wants to interact with Everhour data") are present, though the "when" clause could be more specific.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Everhour data" surfaces the product name as a keyword, but "interact with Everhour data" is generic and omits natural variations like time tracking, time entries, or invoices.	3 / 5
Distinctiveness Conflict Risk	"Everhour integration" names a specific product niche with distinct triggers, making it unlikely to fire for unrelated skills.	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/everhour/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.