Name: everee
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

everee

Everee integration. Manage Companies. Use when the user wants to interact with Everee data.

Quality

72%

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

Quality

Content

78%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 content is highly actionable and reasonably sequenced, but it leans on a single inlined file rather than splitting reference material into bundled files. Fixing the dangling step labels and moving the action catalog to a reference would raise the lower dimensions.

Suggestions

Resolve the dangling references: define "Step 2" and add a matching "1a" before "1b. Wait for the connection to be ready".

Move the Popular actions table and proxy options into a references/ file (e.g. ACTIONS.md) and link to it from the body.

Trim the introductory Everee paragraph to only what Claude cannot infer about the platform.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference, with only minor over-explanation in the opening Everee summary and the conversational "Agent Types" line.	4 / 5
Actionability	Copy-paste-ready `membrane` commands and a populated Popular actions table cover the common cases with concrete keys and parameter examples.	5 / 5
Workflow Clarity	The connect → poll-for-ready → search → run flow is sequenced with state-based feedback loops (READY/CLIENT_ACTION_REQUIRED), though dangling "Step 2" and "1b" labels introduce minor gaps.	4 / 5
Progressive Disclosure	It is a single monolithic file with the large actions table and proxy flag reference inlined, and no external bundle files or signaled references to offload detail.	3 / 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 is distinct and supplies both a what and a when, but it is thin on specific capabilities and trigger synonyms. Expanding the action list and adding natural trigger phrases would lift the weaker dimensions.

Suggestions

List 2-3 concrete capabilities beyond "Manage Companies" (e.g., manage workers, payrolls, timecards) to improve specificity.

Add natural trigger variations such as "payroll", "pay statements", or "worker data" alongside "interact with Everee data".

Tighten the "Use when..." clause to name the concrete Everee tasks users would ask for.

Dimension	Reasoning	Score
Specificity	"Manage Companies" names the Everee domain and one concrete-ish action, but the verb is generic and only a single entity type is mentioned, so coverage is not comprehensive.	3 / 5
Completeness	It states what it does ("Everee integration. Manage Companies.") and gives an explicit "Use when..." trigger, though the trigger phrasing could be more specific.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Everee data" surfaces the key proper-noun "Everee" but offers no synonyms or natural variations beyond "interact with ... data".	3 / 5
Distinctiveness Conflict Risk	Everee is a specific named application, giving the description a clear niche with minimal overlap risk against other 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/everee/SKILL.md
Commit: f484c82

Reviewed: 1 day 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.